Version: All
OS: OSX

What steps will reproduce the problem?
(1) Build Chrome on OSX like normal.

What is the expected output? What do you see instead?
Every once in a while, the Python scripts in the build process run out of processes for multiprocessing and I get a traceback that looks something like this:

    Traceback (most recent call last):
      File "../../../../native_client/build/build_nexe.py", line 1136, in <module>
        sys.exit(Main(sys.argv))
      File "../../../../native_client/build/build_nexe.py", line 1044, in Main
        process.start()
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/process.py", line 130, in start
        self._popen = Popen(self)
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/forking.py", line 121, in __init__
        self.pid = os.fork()
    OSError: [Errno 35] Resource temporarily unavailable

This doesn't happen often enough for it to seriously impact my development, but it does cost me 10-20 minutes if I expect the build to complete in the background.

Should it be sufficient to raise process limits per [1]?
I currently have:

lgarron@lgarron-macbookpro ~ [1]> sysctl kern.maxproc kern.maxprocperuid
kern.maxproc: 1064
kern.maxprocperuid: 709

[1] https://chromium.googlesource.com/chromium/src/+/master/docs/mac_build_instructions.md#Raising-system_wide-and-per_user-process-limits

groby@, I seem to recall you talking about this in the past. Do you know who is best to ask?
 

Deleted: ninja-output.txt 11.3 KB

ninja-output.txt 11.3 KB View Download