Open
Bug 994253
Opened 11 years ago
Updated 7 months ago
[meta] Extend and improve JS crash diagnostics
Categories
(Core :: JavaScript: GC, defect, P3)
Core
JavaScript: GC
Tracking
()
NEW
flash10
People
(Reporter: terrence, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
For as long as we've had crash reporting, we've been plauged by a trickle of crashes in the GC that appear to be due to problems elsewhere in the code or hardware. At today's GC meeting we brainstormed ideas to help find and fix these lingering bugs.
The plan:
Add extra assertions to debug and fuzzing builds which can be independently enabled in opt builds. As we identify specific symptoms, we can flip these flags on for a few days on nightly, on select platforms, to find specific problems. These flags should aim for <10% performance regression, but this is a soft limit depending on the urgency and severity of the identified crashes.
|
||
Updated•11 years ago
|
|
Reporter | |
Updated•11 years ago
|
Priority: P2 → --
Summary: [meta] Operation crash like you mean it → [meta] Extend and improve JS crash diagnostics
Target Milestone: --- → flash10
|
|
Reporter | |
Updated•11 years ago
|
Blocks: GC.stability
|
||
Updated•6 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•