[
https://issues.apache.org/jira/browse/SPARK-16021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365641#comment-15365641
]
Apache Spark commented on SPARK-16021:
--------------------------------------
User 'zsxwing' has created a pull request for this issue:
https://github.com/apache/spark/pull/14084
> Zero out freed memory in test to help catch correctness bugs
> ------------------------------------------------------------
>
> Key: SPARK-16021
> URL: https://issues.apache.org/jira/browse/SPARK-16021
> Project: Spark
> Issue Type: Improvement
> Reporter: Eric Liang
> Assignee: Eric Liang
> Fix For: 2.1.0
>
>
> In both on-heap and off-heap modes, it would be helpful to immediately zero
> out (or otherwise fill with a sentinel value) memory when an object is
> deallocated.
> Currently, in on-heap mode, freed memory can be accessed without visible
> error if no other consumer has written to the same space. Similarly, off-heap
> memory can be accessed without fault if the allocation library has not
> released the pages back to the OS. Zeroing out freed memory would make these
> errors immediately visible as a correctness problem.
> Since this would add some performance overhead, it would make sense to
> conf-flag and enable only in test.
> cc [~sameerag] [~hvanhovell]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
