The account manager dialog appearantly exposes some kind of huge style leak. To reproduce,open Messenger, then go to Edit->Account Setup - now click around all the options in the tree alot - this makes pages reload in the IFRAME on the right. I'm assigning to ramiro because he said I was going to file a bug against it, and he knows where the leaks are.
Adding peterl to the CC because he's the style god...and bruce 'cause he's the leakmaster. It seems to have something to do with loading content in an IFRAME. another good test is to go to http://www.mozilla.org/mailnews/purify/ and click on one of the logs - these are VERY large (4-5Megs) so they take a long time to load, but they're worth it. Once loaded, do a search for any function or fraction thereof. the search will also take a long time, but on Linux the process grows by about 1 meg ever 1-2 seconds during the search...during one search I leaked about 60 Megs!
I believe the style leaks refered to in this bug have been fixed. Reassign to peterl for marking fixed.
Please verify that the leaks are gone...
It is mostly fixed. The huge leaks can't be reproduced with the 2 test cases described here (the "Account Setup" dialog or the "mailnews/purify" page). However we still have some small leaks (a few hundred bytes) with some form controls, especially the drop-down list. I don't know yet whether these leaks come from the style system or from the widget itself. Anyhow, the bug isn't as critical as it was.
To reproduce, go to a bug page like this one and click on one of the popup menus.
Pushing my M15 bugs to M16
Block-moved memory leaks to attinasi
Assignee: pierre → attinasi
Status: ASSIGNED → NEW
I cannot duplicate this, it must have been fixed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Mark or firstname.lastname@example.org: I am unable to verify leaks. Could one of you please marked this as verified? Thanks
Whiteboard: 4/24: requested verification by reporter or assigned eng.
Adding 'verifyme' keyword
No response from reporter. Verifying bug fixed. Please reopen if there still is a problem
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.