184
edits
Snappy/AsyncShutdown: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 37: | Line 37: | ||
It is important to note that FHR does not schedule any new I/O during shutdown - it merely completes what was already initiated pre-shutdown. | It is important to note that FHR does not schedule any new I/O during shutdown - it merely completes what was already initiated pre-shutdown. | ||
= Work in Progress = | |||
== AsyncShutdown.jsm == | |||
As part of [bug 913899](https://bugzilla.mozilla.org/show_bug.cgi?id=913899), we are introducing an experimental version of AsyncShutdown.jsm, a module designed to make shutdown dependencies more explicit. | |||
AsyncShutdown defines one main primitive, |addBlocker|, which may be used to prevent shutdown from moving past a given stage until some conditions have been satisfied. At the moment, this mechanism is implemented by spinning the event loop intelligently (i.e. only one loop spinning per shutdown phase). | |||
Future developments: Stabilizing, adding support for debugging, adding support for C++ code, applying this to all the JS code on m-c, making public. | |||
= Related bugs = | = Related bugs = | ||