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

StackOverflowError should be considered fatal in scala.util.control NonFatal #7999

Closed
scabug opened this issue Nov 22, 2013 · 1 comment
Closed
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Nov 22, 2013

As mentioned in this thread https://groups.google.com/d/msg/scala-language/eC9dqTTBYHg/Fu-lTp2fTlAJ, the JVM can end up in an inconsistent state after an SOE has occurred.

This should not be considered “non-fatal”. People who know what they do can still use their own SpecialNonFatal type or override the uncaught exception handler to their liking.

@scabug
Copy link
Author

@scabug scabug commented Nov 22, 2013

Imported From: https://issues.scala-lang.org/browse/SI-7999?orig=1
Reporter: @soc
Affected Versions: 2.10.3, 2.11.0-M7

@scabug scabug closed this Nov 23, 2013
@scabug scabug added this to the 2.11.0-M8 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants