Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.exit may not be sufficient to terminate the forked JVM #133

Open
dweiss opened this issue Oct 27, 2012 · 1 comment
Open

System.exit may not be sufficient to terminate the forked JVM #133

dweiss opened this issue Oct 27, 2012 · 1 comment

Comments

@dweiss
Copy link
Contributor

dweiss commented Oct 27, 2012

Because shutdown hooks and finalizers can block the exiting thread indefinitely. Switch to using Runtime.halt() -- there is not much we can do to prevent finalizers from deadlocking.

@ghost ghost assigned dweiss Oct 27, 2012
@dweiss dweiss closed this as completed in ccc8807 Oct 27, 2012
@dweiss dweiss reopened this Oct 29, 2012
@dweiss
Copy link
Contributor Author

dweiss commented Oct 29, 2012

Even halt won't terminate the JVM if one of the threads is in native code or God knows what other condition holds. We should just ignore those JVMs, possibly firing some message back to the user.

@dweiss dweiss removed this from the 2.1.0 milestone Feb 27, 2014
@dweiss dweiss removed the 2.1.0 label Feb 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant