Closed
Bug 426963
Opened 16 years ago
Closed 12 years ago
Thunderbird leaks on shutdown
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: memory-leak, meta)
Attachments
(1 file, 1 obsolete file)
4.21 KB,
text/plain
|
Details |
A clean Mac trunk Thunderbird debug build leaks on shutdown, see attached log. Part of the noise in bug 426946.
Reporter | ||
Updated•16 years ago
|
Flags: blocking-thunderbird3?
Comment 1•16 years ago
|
||
The nsVoidArray leak should have already been fixed by bug 424677.
Depends on: 424677
Reporter | ||
Comment 2•16 years ago
|
||
Mark, on the contrary, on a build compiled today, the nsVoidArray leak is still present. All previous leaking objects in the leak log of comment #0 are still leaking as of today's build.
Comment 3•16 years ago
|
||
no evidence that this leak is debilitating, so it doesn't block yet.
Flags: wanted-thunderbird3+
Flags: blocking-thunderbird3?
Flags: blocking-thunderbird3-
Reporter | ||
Comment 4•16 years ago
|
||
Here's an updated leak log from the latest hg pull.
Attachment #313542 -
Attachment is obsolete: true
Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #4) > Created an attachment (id=340731) [details] > updated leak log 2 > > Here's an updated leak log from the latest hg pull. We now leak at more places, such as nsAutoSyncManager, nsTArray_base, nsThread and nsTimerImpl. Fresh profile on Mac 10.5.5 btw.
Comment 6•16 years ago
|
||
(In reply to comment #5) > We now leak at more places, such as nsAutoSyncManager, nsTArray_base, nsThread > and nsTimerImpl. These are all most likely as a result of the nsAutoSyncManager landing, I've raised bug 457452 to cover them.
Comment 7•12 years ago
|
||
I'm going to say this is superseeded by bug 764742/bug 765074. It may be that we never fixed all of these, but we'll continue investigations in the new bugs.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•