Eliminate crashes from crash-stats due to difficult data races
Categories
(Core :: DOM: Security, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: ckerschb, Assigned: ckerschb)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
We have received a number crashes that occur in crash-stats due to very difficult to reproduce data races. We were able to trace a few of them and found that even the most common of these crashes were so dependent on internal timing we couldn't cause them to reproduce.
I think we should be able to prevent more from being introduced while we burn down the backlog.
If you need more info, please let me know and I add you to the internal document.
|
Assignee | |
Comment 1•4 years ago
|
||
Pushed by cbrindusan@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1f667dc68332 Assert IsSafeToRunScript. r=emilio
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
|
||
Comment 5•1 year ago
|
||
Christoph, do you think this machinery should crash in fuzzing builds (#ifdef FUZZING)? Maybe during the check? I guess not in the constructor..
|
|
Assignee | |
Comment 6•11 months ago
|
||
(In reply to Frederik Braun [:freddy] from comment #5)
Christoph, do you think this machinery should crash in fuzzing builds (
#ifdef FUZZING)? Maybe during the check? I guess not in the constructor..
I looked at it in more detail and at this point I don't think we should crash in fuzzing builds. However, once we have eliminated more of the cases maybe we can crash in fuzzing builds.
Description
•