ASSERTION: Serial number requested for unrecognized pointer! Are you memmoving a refcounted object? when cycle collecting nsGenericElement after loading tinderbox

NEW
Unassigned

Status

()

Core
DOM: Core & HTML
8 years ago
8 years ago

People

(Reporter: hsivonen, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
(Redescribed from bug 514807).

Steps to reproduce:
 1) Enable leak logging for nsGenericElement
 2) Load http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox
 3) Quit the app.

Actual results:
Lots of assertions like
###!!! ASSERTION: Serial number requested for unrecognized pointer!  Are you memmoving a refcounted object?: 'serialno != 0', file /Users/Shared/Projects/mozilla-html5/xpcom/base/nsTraceRefcntImpl.cpp, line 996
###!!! ASSERTION: Serial number requested for unrecognized pointer!  Are you memmoving a refcounted object?: 'serialno != 0', file /Users/Shared/Projects/mozilla-html5/xpcom/base/nsTraceRefcntImpl.cpp, line 1050

(Looking at the stacks shows that this is cycle collector releasing stuff.)

Expected results:
No assertions.

Additional info:
Happens both with the old parser and the HTML5 parser.
And is this a recent regression, or has it been around for a while?
Any stacks? I doubt this is a CC problem. I've seen this for documents, because they're added as mutation observers to themselves. We end up refcounting them from LastRelease where we addref the mutation observers, but we've already removed the object from the serial number hash (from the last release).
You need to log in before you can comment on or make changes to this bug.