Open
Bug 1242726
Opened 8 years ago
Updated 2 years ago
Leak check should report a more starrable failure when leaking multiple windows
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: mccr8, Unassigned)
Details
(Whiteboard: [MemShrink:P2])
When a test leaks multiple nsDOMWindows, leakcheck reports a large generic list of leaked objects. This means that multiple window leaks can get dumped into the same bug, specifically into bug 1186675. It would be good if leakcheck could recognize that there is a generic window leak, and display some other information, like maybe the URL of the leaked window, instead.
Updated•8 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 1•8 years ago
|
||
Does the leak analyzer still work? I at some point made it work with TBPL so that it would tell you which window got leaked. Not sure what happened to that in the transition to TH.
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to :Ehsan Akhgari from comment #1) > Does the leak analyzer still work? I at some point made it work with TBPL > so that it would tell you which window got leaked. Not sure what happened > to that in the transition to TH. If this is the same thing I'm thinking of, IIRC it wasn't ported over to TreeHerder, but was already broken anyways in TBPL at the time the transition happened.
Comment 3•8 years ago
|
||
Yep, the way I remember it is that nobody ever made it survive the switch to mozharness with the timestamps at the start of lines.
Comment 4•8 years ago
|
||
Bug 840192
Comment 5•8 years ago
|
||
Well then!
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•