Confirmed users
157
edits
XPCOM Shutdown: Difference between revisions
Jump to navigation
Jump to search
→XPCOM Shutdown Sequence
(restore table end-tag) |
|||
| Line 19: | Line 19: | ||
<th>Component Manager | <th>Component Manager | ||
<th>Function calls across components | <th>Function calls across components | ||
<tr> | |||
<th><tt>xpcom-will-shutdown</tt> notification | |||
<td>Notification of the coming xpcom shutdown... during this topic observers can mark themselves as being destroyed, but they must not spin event loop. | |||
<td rowspan="5">Events accepted | |||
<td rowspan="6">All calls allowed | |||
<td>No event loop spinning | |||
<tr> | <tr> | ||
<th><tt>xpcom-shutdown</tt> notification | <th><tt>xpcom-shutdown</tt> notification | ||
<td>Initial notification of xpcom shutdown... during this observer topic all primary modules should begin shutdown and should release any root references. | <td>Initial notification of xpcom shutdown... during this observer topic all primary modules should begin shutdown and should release any root references. | ||
<td rowspan="7">Calls across components allowed | <td rowspan="7">Calls across components allowed | ||