Open Bug 673492 Opened 13 years ago Updated 2 years ago

Automated GC regression testing

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect

Tracking

()

People

(Reporter: gwagner, Unassigned)

References

(Blocks 2 open bugs)

Details

It seems that GC regressions become a very serious problem now and we have no way of detecting it other than manually look at the GCTIMER output.
Currently I see a bad behavior for the v8-splay benchmark in a multithreaded shell on my MBP. We *always* perform 2 GCs right after each other. So the 2nd GC has to wait for the first background finalization to end. In my case it has to wait 20ms for every other GC. So the number of GCs not only doubled, but we also have a locking time where we wait for the first GC to finish.

We need a better way to detect this!
No longer blocks: GenerationalGC
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.