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
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]
A guess would be that it depends on whether we GC at some point or another when we're at max memory usage.
we don't run this specific test anymore
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.