Closed
Bug 860785
Opened 11 years ago
Closed 9 years ago
Bimodal data in Talos Trace Malloc MaxHeap on linux32 (CentOS release 5)
Categories
(Testing :: Talos, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mbrubeck, Unassigned)
Details
(Whiteboard: [SfN])
Trace Malloc MaxHeap results seem to jump between two values on these Linux machines, causing occasional false regression alarms and making real regression finding tricky: http://graphs.mozilla.org/graph.html#tests=[[29,63,6]]&sel=1365091290490,1365696090490&displayrange=7&datatype=running
Comment 1•11 years ago
|
||
This is annoying but it's unclear what can be done about it, given that we have just a single number.
Whiteboard: [SfN][MemShrink] → [SfN]
Comment 2•11 years ago
|
||
A guess would be that it depends on whether we GC at some point or another when we're at max memory usage.
Comment 3•9 years ago
|
||
we don't run this specific test anymore
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•