Closed Bug 751121 Opened 12 years ago Closed 12 years ago

Intermittent mochitest-a11y leak of 404 bytes (1 Mutex, 2 ReentrantMonitor, 1 nsHttpConnectionMgr, 1 nsTArray_base, 1 nsThread)

Categories

(Core :: General, defect)

15 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, memory-leak)

Rev3 Fedora 12 fx-team debug test mochitest-other on 2012-05-01 17:36:10 PDT for push 41e7d93533c1

slave: talos-r3-fed-064

https://tbpl.mozilla.org/php/getParsedLog.php?id=11374806&tree=Fx-Team

{
== BloatView: ALL (cumulative) LEAK AND BLOAT STATISTICS, default process 2918

     |<----------------Class--------------->|<-----Bytes------>|<----------------Objects---------------->|<--------------References-------------->|
                                              Per-Inst   Leaked    Total      Rem      Mean       StdDev     Total      Rem      Mean       StdDev
   0 TOTAL                                          15      404 65193620        7 ( 9236.83 +/- 11368.77) 30936074        3 ( 8838.73 +/- 17625.32)
 148 Mutex                                          12       12     2989        1 (  126.98 +/-    18.28)        0        0 (    0.00 +/-     0.00)
 189 ReentrantMonitor                               16       32     3017        2 (   97.24 +/-    42.60)        0        0 (    0.00 +/-     0.00)
 713 nsHttpConnectionMgr                           176      176        1        1 (    1.00 +/-     0.00)       42        1 (    2.34 +/-     0.86)
 984 nsTArray_base                                   4        4  6318582        1 (40903.66 +/- 12368.92)        0        0 (    0.00 +/-     0.00)
 994 nsThread                                      112      112       49        1 (   13.76 +/-     4.63)    33729        1 (  116.86 +/-    11.57)
 999 nsTimerImpl                                    68       68     5819        1 (   36.03 +/-     3.19)    40179        1 (   60.32 +/-     6.21)

nsTraceRefcntImpl::DumpStatistics: 1157 entries
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 404 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of Mutex with size 12 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 2 instances of ReentrantMonitor with size 16 bytes each (32 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsHttpConnectionMgr with size 176 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsTArray_base with size 4 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsThread with size 112 bytes
TEST-INFO | automationutils.processLeakLog() | leaked 1 instance of nsTimerImpl with size 68 bytes

== BloatView: ALL (cumulative) LEAK AND BLOAT STATISTICS, plugin process 2975

     |<----------------Class--------------->|<-----Bytes------>|<----------------Objects---------------->|<--------------References-------------->|
                                              Per-Inst   Leaked    Total      Rem      Mean       StdDev     Total      Rem      Mean       StdDev
   0 TOTAL                                          28        0      319        0 (   26.82 +/-    22.31)      271        0 (   58.89 +/-    45.72)

nsTraceRefcntImpl::DumpStatistics: 21 entries
TEST-PASS | plugin process 2975 | automationutils.processLeakLog() | no leaks detected!

INFO | runtests.py | Running tests: end.
program finished with exit code 0
elapsedTime=250.608495
TinderboxPrint: mochitest-a11y<br/>22662/0/1173&nbsp;<em class="testfail">LEAK</em>
}
Summary: Intermittent mochitest-other leak of 404 bytes (1 Mutex, 2 ReentrantMonitor, 1 nsHttpConnectionMgr, 1 nsTArray_base, 1 nsThread) → Intermittent mochitest-a11y leak of 404 bytes (1 Mutex, 2 ReentrantMonitor, 1 nsHttpConnectionMgr, 1 nsTArray_base, 1 nsThread)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.