Open
Bug 916078
(AsyncShutdown)
Opened 11 years ago
Updated 2 years ago
[meta][Async shutdown] Make asynchronous services shutdown-safe
Categories
(Toolkit :: Async Tooling, defect)
Toolkit
Async Tooling
Tracking
()
NEW
People
(Reporter: Yoric, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
(Keywords: meta)
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.
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Component: General → Async Tooling
Reporter | ||
Updated•11 years ago
|
Alias: AsyncShutdown
Whiteboard: [Async][Async Shutdown]
Updated•11 years ago
|
Whiteboard: [Async][Async Shutdown]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•