Closed
Bug 661467
Opened 14 years ago
Closed 1 year ago
Leaks during dromaeo tests?
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: gwagner, Unassigned)
References
Details
(Whiteboard: [MemShrink:P3])
Attachments
(1 file)
(deleted),
text/plain
|
Details |
Looks like we have some leaks during the dromaeo JavaScript performance suite.
We start with a marking time of around 10 ms for each GC. After a while the marking time increases to 60ms even for compartment GCs.
Neat find. Is it possible that they're just stashing away benchmark results in some sort of large, inefficient data structure? We should try to get a break down of the mark time and see how much XPConnect is contributing, since I assume that's the sort of leak you're thinking of?
Comment 2•14 years ago
|
||
There could be all sorts of stashing involved, yes. Worth looking at the actual code too, perhaps.
Updated•14 years ago
|
Whiteboard: [MemShrink:P2]
Comment 3•13 years ago
|
||
Gregor, would you have time to look into this?
Comment 4•13 years ago
|
||
Downgrading this bug -- I don't think we're going to take any concrete action here unless we have a reason to think that Dromaeo itself is not to blame here.
Whiteboard: [MemShrink:P2] → [MemShrink:P3]
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•