Goma with large -j keeps chrome from opening tabs, all other apps are fine |
|||||
Issue descriptionGoogle Chrome 59.0.3041.0 (Official Build) canary (64-bit) Revision 0192171168e7afc337edc13c150eca4152185cd5-refs/heads/master@{#456562} OS Mac OS X Build with ninja -C out/Release -j 400 on a MBP. Then try to open a new Chrome tab, the tab will fail to load with no obvious error (shows the crashed tab icon) but no crash is in about:crashes. Note that while this seems like a too many processes bug Safari works fine in this state. I can also launch other apps like Activity Monitor, Sublime, and others. The badness is confined to Chrome only where it seems like it's not handling an error the same as the other apps or doing something unusual.
,
Mar 15 2017
It's not clear what needs fixing here, some interaction between goma and chrome makes chrome unnable to open tabs while every other app on the system is fine. Maybe Chrome has a race condition where when the system is very under load tabs fail?
,
Mar 15 2017
I'm guessing Chrome is unable to create new processes, but that doesn't explain why Safari continues working. If you try it again and confirm that Chrome is unable to open tabs, try it again in Safari and see (via Activity Monitor) if there are new Safari processes for new tabs you create in Safari.
,
Apr 28 2017
rsesek@ - any thoughts here about what's going on, or how to determine what code paths are being traversed?
,
Apr 28 2017
Logs would maybe help, either from Console.app or running Chrome with --enable-logging. There's not really a lot to go on in this report at the moment. Is this consistently reproducible?
,
May 1 2017
,
May 1 2017
I'll see if I can get some logs this week.
,
May 11 2017
I'm going to WontFix this since I won't have time to get the logs before leaving. I'm not sure what the problem is but I suspect there's a serious bug somewhere in the tab opening logic when the system is under load. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by shinyak@google.com
, Mar 15 2017