660
edits
Electrolysis/Errors and Shutdown: Difference between revisions
Electrolysis/Errors and Shutdown (view source)
Revision as of 03:45, 15 February 2010
, 15 February 2010no edit summary
m (moved Content Processes/Errors and Shutdown to Electrolysis/Errors and Shutdown: Going to unify plugin/tab/mobile/etc e10s planning) |
Johnjbarton (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
When a content process is intentionally no longer needed, it should shut down. In release builds, there is no reason to shut down "cleanly", and the content process can just _abort(). In debug/leaktesting builds, the content process should perform a full shutdown so that leak testing can verify that there are no leaked objects. | When a content process is intentionally no longer needed, it should shut down. In release builds, there is no reason to shut down "cleanly", and the content process can just _abort(). In debug/leaktesting builds, the content process should perform a full shutdown so that leak testing can verify that there are no leaked objects. | ||
Q.jjb ''How will extensions and debuggers know that the content process is exiting in a release build?'' | |||
== IPDL Notifications == | == IPDL Notifications == | ||