Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15916
Of course it is not actually a real memory leak because the memory is
released at the end by calling `taskMemoryManager.cleanUpAllAllocatedMemory` in
`Executor`. But with `spark.unsafe.exceptionOnMemoryLeak` as true by default,
we will see the exception.
Or we just need to turn `spark.unsafe.exceptionOnMemoryLeak` to false by
default?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
