Closed
Bug 699799
Opened 13 years ago
Closed 13 years ago
Don't AddRef/Release every uncollectable document before cycle collection
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: peterv, Assigned: peterv)
Details
Attachments
(1 file)
887 bytes,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
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).
Attachment #571971 -
Flags: review?(jst)
Updated•13 years ago
|
Attachment #571971 -
Flags: review?(jst) → review+
Comment 1•13 years ago
|
||
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.
Assignee | ||
Comment 2•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/1aab8b1485dd
Target Milestone: --- → mozilla10
Assignee | ||
Comment 3•13 years ago
|
||
(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.
Comment 4•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1aab8b1485dd
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•