If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Leaks during dromaeo tests?

NEW
Unassigned

Status

()

Core
JavaScript Engine
6 years ago
3 years ago

People

(Reporter: gwagner, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P3])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 536820 [details]
GCTimer output

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?
There could be all sorts of stashing involved, yes.  Worth looking at the actual code too, perhaps.
Blocks: 659860
Whiteboard: [MemShrink:P2]
Gregor, would you have time to look into this?
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

3 years ago
Assignee: general → nobody
You need to log in before you can comment on or make changes to this bug.