JS shell and fuzz-tests crash when libFuzzer calls `exit`
Categories
(Core :: Fuzzing, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox85 | --- | wontfix |
firefox86 | --- | wontfix |
firefox87 | --- | fix-optional |
People
(Reporter: decoder, Assigned: decoder)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Since the refactoring in bug 1664810, both the JS shell (when used in jsrtfuzzing mode) and the fuzz-tests binary crash when libFuzzer calls exit
, because an in-use mutex is being destroyed. This affects mostly merge jobs and coverage runs because in these situations, libFuzzer will exit eventually (in regular fuzzing, libFuzzer just keeps going forever until it crashes).
Right now, the easiest solution seems to be another atexit
handler, just like we have in Firefox already for deinitializing XPCOM.
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
bugherder |
Assignee | ||
Comment 4•5 years ago
|
||
Reopening this, because we need a follow-up to silence a warning I am seeing now in some targets. The problem is that we should also free any active runtimes before calling shutdown. This isn't a blocker like the previous issue, but it would still be much cleaner to properly shutdown all runtimes instead of leaking them.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Description
•