Closed Bug 51306 Opened 26 years ago Closed 26 years ago

crash selecting local folder after compacting it

Categories

(MailNews Core :: Backend, defect, P1)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Bienvenu, Assigned: Bienvenu)

Details

(Keywords: crash, Whiteboard: [nsbeta3+][PDTP1]Fix in hand)

I compacted my local inbox, and then tried to open it - I crashed because the db headers being held onto by the nsIMessage's were no longer valid. Not sure when this was broken, or if it ever worked (but I'm guessing it must have worked).
Severity: normal → critical
Status: NEW → ASSIGNED
Keywords: crash, nsbeta3
Priority: P3 → P1
Is this because of the nsMessage recycler, Alec? In theory, we should be getting rid of all the old message resources in this case, because they're all invalid (the msg keys change when we compact). But I suspect that before, they just hung around. Is there an easy way in RDF to get rid of a bunch of resources? Or, I guess I could enumerate over the nsMessage's and clear out their nsIMsgDBHdr pointers before blowing away the old db.
I really don't think so - I didn't change the lifetime of the nsMessage objects or anything yet.. the only thing that HAS changed is the way the messagetype is set - and I think that only affected the RDF display of the message
nsbeta3+, P1.
Whiteboard: [nsbeta3+]
yeah, I don't think we are recycling yet. But it's a good point that when we do recycle we should remember to remove the ref to the msghdr and to the folder.
Keywords: mail4
QA Contact: lchiang → fenella
Target Milestone: --- → M18
right, we're not recycling yet
PDT agrees P1
Whiteboard: [nsbeta3+] → [nsbeta3+][PDTP1]
this is happening because we're leaking nsMsgHdrs (or, really, because the nsXULDocument is leaking, and it's holding onto nsMsgHdrs.)
Whiteboard: [nsbeta3+][PDTP1] → [nsbeta3+][PDTP1]Fix in hand
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Linux (2000-09-11-08 M18) Win32 (2000-09-11-08 M18) Mac (2000-09-08-20 M18) This problem has been fixed.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.