Closed
Bug 51306
Opened 26 years ago
Closed 26 years ago
crash selecting local folder after compacting it
Categories
(MailNews Core :: Backend, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M18
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).
| Assignee | ||
Updated•26 years ago
|
| Assignee | ||
Comment 1•26 years ago
|
||
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.
Comment 2•26 years ago
|
||
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
Comment 4•26 years ago
|
||
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.
Comment 5•26 years ago
|
||
right, we're not recycling yet
| Assignee | ||
Comment 7•26 years ago
|
||
this is happening because we're leaking nsMsgHdrs (or, really, because the
nsXULDocument is leaking, and it's holding onto nsMsgHdrs.)
| Assignee | ||
Updated•26 years ago
|
Whiteboard: [nsbeta3+][PDTP1] → [nsbeta3+][PDTP1]Fix in hand
| Assignee | ||
Comment 8•26 years ago
|
||
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
Updated•21 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•