Skip to content

uncaughtException documentation should mention that it not a reliable «restart on crash» method #6223

Closed
@ChALkeR

Description

@ChALkeR

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    docIssues and PRs related to the documentations.processIssues and PRs related to the process subsystem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions