Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/783#issuecomment-43163719
@marmbrus The whole point of this function was to catch and print
Throwable. It is intended to be used in places where the exception would
otherwise be silently masked, such as the outermost scope of a Thread's run()
method.
@pwendell AFAIK, Throwables are not necessarily printed anywhere. OOMs and
StackOverflowErrors tend to behave like normal exceptions that can just appear
in unusual places, so they can be masked. You can ask Java to heap dump on OOM,
or to run arbitrary code with `-XX:OnOutOfMemoryError`, but by default nothing
special happens. The JVM can even recover from an OOM if a thread death allows
sufficient GC to occur, but we do not expect that Spark is in a healthy state
after something like that happens.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
