Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11805#issuecomment-202616817
Discovered a potentially major problem: if we bail out of a getOrElseUpdate
call and don't end up caching a block and then do not fully consume or dispose
of the resulting valuesIterator then we might leak off-heap memory. This
problem didn't exist before because we'd never use off-heap memory for unroll
space. I may have to add some task completion callbacks to dispose of
PartiallySerializedBlocks.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
