Closed
Bug 303839
Opened 19 years ago
Closed 19 years ago
Leaking webshell/domWindow
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: mikepinkerton, Assigned: sfraser_bugs)
References
Details
(Keywords: fixed1.8, memory-leak, regression)
Attachments
(1 file, 1 obsolete file)
4.15 KB,
patch
|
bryner
:
review+
bzbarsky
:
superreview+
asa
:
approval1.8b4+
|
Details | Diff | Splinter Review |
We're leaking a dom window every time you close the browser window. Not sure
when this regressed.
cc'ing jst in case it's more fallout from the split-window bug.
Reporter | ||
Updated•19 years ago
|
Target Milestone: --- → Camino0.9
Updated•19 years ago
|
Blocks: splitwindows
Assignee | ||
Comment 1•19 years ago
|
||
Firefox is leaking 2 dom windows for each main window that you create and then
close.
Reporter | ||
Comment 2•19 years ago
|
||
well then!
Assignee: pinkerton → general
Component: General → DOM
Flags: camino0.9?
Product: Camino → Core
QA Contact: ian
Target Milestone: Camino0.9 → ---
Version: unspecified → Trunk
Reporter | ||
Updated•19 years ago
|
Severity: normal → blocker
Flags: blocking1.8b4?
Comment 3•19 years ago
|
||
JST - Split window related?
Assignee: general → jst
Flags: blocking1.8b4? → blocking1.8b4+
Comment 4•19 years ago
|
||
Hmm. Seems like Mac only, or anyone see this on non-Mac platforms?
Comment 5•19 years ago
|
||
Ok, I actually do see this on win32 and linux as well. This is a leak that crept
in *after* the splitwindow landing, when that change landed, we didn't leak a
single window object after starting firefox and opening another window, and then
closing firefox.
OS: MacOS X → All
Hardware: Macintosh → All
Comment 6•19 years ago
|
||
I see us leaking one document object, the URL loaded into the leaked document is
"chrome://browser/content/feedview/feedview.xsl". There's no JS reference to
that document, so it seems like a leak through C++ code somewhere... digging
deeper...
Might be related to bug 303043.
Also see bug 303043 comment 8.
Assignee | ||
Comment 8•19 years ago
|
||
Would we get this feedview stuff in Camino?
Comment 9•19 years ago
|
||
No idea...
Comment 10•19 years ago
|
||
The feedview leaks have been fixed on the trunk and branches, does this leak
still exist in Camino?
Assignee | ||
Comment 11•19 years ago
|
||
I still see one nsGlobalWindow leaked per main window in Camino when loading a
simple page.
After heavy browsing sessions, I've seen 50-60 windows leaked.
Comment 12•19 years ago
|
||
Someone needs to enable GC_MARK_DEBUG to start with to see if we're leaking due
to JS references not being torn down or if it's a C++ leak somewhere. That'd be
where I'd start. Feel free to take this bug, I won't be able to get to a place
where I can debug this any time soon. I can help whoever takes on the task of
finding where this leak is tho...
Comment 13•19 years ago
|
||
Simon - is it possible for you to take a swag at this?
Assignee: jst → sfraser_bugs
Assignee | ||
Comment 14•19 years ago
|
||
We're leaking webshells, which entrain dom windows.
I think it may be attributable to this change:
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/cvsroot&subdir=mozilla/embedding/browser/webBrowser&command=DIFF_FRAMESET&file=nsWebBrowser.cpp&rev2=1.152&rev1=1.151
which bryner made.
Summary: Leaking domWindow → Leaking webshell/domWindow
Assignee | ||
Comment 15•19 years ago
|
||
It looks like we have a ref cycle between nsSecureBrowserUIImpl and docShell,
which I don't see being broken anywhere.
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 16•19 years ago
|
||
This patch breaks the ref cycle between the secureBrowserUI/docShell/domWindow.
I'm not sure if this is the best solution.
Assignee | ||
Updated•19 years ago
|
Blocks: blazinglyfastback
Assignee | ||
Comment 17•19 years ago
|
||
Attachment #193596 -
Attachment is obsolete: true
Attachment #193614 -
Flags: superreview?(bzbarsky)
Attachment #193614 -
Flags: review?(bryner)
Updated•19 years ago
|
Attachment #193614 -
Flags: review?(bryner) → review+
Comment 18•19 years ago
|
||
Seems like this had nothing to do with the split window changes. Updating
dependencies...
No longer blocks: splitwindows
Comment 19•19 years ago
|
||
Comment on attachment 193614 [details] [diff] [review]
Better patch
Thanks, Simon!
Attachment #193614 -
Flags: superreview?(bzbarsky) → superreview+
Assignee | ||
Comment 20•19 years ago
|
||
Comment on attachment 193614 [details] [diff] [review]
Better patch
This needs to be fixed on the branch too.
Attachment #193614 -
Flags: approval1.8b4?
Updated•19 years ago
|
Attachment #193614 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 21•19 years ago
|
||
Checked into the trunk and branch.
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
•