Bug 916078 (AsyncShutdown)

[meta][Async shutdown] Make asynchronous services shutdown-safe




5 years ago
3 months ago


(Reporter: Yoric, Unassigned)


(Depends on: 2 bugs, Blocks: 2 bugs, {meta})

Firefox Tracking Flags

(Not tracked)



Bug 911820 demonstrates that we currently do not shutdown all services in a shutdown-safe way. In this case, some writes may started too late and be interrupted while in progress, causing data loss. Examining some parts of the code seems to indicates that attempts to avoid such data loss results in code that may deadlock.

Opening this bug to track the effort on making our services shutdown-safe:
- every service that performs asynchronous operations must have the opportunity to call the services from which it depends before they become unavailable;
- such calls must not cause deadlocks.
Depends on: 916729
Depends on: 917764
Component: General → Async Tooling
Depends on: 918317
Depends on: 918798
Depends on: 859695
Alias: AsyncShutdown
Whiteboard: [Async][Async Shutdown]


5 years ago
Whiteboard: [Async][Async Shutdown]
Depends on: 983571
Depends on: 801598
Depends on: 966253
Depends on: 984879
Depends on: 1017706
Depends on: 917883
Depends on: 1008944
Depends on: 853549
Depends on: 1016831
Depends on: 940408
Depends on: 967203
Depends on: 1008148
Depends on: 985655
Depends on: 952543


4 years ago
Depends on: 1121130
Keywords: meta
You need to log in before you can comment on or make changes to this bug.