You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2017/02/23 19:36:44 UTC
[jira] [Updated] (SPARK-17822) JVMObjectTracker.objMap may leak JVM
objects
[ https://issues.apache.org/jira/browse/SPARK-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph K. Bradley updated SPARK-17822:
--------------------------------------
Target Version/s: 2.1.0, 2.0.3 (was: 2.0.3, 2.1.1, 2.2.0)
> JVMObjectTracker.objMap may leak JVM objects
> --------------------------------------------
>
> Key: SPARK-17822
> URL: https://issues.apache.org/jira/browse/SPARK-17822
> Project: Spark
> Issue Type: Bug
> Components: SparkR
> Reporter: Yin Huai
> Assignee: Xiangrui Meng
> Fix For: 2.0.3, 2.1.0
>
> Attachments: screenshot-1.png
>
>
> JVMObjectTracker.objMap is used to track JVM objects for SparkR. However, we observed that JVM objects that are not used anymore are still trapped in this map, which prevents those object get GCed.
> Seems it makes sense to use weak reference (like persistentRdds in SparkContext).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org