Closed
Bug 826143
Opened 12 years ago
Closed 4 years ago
Shutdown by _exit(0) for faster shutdown
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1606879
People
(Reporter: espindola, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
No description provided.
|
Reporter | |
Comment 1•12 years ago
|
||
Once bug 662444 is fixed, we should make some effort to find all cases that depend on exit being called (destructors, atexit functions, etc).
If for some reason there are OS libraries that depend on exit being called, we should try to at least remove as many of our own destructors as we can from the fast shutdown path.
|
||
Updated•11 years ago
|
Blocks: shutdown-faster
Keywords: perf
Summary: Shutdown by _exit(0) → Shutdown by _exit(0) for faster shutdown
|
||
Updated•11 years ago
|
Assignee: respindola → nobody
| Comment hidden (obsolete) |
| Comment hidden (obsolete) |
| Comment hidden (obsolete) |
|
||
Comment 6•4 years ago
|
||
Chrome is changing its Windows process shutdown from using exit() to TerminateProcess() (to avoid running destructors for C++ global objects):
https://chromium-review.googlesource.com/c/chromium/src/+/2598043
|
||
Comment 7•4 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #6)
Chrome is changing its Windows process shutdown from using exit() to TerminateProcess() (to avoid running destructors for C++ global objects):
_exit also doesn't run destructors. (_exit != exit)
|
||
Comment 8•4 years ago
|
||
Bug 1606879 has more recent activity, so I'll dupe this over to that.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•