Closed
Bug 728699
Opened 12 years ago
Closed 12 years ago
error console logging for GC should indicate if incremental GC is disabled
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mccr8, Unassigned)
References
Details
This would be useful for figuring out what is going on. Currently with (I'm assuming) incremental disabled there's no explicit indication that it is turned off: GC(T+2096.4) TotalTime: 138.6ms, Type: global, MMU(20ms): 0%, MMU(50ms): 0%, Reason: CC_WAITING, +chunks: 0, -chunks: 0 mark: 103.6, mark-roots: 8.9, mark-other: 4.4, sweep: 32.0, sweep-obj: 6.1, sweep-string: 1.3, sweep-script: 0.6, sweep-shape: 5.0, discard-code: 2.1, discard-analysis: 8.2, xpconnect: 2.2, deallocate: 0.1 The lack of any information about slices, and the 0% MMU, is an indication, but given that this is an erroneous situation, it would be nice if it explicitly said that incremental GC is disabled.
Comment 2•12 years ago
|
||
thats not the point.
Reporter | ||
Comment 3•12 years ago
|
||
This was fixed at some point: GC(T+91204.4) TotalTime: 165.7ms, Type: global, MMU(20ms): 0%, MMU(50ms): 0%, Reason: SET_NEW_DOCUMENT, NonIncrementalReason: incremental permanently disabled, +chunks: 0, -chunks: 0 mark: 111.6, mark-roots: 10.6, mark-other: 3.9, sweep: 52.8, sweep-obj: 6.8, sweep-string: 0.6, sweep-script: 0.7, sweep-shape: 4.4, discard-code: 2.4, discard-analysis: 28.8, xpconnect: 2.6, deallocate: 0.1
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•