Closed
Bug 749589
Opened 13 years ago
Closed 13 years ago
Less-leaky classinfo for XTF
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Assigned: smaug)
Details
Attachments
(1 file)
|
5.47 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
No description provided.
| Assignee | ||
Comment 1•13 years ago
|
||
Classinfo shouldn't keep the object alive.
| Assignee | ||
Comment 2•13 years ago
|
||
| Assignee | ||
Comment 3•13 years ago
|
||
Comment on attachment 619016 [details] [diff] [review]
WIP
Bill, could you test this?
It should fix the leak you saw where keeping classinfo alive ends up
keeping element alive.
Attachment #619016 -
Flags: review?(jst)
Attachment #619016 -
Flags: feedback?(wmccloskey)
| Assignee | ||
Comment 4•13 years ago
|
||
| Assignee | ||
Comment 5•13 years ago
|
||
Jst, review ping. I believe this block iGC.
Comment 6•13 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #5)
> Jst, review ping. I believe this block iGC.
No, it doesn't. This is just an existing leak that we've ignored for years that Bill happened to notice while investigating IGC leaks, if I understand correctly.
| Assignee | ||
Comment 7•13 years ago
|
||
Oh, I thought iGC+xpcshell tests were leaking because of this.
But anyhow, Bill, you could test this.
| Assignee | ||
Comment 8•13 years ago
|
||
er, could you...
(In reply to Olli Pettay [:smaug] from comment #7)
> Oh, I thought iGC+xpcshell tests were leaking because of this.
They are, but non-iGC+xpcshell are too :-)
Yeah, this fixes the leak. Thanks.
This doesn't block IGC. It's a leak we found while trying to debug the IGC leak. As Rafael said, it leaks on trunk right now.
Updated•13 years ago
|
Attachment #619016 -
Flags: review?(jst) → review+
| Assignee | ||
Updated•13 years ago
|
Attachment #619016 -
Flags: feedback?(wmccloskey)
| Assignee | ||
Comment 11•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•