Intermittent awsy\test_base_memory_usage.py TestMemoryUsage.test_open_tabs | AssertionError: heap-unclassified was negative
Categories
(Core :: Graphics: WebRender, defect, P5)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: intermittent-failure)
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Comment 4•6 years ago
|
||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Comment hidden (Intermittent Failures Robot) |
Comment 9•6 years ago
|
||
Comment 10•6 years ago
|
||
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 14•6 years ago
|
||
I downloaded the DMD logs from the try run failure in comment 13 and ran them through dmd.py. Only one of the files (dmd-TabsOpenForceGC-0-12128.json.gz) had twice-reported entries, and that amounted to a total of 448 bytes, while the failure message was complaining about heap-unclassified being -3152. So either the DMD logs are not catching the relevant twice-reported, or we're actually reporting a negative number somewhere. Not sure what's the deal here.
Comment 15•6 years ago
|
||
Also I guess the failure in comment 13 is not from a -qr build. There haven't been any failures on -qr builds for a while (the previous two comments where on try pushes in december). So from a QR point of view this is effectively WFM. I'm gonna close it. If it happens on non-try builds somebody should file a new bug (or reopen this one if the builds are QR builds).
Comment hidden (Intermittent Failures Robot) |
Description
•