Backstory: when Botond tried landing bug 1611660, it caused a spike in win7 mingw reftest timeouts. See bug 1611660 comment 40 for a sample try push. I've been doing try pushes with additional logging to track this down, and the timeouts are caused by the content process simply hanging at various points. I've done many try pushes with lots of printfs to bisect exactly where the hangs are. This bug is specifically about the content process hanging somewhere in at [this block of code](https://searchfox.org/mozilla-central/rev/5e4d4827aa005d031580d2d17a01bae1af138b2e/toolkit/crashreporter/nsExceptionHandler.cpp#3512-3516). See e.g. the output in [this try push](https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=304530511&repo=try&lineNumber=66349) where the last line logged comes from [this printf](https://hg.mozilla.org/try/rev/16b40bfbf43978d78c84cafd3fc1d8dc7224d2ce#l1.17) and the next one a couple of lines down (after the ExceptionHandler creation) doesn't show up in the log. I'll do more try pushes to narrow this down further, and file other bugs for other hang points as I identify them.
Bug 1642331 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Backstory: when Botond tried landing bug 1611660, it caused a spike in win7 mingw reftest timeouts. See bug 1611660 comment 40 for a sample try push. I've been doing try pushes with additional logging to track this down, and the timeouts are caused by the content process simply hanging at various points. I've done many try pushes with lots of printfs to bisect exactly where the hangs are. This bug is specifically about the content process hanging somewhere in [this block of code](https://searchfox.org/mozilla-central/rev/5e4d4827aa005d031580d2d17a01bae1af138b2e/toolkit/crashreporter/nsExceptionHandler.cpp#3512-3516). See e.g. the output in [this try push](https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=304530511&repo=try&lineNumber=66349) where the last line logged comes from [this printf](https://hg.mozilla.org/try/rev/16b40bfbf43978d78c84cafd3fc1d8dc7224d2ce#l1.17) and the next one a couple of lines down (after the ExceptionHandler creation) doesn't show up in the log. I'll do more try pushes to narrow this down further, and file other bugs for other hang points as I identify them.