You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a discussion with a user today who apparently thought that uncaughtException event could be used as a reliable way to restart the application on a crash (after the cleanup and termination). Or that's how I understood what he told me.
The documentation for uncaughtException already has a long and expressive warning noting that the process must not be continued after receiving that exception (ref).
Perhaps it should also explicitly note that the application could crash in ways that do not trigger this event, and that if one wants to restart the process in a guaranteed way — an external watcher should be used.
The text was updated successfully, but these errors were encountered:
ChALkeR
added
doc
Issues and PRs related to the documentations.
process
Issues and PRs related to the process subsystem.
labels
Apr 15, 2016
State in the documentation that `uncaughtException` is not a reliable
way to restart a crashed application, and clarify that an application
may crash in ways that do not trigger this event.
Use a documented synchronous function in example code.
Fixes: #6223
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #6378
State in the documentation that `uncaughtException` is not a reliable
way to restart a crashed application, and clarify that an application
may crash in ways that do not trigger this event.
Use a documented synchronous function in example code.
Fixes: #6223
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #6378
I had a discussion with a user today who apparently thought that
uncaughtException
event could be used as a reliable way to restart the application on a crash (after the cleanup and termination). Or that's how I understood what he told me.The documentation for
uncaughtException
already has a long and expressive warning noting that the process must not be continued after receiving that exception (ref).Perhaps it should also explicitly note that the application could crash in ways that do not trigger this event, and that if one wants to restart the process in a guaranteed way — an external watcher should be used.
The text was updated successfully, but these errors were encountered: