Closed
Bug 605294
Opened 15 years ago
Closed 15 years ago
Leak nsGlobalWindow hiding a focused iframe
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | betaN+ |
People
(Reporter: jruderman, Assigned: smaug)
Details
(Keywords: memory-leak, testcase)
Attachments
(2 files)
|
248 bytes,
text/html
|
Details | |
|
2.87 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
1. Load the testcase
2. Quit Firefox
Result: Leak nsGlobalWindow+
If I change focus before quitting, the leak goes away. So this affects fuzzing more than it affects real life. But I'd like to be able to fuzz for leaks ;)
| Reporter | ||
Updated•15 years ago
|
blocking2.0: --- → ?
Comment 1•15 years ago
|
||
Peter, can you have a look?
Assignee: nobody → peterv
blocking2.0: ? → betaN+
Comment 2•15 years ago
|
||
I'm having a hard time reproducing. I managed to make it leak once after trying about 20 times.
| Assignee | ||
Comment 3•15 years ago
|
||
I can reproduce this easily on Linux.
I could take a look.
Assignee: peterv → Olli.Pettay
| Assignee | ||
Comment 4•15 years ago
|
||
When shutting down we should just release the comptrs the singleton owns.
In normal cases focused windows changes all the time, so this isn't a "real"
leak bug.
Attachment #497540 -
Flags: review?(peterv)
| Assignee | ||
Updated•15 years ago
|
Status: NEW → ASSIGNED
Comment 5•15 years ago
|
||
Comment on attachment 497540 [details] [diff] [review]
patch
I don't suppose we could clear these when the iframe is hidden?
Attachment #497540 -
Flags: review?(peterv) → review+
| Assignee | ||
Comment 6•15 years ago
|
||
That is another (open) bug and may be fixed as well. But I think there might
still be cases when we don't clear the variables before shutdown.
| Assignee | ||
Comment 7•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 8•15 years ago
|
||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•