Closed
Bug 344545
Opened 18 years ago
Closed 18 years ago
DOM Inspector 1.8.1b1 Leak (dom.js)
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: LouCypher, Assigned: sdwilsh)
Details
Attachments
(2 files, 1 obsolete file)
1.21 KB,
text/plain
|
Details | |
913 bytes,
patch
|
db48x
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 - Build ID: 2006071020 Clean profile Reproducible: Always Steps to Reproduce: 1. Run Firefox 2. Open Error Console 3. Run DOM Inspector 4. From DOM Inspector window, click the "Select Element By Click" button. 5. Close DOM Inspector without selecting any object/element. Actual Results: Error Console will display: Error: viewer is not defined Source File: chrome://inspector/content/viewers/dom/dom.js Line: 1005 Error Console will continue to display the error message until the inspected document/window is closed. On prior version of Firefox (with patched DOMI from bug 3366961) where Leak Monitor is installed and running, Leak Monitor will report memory leaks (see next attachment). Solution: Modify dom.js and edit function DOMViewer_destroy() to: PrefUtils.removeObserver("inspector", PrefChangeObserver); + try { + viewer.removeClickListeners(); + } catch(ex) { + } viewer = null;
Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
Patches accepted, Lou :)
Assignee | ||
Comment 3•18 years ago
|
||
Can someone see if this takes care of it (ie the reporter)? I don't have the extension installed. If this works, I'll request review.
Assignee | ||
Comment 4•18 years ago
|
||
any takers on the whole testing thing?
Assignee | ||
Updated•18 years ago
|
Attachment #230745 -
Flags: review?(db48x)
Assignee | ||
Updated•18 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Updated•18 years ago
|
Assignee: dom-inspector → comrade693+bmo
Status: ASSIGNED → NEW
Comment 5•18 years ago
|
||
Comment on attachment 230745 [details] [diff] [review] v1 r=db48x
Attachment #230745 -
Flags: review?(db48x) → review+
Comment 6•18 years ago
|
||
Unless you can give me steps to reproduce an exception removing the click listeners, I'd only give you sr+ without the try/catch.
Assignee | ||
Comment 7•18 years ago
|
||
Can't figure out why we need the try catch block - no exceptions thrown.
Attachment #230745 -
Attachment is obsolete: true
Attachment #251398 -
Flags: superreview?(neil)
Attachment #251398 -
Flags: review?(db48x)
Comment 8•18 years ago
|
||
Comment on attachment 251398 [details] [diff] [review] v1.1 r=db48x
Attachment #251398 -
Flags: review?(db48x) → review+
Updated•18 years ago
|
Attachment #251398 -
Flags: superreview?(neil) → superreview+
Assignee | ||
Updated•18 years ago
|
Whiteboard: [checkin needed]
Assignee | ||
Comment 9•18 years ago
|
||
Checked in by timeless.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Whiteboard: [checkin needed]
Updated•17 years ago
|
QA Contact: timeless → dom-inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•