Docshells created when reading mail are not cleaned up until shutdown



MailNews: Message Display
10 years ago
8 years ago


(Reporter: Peter Weilbacher, Unassigned)



Firefox Tracking Flags

(Not tracked)



(1 attachment)



10 years ago
Created attachment 285650 [details]
leak-gauge output

Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a9pre) Gecko/2007102003 SeaMonkey/2.0a1pre

When running with NSPR_LOG_MODULES=DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5 and then running the output through I get the attached result. It seems that all docshells opened by MailNews for the bodies of messages are only cleaned up on shutdown. At the time I ran leak-gauge I only had one browser window open (MailNews closed).

Apart from the OS/2 build quoted above this also happens on Linux with current trunk builds. It does not matter if the messages are read using the message pane or in an extra window, so this is different from bug 399027. Maybe there is a relation to bug 355005 or bug 361235.

In effect, this causes SeaMonkey memory usage for MailNews to always increase and forces the user to restart the app sooner than intended.

Comment 1

8 years ago
Peter, still see this with current 2.0b?
> rv:1.9a9pre) Gecko/2007102003 SeaMonkey/2.0a1pre

Bug 329876 is for "virtual memory size increase(10KB) per a mail view" on MS Windows. It was WORKSFORME with Tb 2007-07-17 build. (I didn't check with Sm builds around 7/17.)
Some changes by Bug 379070 were landed in June/July 2007, and Bug 379070 was finally FIXED on 2008-11-04.

Bug 388353 exists for issue of "leak of resource relates to mail display", and is still open.
> Bug 388353 Displaying a Mail Messages leaks a jsContext & a global window

Comment 3

8 years ago
No, I checked with "Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv: Gecko/20090726 SeaMonkey/2.0b2pre" that I do not see this any more. The MailNews related docshells remain for a few seconds after the last MailNews window was closed, but then they disappear from the leak-gauge output.

Great. :-) --> WFM
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.