Closed Bug 73790 Opened 23 years ago Closed 23 years ago

compacting POP folders leaks prodigious amounts of memory

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.1

People

(Reporter: Bienvenu, Assigned: Bienvenu)

Details

(Whiteboard: [nsbeta1+]) 

Compacting a large pop folder seems to leak about 50K of memory a second. Not
sure why this is, but it should be investigated.
nominating
Keywords: nsbeta1
OS: Windows NT → All
Hardware: PC → All
Priority: -- → P2
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.9
That sounds bad. marking nsbeta1+
QA Contact: esther → huang
Target Milestone: mozilla0.9 → mozilla0.9.1
probably related to bug 73790
Status: NEW → ASSIGNED
this is bug 73790!
yeah, just call me mr. tautology. I meant bug 76118
bienvenu, dup?
there are separate fixes for the two problems (I rewrote compact not to do a
commit on every message copied in the compaction process), so I'd rather not
make it a dup.
fix checked in as part of reworking multiple local msg move/copy and bug 76118
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
POP -> Sheela
QA Contact: huang → sheelar
Summary: compacting folders leaks prodigious amounts of memory → compacting POP folders leaks prodigious amounts of memory
Stephen, I am reassigning this bug to you as per our conversation. Thanks.
QA Contact: sheelar → stephend
Stephen, you can verify this with the windows task manager performance tab. You
don't need purify for it.
Verified Fixed.  Memory usage fluctuated from 110300k to 110720k, but once the
operation was complete, hovered right around 110300k (which is what I began
with).  Build 2001051604 on Windows 2000.  I had 569 messages, most of which
were 5k.
Status: RESOLVED → VERIFIED
And just for posterity, I did the same things with a 2075 message folder (again,
about 5-7k per message).
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.