I think I know why this error appears and disappears. All of the "application unexpectedly closed" messages occur on pushes at around 20:00 UTC. That would be the busiest time for the build infrastructure, with merge builds in progress on m-c (2), m-i, and autoland, plus it's afternoon US time where a lot of the developers are. Tests run at other times of day don't have the timeout problem. I've just re-run some failed tests from last week with different results. What do we do about it? I'm not sure yet, re-running some more recent failed tests to see what happens with them.
Bug 1545918 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think I know why this error appears and disappears. All of the "application unexpectedly closed" messages occur on pushes at around ~~20:00~~ 22:00 UTC. That would be the busiest time for the build infrastructure, with merge builds in progress on m-c (2), m-i, and autoland, plus it's afternoon US time where a lot of the developers are. Tests run at other times of day don't have the timeout problem. I've just re-run some failed tests from last week with different results. What do we do about it? I'm not sure yet, re-running some more recent failed tests to see what happens with them.