Closed
Bug 693312
Opened 13 years ago
Closed 2 years ago
browser chrome leak while removing specialpowers extension
Categories
(Core :: DOM: Content Processes, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jmaher, Unassigned)
References
Details
(Whiteboard: [specialpowers])
it seems that we have a leak when we fiddle too much with special powers. Right now it seems that if we do not install the specialpowers extension (http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#532) for chrome/a11y/browser-chrome then we run into this. The harness and tools will support this with minimal editing, but we get a leak 75%+ of the time. This delayed landing a series of patches in August/September and this bug should be used to track fixing the issue.
Adding bmoss and jst so they can keep abreast of our efforts to hunt down this leak. For context and debugging patches see bug 621363.
Updated•10 years ago
|
Component: IPC → DOM: Content Processes
Comment 2•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Comment 3•2 years ago
|
||
Hi Joel! I'd assume that we have a quite sophisticated reporting of leaks these days such that this not-very-specific bug is not needed anymore?
Flags: needinfo?(jmaher)
Reporter | ||
Comment 4•2 years ago
|
||
thanks for bringing this up
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(jmaher)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•