Closed Bug 858962 Opened 13 years ago Closed 12 years ago

Intermittent leakcheck | 436775 bytes leaked (AtomImpl, BackstagePass, BodyRule, Comment, Crypto, ...)

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: intermittent-failure, memory-leak)

Andrew, I don't suppose you could lend some help in this? https://tbpl.mozilla.org/php/getParsedLog.php?id=21504082&tree=Mozilla-Inbound Rev3 WINNT 5.1 mozilla-inbound debug test crashtest on 2013-04-05 19:27:39 PDT for push b56d762d3511 slave: talos-r3-xp-031 02:45:36 INFO - TEST-INFO | leakcheck | leaked 130 AtomImpl (3120 bytes) 02:45:36 INFO - TEST-INFO | leakcheck | leaked 12 BackstagePass (432 bytes) 02:45:36 INFO - TEST-INFO | leakcheck | leaked 2 BodyRule (32 bytes) 02:45:36 INFO - TEST-INFO | leakcheck | leaked 3 Comment (204 bytes) 02:45:36 INFO - TEST-INFO | leakcheck | leaked 2 Crypto (24 bytes) 02:45:36 WARNING - TEST-UNEXPECTED-FAIL | leakcheck | 436775 bytes leaked (AtomImpl, BackstagePass, BodyRule, Comment, Crypto, ...) TBPL leak analyzer says leaked 3 DOMWINDOW(s).
What DOMWINDOWs leaked?
Unfortunately, the leak analyzer doesn't say, and I have little experience trying to discern that from the log :( Philor, can you help?
I can just write a little script to match ++DOMWINDOW to --DOMWINDOW if need be.
The leak analyzer got broken by mozharness sticking its timestamps and INFO at the start of lines, so http://hg.mozilla.org/webtools/tbpl/file/1a851b11739b/php/inc/LeakAnalyzer.php#l84 needs to be fixed, bug 840192.
Thanks for the link. Yeah, that is unfortunate...
Assignee: nobody → continuation
It looks like this only happened twice. Feel free to needinfo me if this starts happening regularly.
Assignee: continuation → nobody
(OrangeWFM bugs not touched for 2 months)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.