canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
XPCOM Shutdown: Difference between revisions
Jump to navigation
Jump to search
m
→XPCOM Shutdown Sequence: better wording
m (→XPCOM Shutdown Sequence: swap prior two columns for readability) |
m (→XPCOM Shutdown Sequence: better wording) |
||
| Line 16: | Line 16: | ||
<th>Main Event Queue | <th>Main Event Queue | ||
<th>Component Manager | <th>Component Manager | ||
<th> | <th>Function calls across components | ||
<tr> | <tr> | ||
| Line 23: | Line 23: | ||
<td rowspan="4">Events accepted | <td rowspan="4">Events accepted | ||
<td rowspan="5">All calls allowed | <td rowspan="5">All calls allowed | ||
<td rowspan="7">Calls across | <td rowspan="7">Calls across components allowed | ||
<tr> | <tr> | ||
| Line 54: | Line 54: | ||
<th><tt>xpcom-loader-shutdown</tt> notification | <th><tt>xpcom-loader-shutdown</tt> notification | ||
<td>Component loaders (except for the binary/static component loaders) should do their final shutdown/cleanup activities, unloading all modules. | <td>Component loaders (except for the binary/static component loaders) should do their final shutdown/cleanup activities, unloading all modules. | ||
<td rowspan="2"> | <td rowspan="2">Function calls across components not allowed | ||
<tr> | <tr> | ||