Closed
Bug 1929133
Opened 1 year ago
Closed 1 year ago
Change nsMsgAccountManager shutdown to use AsyncShutdown instead of listening for notifications
Categories
(MailNews Core :: General, task)
MailNews Core
General
Tracking
(thunderbird_esr128 wontfix, thunderbird133 wontfix)
RESOLVED
FIXED
134 Branch
People
(Reporter: darktrojan, Assigned: darktrojan)
References
Details
Attachments
(1 file)
Account manager shutdown is a hot mess. There are two stages, CleanupOnExit, which is triggered by quit-application-granted or the removal of the last message window for some odd reason, and Shutdown triggered by profile-before-change, or xpcom-shutdown, or the class's destructor.
What it should do, is hook up to the async shutdown service, so not only is it notified about shutdown progress, it can block further progress until ready. Then we could be more sure of what is happening and in what order.
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
status-thunderbird_esr128:
--- → wontfix
Keywords: checkin-needed-tb
Target Milestone: --- → 134 Branch
Pushed by john@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/50f31e166660
Change nsMsgAccountManager shutdown to use AsyncShutdown. r=BenC
| Assignee | ||
Updated•1 year ago
|
status-thunderbird133:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•