11_x86 build - build failures due to 'no space on device'

Ryan Schmidt ryandesign at macports.org
Fri Apr 9 18:25:52 UTC 2021

On Apr 8, 2021, at 16:04, Jason Liu wrote:

>> For some reason fseventsd was taking 14GB of memory.
> Not really surprising, for a machine being used as a builder. The constant creation and deletion of files when compiling software is bound to be generating a ton of file system events.

It's completely surprising and unusable for an OS background process to suddenly take 14 *GB* of memory, and Apple will be receiving a bug report from me about it.

Being a build machine is not relevant. None of the other build machines I run for MacPorts, from 10.5 through 10.15, have ever exhibited this problem. Only the macOS 11 machine has, and then not all the time. Right now, the macOS 11 machine is busy building and its fseventsd process is only taking 13 *MB* of memory.

I believe I observed the increased fseventsd memory usage on macOS 11 before when I started a Time Machine backup. I don't want to start a backup now because if it causes the problem again then it might affect the currently running builds. When the currently queued builds are finished, or in a few days, I'll take the builder offline and do a backup, and if the issue surfaces again, then I'll file the bug report.

More information about the macports-dev mailing list