Closed Bug 483917 Opened 15 years ago Closed 15 years ago

"Negative leaks caught" in mochitests


(Testing :: General, defect)

Not set


(Not tracked)



(Reporter: roc, Unassigned)



(Keywords: fixed1.9.1, intermittent-failure)

*** 84926 INFO Passed: 78399
*** 84927 INFO Failed: 0
*** 84928 INFO Todo:   1254
*** 84929 INFO SimpleTest FINISHED
INFO | ( | Application ran for: 1:08:55.235061

== BloatView: ALL (cumulative) LEAK AND BLOAT STATISTICS

                                              Per-Inst   Leaked    Total      Rem      Mean       StdDev     Total      Rem      Mean       StdDev
   0 TOTAL                                          -5        0 -1136421943        0 (188643.78 +/-     0.00) 1059492278        0 (21041.09 +/-     0.00)

nsTraceRefcntImpl::DumpStatistics: 1180 entries

Since no particular classes were displayed, my best guess is that this is a bug in test automation or bloat test code. Is it possible that something overflowed?
See also bug 482236, bug 483500.  This should probably depend on the latter.
The underlying "leak" is the one already tracked in comment 1 bugs.

The new failure message confirms that bug 482236 fix works :-)

The filtering out of the nsRect line is an erroneous side-effect of bug 469509 fix :-(
(See the discussion there about all the good I think of the patch which was checked in...)
Blocks: 469509
Depends on: 482236
Version: unspecified → Trunk
No longer depends on: 482236
Depends on: 482236
Depends on: 483500
No longer blocks: 469509
Depends on: 469509
I just landed bug 483500, so if this happens again on mozilla-central, we need a new theory about why it's happening.

If it doesn't happen again on mozilla-central, we should probably land bug 483500 on mozilla-1.9.1.
It does still appear on 1.9.1:
OS X 10.5.2 mozilla-1.9.1 unit test on 2009/04/16 13:45:04
bug 483500 is now landed on 1.9.1.

I'm going to allege that it fixed this.  If not, please reopen.
Closed: 15 years ago
Keywords: fixed1.9.1
Resolution: --- → FIXED
OS X 10.5.2 mozilla-1.9.1 unit test on 2009/04/17 05:13:25  

(before the landing on 1.9.1)
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.