Created attachment 571971 [details] [diff] [review] v1 The Release adds the document to the cycle collector as a suspect, even though we know it's not collectable (that's the whole point of the code in nsCCUncollectableMarker).
Is this just going to avoid adding the document itself, due to the nsCCUncollectableMarker optimization, or will it pull in some successors of the document too? One thing I want to look into is what exactly the large DOM-y globs that show up in the cycle collector graph actually are. One theory I've had is that we aren't pruning out all visible documents that we should.
(In reply to Andrew McCreight [:mccr8] from comment #1) > Is this just going to avoid adding the document itself, due to the > nsCCUncollectableMarker optimization I think so, yes.