Closed Bug 17745 Opened 25 years ago Closed 25 years ago

After reading mail, one webshell is leaked.

Categories

(SeaMonkey :: MailNews: Message Display, defect, P1)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jar, Assigned: travis)

Details

(Keywords: memory-leak)

I noticed that my system uses up memory when I click on the "read/unread" column in my mail subject pane (top right pane on the 3 pane interface). The memory gets used whether I click on the little dot and turn it green (marking the message unread), or click on the green dot to turn it grey (marking the message read). I think this is part of why I can't use the product for too long... I get and read too many messages... and it uses up all my memory. If this isn't a classical "Leak," then the space team should at least understand what datastructure is growing by such large jumps. I'm running today's build (pulled ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/1999-11-01-09-M11/) Thanks, Jim
Assignee: phil → dougt
This is a side effect leaking a web shell per iframe, which was tracked down to a reference counting issue in the autoproxy stuff. Reassigning to dougt.
Status: NEW → ASSIGNED
accepting.
marking as m12.
Putting on PDT+ radar.
Whiteboard: [PDT+]
Assignee: dougt → phil
Status: ASSIGNED → NEW
Summary: [Dogfood] Leak or use one meg of memory with each click during mail reading → After reading mail, one webshell is leaked.
After my changes, I am only see one webshell leak from mailnews. 1. open mozilla.org 2. load www.mozilla.org 3. quit Note that there are three webshell that are leaked. 1. open mozilla.org 2. load www.mozilla.org 3. open mail/imap 4. look at a bunch of mail. 5. quit. Note that there are 4 webshell leaks. This is no longer a proxy problem (i thing), reassigning to phil@netscape.com.
Assignee: phil → waterson
waterson, word is you have M12 stuff which fixes this. If not, please reassign back to me.
Status: NEW → ASSIGNED
Priority: P3 → P1
sounds good.
Summary: After reading mail, one webshell is leaked. → [DOGFOOD] After reading mail, one webshell is leaked.
Waterson, if you haven't already fixed this, I, scc or Robert can take this. For the record, dougt's changes never landed. These are essential for driving leaked webshells to zero.
Assignee: waterson → dp
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] week ending 11/28
Blocks: 18951
Summary: [DOGFOOD] After reading mail, one webshell is leaked. → After reading mail, one webshell is leaked.
Whiteboard: [PDT+] week ending 11/28
I just regressed this bug at the PDT meeting. The gross and ongoing leak (1 meg per click) is definately fixed. Per discussion with DP and the PDT team, we're changing this to a PDT- now. It probably isn't dogfood in this state by any measure... and since I submitted it... I'm pulling the dogfood comment.
Target Milestone: M12 → M14
Assignee: dp → travis
Status: ASSIGNED → NEW
Travis, some old webshell leak bug. Dont even know if this is relevant. Hope you would know.
Keywords: mlk
I don't see this. Most likely it has been fixed with other changes that have been made. Marking works for me.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
No longer blocks: 18951
Keywords: verifyme
such an old bug. marking verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.