Open
Bug 1159323
Opened 10 years ago
Updated 2 years ago
[jsdbg2] The onGarbageCollection hook should fire for each slice instead of each cycle
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: fitzgen, Unassigned)
References
(Blocks 1 open bug)
Details
It turns out that the API would be easier for devtools API users if it were this way.
We would need to restructure the event data to something like
{
// Whether this is an incremental slice, or not.
isIncrementalSlice: true|false,
// This would just be the major GC number, used to identify
// which slices are related to each other.
incrementalGCCycle: Number,
// If nonincremental, string saying why.
nonincrementalReason: null|string,
// Short string describing why we are GCing at all.
reason: string,
// Timestamps for the start and end of this slice/collection.
startTimestamp: timestamp,
endTimestamp: timestamp
}
Reporter | ||
Updated•10 years ago
|
Blocks: memory-platform
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•