Closed Bug 65377 Opened 24 years ago Closed 7 years ago

Leak when removing browser xbl binding

Categories

(Core :: XBL, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE
Future

People

(Reporter: jag+mozbugs, Unassigned)

Details

(Keywords: memory-leak)

Attachments

(1 file)

I'll attach a nav.xul (nearly the same one as on bug 60729, but without the navigator.css stylesheet), which leaks when I remove the xbl binding for the <browser/> tag. Not sure where to file this... Put nav.xul in chrome/comm/content/navigator/, and start mozilla with $ mozilla -chrome chrome://navigator/content/nav.xul Be sure to don't have JARring on, or edit installed-chrome.txt and remove "jar:" and ".jar!" from all lines. When I remove these three lines from chrome/toolkit/content/global/xul.css, I see the leak: This selector (line 27): *[collapsed="true"], From slider (line 497): -moz-binding: url("chrome://global/content/xulBindings.xml#slider"); From browser (line 98): -moz-binding: url(chrome://global/content/xulBindings.xml#browser); I need to remove the first two for bug 60729, I don't know how relevant they are to this leak otherwise. Removing the third line causes the leak to show up for me. It seems to be a different leak than the one in 60729, based on leak log output.
Attached file [testcase] nav.xul (deleted) —
->future
Target Milestone: --- → Future
Assignee: hyatt → nobody
Keywords: mlk
QA Contact: jrgmorrison → xbl
Carsten, can you confirm?
Keywords: qawanted
Removing QAwanted since it was added without a specific request. Please re-add it if this is still an issue and specify what you need from QA.
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: