Closed
Bug 28409
Opened 25 years ago
Closed 25 years ago
Localstore not being saved in mail
Categories
(Core Graveyard :: RDF, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M15
People
(Reporter: scottputterman, Assigned: waterson)
Details
In today's build, when I change the expand/collapse state of a folder or change
the threaded state of a folder, it is not being saved when I quit. I can see
that localstore.rdf is not being modified. This is only happening when I run
-mailnews. If I startup the browser then it is being saved.
I think this might be happening due to a leak in ~nsXULDocument because I can
see that LocalStoreImpl::Flush() is never being called. Assuming this is the
right code, I wonder if we need some way to save the local store without relying
on a destructor? Possibly doing it onshutdown.
Comment 1•25 years ago
|
||
I agree that doing this in an OnShutdown type method would be good. But when I
run, I am hitting the destructor for the nsXULDocument - I'm just running mail,
and not doing anything fancy (like maybe even reading a message - I should try
that).
Assignee | ||
Comment 2•25 years ago
|
||
Better yet, you could do it in messenger.xul's "onunload" handler. I think that
the browser does it this way.
Should we try to find the leak? (Or at least file a different bug for that?)
Assignee | ||
Comment 3•25 years ago
|
||
wait, you said you *are* hitting nsXULDocument's dtor? mysterious.
Status: NEW → ASSIGNED
Target Milestone: M15
Comment 4•25 years ago
|
||
I'm not seeing Putterman's problem at all - but that's only fair, he's not seeing all my problems either.
Assignee | ||
Comment 5•25 years ago
|
||
putterman: is this still broken?
Reporter | ||
Comment 6•25 years ago
|
||
I haven't seen it recently. Marking WORKSFORME.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 7•24 years ago
|
||
Verified
Platform: PC
OS: Windows 98
Mozilla Build: 2000101020 M18 Trunk Build
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•