Closed Bug 99239 Opened 24 years ago Closed 24 years ago

prefs service gets shutdown before other components which would like to use prefs

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: Bienvenu, Assigned: Bienvenu)

Details

See bug 98816 for more details, but things are breaking because the prefs service is getting shut down earlier than it used to. In news, in our shutdown handling, we were writing out the newsrc file, which was breaking because the prefs service had already shut down. Cc'ing Simon, who said said had seen some annoying assert on shutdown that might be related.
Seth suggested filing this on bnesse and cc'ing mitesh, so that's what I'm doing. Is there any way for us to make sure we're shut down before the prefs service?
Assignee: dougt → bnesse
I note that mail/news it holding a reference to a pref branch. http://lxr.mozilla.org/seamonkey/source/mailnews/base/util/nsMsgIncomingServer.cpp#374 I don't fully understand how the prefservice can have been released while this reference exists. Alec, do you have any ideas on this?
The bug that I filed is bug 97240.
we're in the shutdown process, so it doesn't seem to matter that we're still holding a reference to the prefs service. Simon's bug was filed 08/27/01 so this must have changed sometime before then.
prefs can't garantee when it will be shutdown - all services are shut down by XPCOM In any case, it sounds like mail should be using the xpcom-shutdown topic from the observer service to write out the .newsrc.
I don't know what could have caused the shutdown order to change. When I breakpointed the area of code in question, it didn't even hit my breakpoints during shutdown. I don't know if that means I did something wrong, or if it is no longer going through GetNewsrcFilePath() on shutdown... As I can neither control nor dictate the timing of prefs shutdown, I guess this goes back to mail/news.
Assignee: bnesse → bienvenu
resolving as invalid - I fixed the mailnews problem, and your comment is basically that you can't fix it, or rather, that the bug is invalid. I don't agree 100%, but I doubt I'm going to get anywhere.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.