Closed
Bug 350326
Opened 18 years ago
Closed 6 years ago
Venkman debugger leaks when closing
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Other Applications Graveyard
Venkman JS Debugger
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bugzilla, Assigned: rginda)
References
Details
(Keywords: memory-leak)
D. Baron's Leak Monitor 0.3.4 will report a leakage in
onExecute (2900750, chrome://venkman/content/venkman-debugger.js, 248-340) = function jsdExecutionHook(frame, type, rv)
when closing Venkman Javascript Debugger v. 0.9.87.
Steps to reproduce:
1- Load any page (even an about:blank) in Bon Echo 2.0b2
2- Open up the latest Venkman Javascript Debugger 0.9.87
3- Close Venkman
Actual results:
Leaks in window 0x2787378:
[+] [leaked object] (3672fa8) = [object Object]
[+] onExecute (2900750, chrome://venkman/content/venkman-debugger.js, 248-340) = function jsdExecutionHook(frame, type, rv) {
dd("execution hook: " + formatFrame(frame));
var hookReturn = jsdIExecutionHook.RETURN_CONTINUE;
etc...
Reproducible: Always
In Firefox 2.0b2 rv:1.8.1b2 build 20060825 BonEcho 2.0b2
under XP Pro SP2
Notes
=====
- I searched for a duplicate and did not find any.
- I'm letting someone else more competent than I the liberty to confirm this one
- I set Version to 2.0 branch; change it if necessary/wrong
- mlk keyword added
Reporter | ||
Updated•18 years ago
|
Flags: blocking-firefox2?
Updated•18 years ago
|
Assignee: nobody → rginda
Component: General → JavaScript Debugger
Flags: blocking-firefox2?
Product: Firefox → Other Applications
QA Contact: general → caillon
Version: 2.0 Branch → 1.8 Branch
Comment 1•18 years ago
|
||
The second leaked object is already fixed in bug 336680; the first one is known but currently unfixable.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: 1.8 Branch → Trunk
Comment 2•18 years ago
|
||
Silver: could you explain why this first leak is unfixable?
Comment 3•18 years ago
|
||
Because no-one has been able to identify what is leaking it. We know exactly what object is being leaking (the <browser>'s XBL binding), but no idea where or how.
Comment 4•6 years ago
|
||
Component is obsolete so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•