LME reports a transient memory leak when closing 3-Pane window, with these steps

RESOLVED INCOMPLETE

Status

--
minor
RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: sgautherie, Unassigned)

Tracking

(Blocks: 1 bug, {memory-leak})

Trunk
x86
Windows 2000
memory-leak
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [onhold:reporter] [closeme 2010-08-25])

(Reporter)

Description

11 years ago
This is with my "usual" profile,
but not reproducible with dumb Pop3 or Imap4 account profiles.

Moving here from bug 365723 comment 13,
as Unconfirmed until I narrow the (profile) triggering cause.

NB:
Leak Monitor extension v0.4.2 reports Leak + Reclaim.
I'd like to avoid this annoyance,
but it's not an actual memory leak otherwise.


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.1pre) Gecko/2008062803 Thunderbird/3.0a2pre] (nightly) (W2Ksp4)

1. Start Thunderbird.
2. Open Error Console.
   [To have another window.]
3. F8 (Close Message Pane)
   [Only to confirm that Message Pane (content) is not a trigger.]
3. Select a (empty) folder.
4. Ctrl+W (Close 3-pane window), or Alt+F4.
4r. Wait a little, then get leak (and later reclaim):
{{
Leaks in window 0x2ca09a0:
[ ] [leaked object] (2ca09a0) = [ChromeWindow]

Leaks in window 0x2ca0aa0:
[ ] [leaked object] (2ca0aa0) = [ChromeWindow]
[ ] [leaked object] (33a31c0, chrome://global/content/charsetOverlay.js, 240-245) = [Function]
[ ] [leaked object] (2cf0b80, chrome://messenger/content/msgMail3PaneWindow.js, 1363-1373) = [Function]
[ ] [leaked object] (32316e0, chrome://messenger/content/threadPane.js, 43-88) = [Function]
}}
(Reporter)

Updated

11 years ago
Blocks: 442482
(Reporter)

Comment 1

11 years ago
(In reply to comment #0)
> but not reproducible with dumb Pop3 or Imap4 account profiles.

Of course, it can ... after installing LME :->
(Reporter)

Updated

11 years ago
Depends on: 442569

Updated

10 years ago
Whiteboard: [onhold:reporter]
Serge shall we keep this one open ?
see comment #2
Whiteboard: [onhold:reporter] → [onhold:reporter] [closeme 2010-08-25]
RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this bug was in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.