Closed
Bug 336973
Opened 18 years ago
Closed 17 years ago
Message window leaks (newsgroups)
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 365723
People
(Reporter: JasnaPaka, Assigned: ispiked)
Details
(Keywords: memory-leak)
Attachments
(1 file, 1 obsolete file)
33.43 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060506 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060506 Minefield/3.0a1 version 2 alpha 1 (20060506) Reproducible: Always Steps to Reproduce: 1. Install Leak Monitor Extension (http://dbaron.org/mozilla/leak-monitor/). 2. Close Thunderbird. 3. Open Thunderbird, open exists message in new window, close this window. Actual Results: Leak dialog is showed.
Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
Note: From this image report, the 'enigmail' leaks should be ignored, at least until the "core" ones are dealt with.
Depends on: 339438
Version: unspecified → Trunk
Assignee | ||
Updated•18 years ago
|
Component: General → Message Compose Window
OS: Windows XP → All
QA Contact: general
Hardware: PC → All
Assignee | ||
Comment 3•18 years ago
|
||
Nulling out msgWindow.msgHeaderSink takes care of securityInfo, too, but it's still appropriate to release this.
Assignee | ||
Updated•18 years ago
|
Attachment #224019 -
Flags: review? → review?(bienvenu)
Comment 4•18 years ago
|
||
Comment on attachment 224019 [details] [diff] [review] fix I'm fine with this - however, Neil was looking at an alternative fix. It would be nice to add a comment here as well as to why we need to null this out.
Attachment #224019 -
Flags: review?(bienvenu) → review+
Comment 5•18 years ago
|
||
(See bug 339072 for its SeaMonkey counterpart.)
This was a false positive, and the report will no longer appear in Leak Monitor 0.3.0.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 7•18 years ago
|
||
(In reply to comment #6) > This was a false positive, and the report will no longer appear in Leak Monitor > 0.3.0. dbaron, no leak report in POP3 account but with newsgroups there is still this reported problem with Leak Monitor 0.3. Steps to Reproduce: 1. Choose View -> Threads -> Collapse All Threads. 2. Select thread with answers. 3. Open message in window. 4. Close window. Reproducibility: Happens sometimes.
Is it the same objects leaking? If so, reopen this bug or file a new one; if not, definitely file a new one.
Reporter | ||
Comment 9•18 years ago
|
||
(In reply to comment #8) > Is it the same objects leaking? Yes, same objects.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Summary: Message window leaks → Message window leaks (newsgroups)
Assignee | ||
Comment 10•18 years ago
|
||
Pavel, can you still reproduce this in a current trunk build?
Reporter | ||
Comment 11•18 years ago
|
||
(In reply to comment #10) > can you still reproduce this in a current trunk build? Yes, same result with latest trunk build. I used Leak Monitor 0.3.4.
Updated•17 years ago
|
QA Contact: message-compose
Comment 12•17 years ago
|
||
Pavel, you still get same leak results with trunk?
Severity: normal → major
Reporter | ||
Comment 13•17 years ago
|
||
Now all works fine. No leak report with latest trunk.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 17 years ago
Resolution: --- → WORKSFORME
Comment 14•16 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.1pre) Gecko/2008062602 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) Eventually, it turned out to be: R.Duplicate, per bug 365723 comment 11. [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.1pre) Gecko/2008062615 SeaMonkey/2.0a1pre] (SEA-WIN32-TBOX-trunk) (W2Ksp4)
Component: Message Compose Window → Mail Window Front End
No longer depends on: 339438
QA Contact: message-compose → front-end
Resolution: WORKSFORME → DUPLICATE
Updated•16 years ago
|
Attachment #224019 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•