Open
Bug 1509157
Opened 6 years ago
Updated 7 months ago
Make GC-related failures more deterministic to assist test case reduction
Categories
(Core :: JavaScript: GC, enhancement, P5)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: sfink, Unassigned)
References
(Blocks 1 open bug)
Details
Spawned from bug 1479529.
The idea is that you have a massive unreduced test case that crashes as a side effect of GC'ing at just the wrong time. Currently, reducing such test cases can be difficult because eliminating code is likely to eliminate allocations, which shifts when the GC happens. If we could have a GC happen at the "same" point in the reduced test case, it is more likely to reproduce the problem.
As gkw noted in bug 1479529 comment 1, we *do* have GCAfterAllocations(N) that could attempt to vary the N, so a separate mechanism to report the allocation triggers or whatever to reproduce them might be more trouble than it's worth, but I'm filing a bug to record the idea anyway.
|
||
Updated•6 years ago
|
Priority: -- → P5
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•7 months ago
|
Blocks: GC.easeofuse
Severity: S3 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•