JavaScript error: resource://gre/modules/CrashManager.jsm, line <random>: AbortError: IOUtils: Shutting down and refusing additional I/O tasks
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
People
(Reporter: whimboo, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:94.0) Gecko/20100101 Firefox/94.0 ID:20211003201113
Running the Puppeteer unit tests on MacOS locally result in a lot of shutdown hangs. For most of these cases I can see the following JavaScript error in the log:
JavaScript error: resource://gre/modules/CrashManager.jsm, line 828: AbortError: IOUtils: Shutting down and refusing additional I/O tasks
As result the crash reporter claims that no crash report could be written because the application data file hasn't been found. And as it looks like here we have a case that writing this file to disk is refused by IOUtils because of an ongoing shutdown.
The steps to take to reproduce this are:
- Change this line to use
describe.only
- Run
./mach puppeteer-test --subset
To reproduce the shutdown hangs you have to use an artifact build (maybe also a full build will be ok), but a Nightly will not show them. I'm still investigating why these shutdown hangs only happen for these kind of builds.
Gabriele, could you please have a look why we are failing here?
Comment 1•3 years ago
|
||
Our error-handling in that particular area is incomplete, this is caused by bug 1694624.
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Reporter | ||
Updated•2 months ago
|
Reporter | ||
Comment 3•2 months ago
|
||
Gabriele, most of the shutdown hangs as listed on bug 1358898 have that error in the lines. Do you think that it could be one of the culprits?
Comment 4•2 months ago
|
||
Yes, it could be. We are considering getting rid of the crash manager entirely in bug 1911301.
Reporter | ||
Comment 5•2 months ago
|
||
Thanks Gabriele. Does it mean bug 1694624 can be closed as wontfix or could this bug a workaround until bug 1911301 is fixed, which seems to be a complex refactoring that might take longer.
Comment 6•2 months ago
|
||
Yes, I forgot about bug 1694624, that should be an effective workaround and is relatively easy to fix. I'll prioritize it.
Reporter | ||
Comment 7•2 months ago
|
||
The line has changed and as I can see a good number of bugs seem to have been classified for bug 1358898. I'll try to correct some of them.
Reporter | ||
Updated•2 months ago
|
Reporter | ||
Comment 8•2 months ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #6)
Yes, I forgot about bug 1694624, that should be an effective workaround and is relatively easy to fix. I'll prioritize it.
The number of failures (21 in the last week) isn't that high but I wonder if you were able to make some progress on bug 1694624. Thanks Gabriele!
Comment 9•2 months ago
|
||
No I hadn't, but I've quickly cobbled a patch together, let's see if it survives testing.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Reporter | ||
Comment 16•13 days ago
|
||
Gabriele, there are still issues on autoland. Is that expected?
Comment 17•13 days ago
|
||
It wasn't expected but I see it's a different problem. I now realize that my patch only addressed issues around the crash manager store not being accessible, but we can still have failures with I/O operations on other files - like the ones in a crash report. I have to put guards around all I/O operations to make this code more robust. I'll file a separate bug.
Comment hidden (Intermittent Failures Robot) |
Reporter | ||
Comment 19•6 days ago
|
||
(In reply to Intermittent Failures Robot from comment #18)
23 failures in 4515 pushes (0.005 failures/push) were associated with this bug in the last 7 days.
All these failures seem to be unrelated to this bug. I filed bug 1930437 to cover this specific shutdown hang.
Description
•