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)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M14
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
Updated•25 years ago
|
Assignee: phil → dougt
Comment 1•25 years ago
|
||
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.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 2•25 years ago
|
||
accepting.
Comment 3•25 years ago
|
||
marking as m12.
Updated•25 years ago
|
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.
Comment 5•25 years ago
|
||
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.
Updated•25 years ago
|
Assignee: phil → waterson
Comment 6•25 years ago
|
||
waterson, word is you have M12 stuff which fixes this. If not, please reassign
back to me.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Priority: P3 → P1
Comment 7•25 years ago
|
||
sounds good.
Updated•25 years ago
|
Summary: After reading mail, one webshell is leaked. → [DOGFOOD] After reading mail, one webshell is leaked.
Comment 8•25 years ago
|
||
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.
Updated•25 years ago
|
Assignee: waterson → dp
Status: ASSIGNED → NEW
Updated•25 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+] week ending 11/28
Reporter | ||
Updated•25 years ago
|
Summary: [DOGFOOD] After reading mail, one webshell is leaked. → After reading mail, one webshell is leaked.
Whiteboard: [PDT+] week ending 11/28
Reporter | ||
Comment 9•25 years ago
|
||
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.
Updated•25 years ago
|
Target Milestone: M12 → M14
Updated•25 years ago
|
Assignee: dp → travis
Status: ASSIGNED → NEW
Comment 10•25 years ago
|
||
Travis, some old webshell leak bug. Dont even know if this is relevant. Hope
you would know.
Assignee | ||
Comment 11•25 years ago
|
||
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
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•