Open Bug 810344 Opened 12 years ago Updated 2 years ago

Memory leak when disabling bootstrapped extension

Categories

(Core :: General, defect)

16 Branch
x86
macOS
defect

Tracking

()

People

(Reporter: matthew.gertner, Unassigned)

References

Details

(Whiteboard: [MemShrink:P3])

Attachments

(2 files)

Attached file Test extension
To reproduce:
1. Install the attached extension.
2. Restart Firefox.
3. Disable the extension.
4. Load about:memory?verbose
5. Search for "salsita".

Result: The test.xul compartment is still in memory.

Note that this problem doesn't seem to occur unless the extension is installed and enabled when Firefox is started. If you install it or enable it while Firefox is running, then the compartment is freed as expected.
Attachment #680090 - Attachment mime type: text/plain → application/x-xpinstall
Whiteboard: [MemShrink]
I did some more analysis and it looks to me like this is definitely related to the <browser type="content" /> in the XUL page opened by the extension. If I remove that or even just remove the type attribute then the leak doesn't occur.
Seems like the same problem occurs if the XUL file references a JS file, even if the JS file is empty (see second test extension attachment).
Attached file Test extension 2
Based on above comments, not an Add-ons Manager bug.
Component: Add-ons Manager → General
Product: Toolkit → Core
Blocks: LeakyAddons
Whiteboard: [MemShrink] → [MemShrink:P3]
Have you tested in a clean profile? How about the same extension, but not bootstrapped?
This sounds a log like bug 759919.
(In reply to Kris Maglione [:kmag] from comment #6)
> This sounds a log like bug 759919.

Yes it looks like the problem does not occur when nglayout.debug.disable_xul_cache is set to true.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: