[
https://issues.apache.org/jira/browse/SPARK-18630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381244#comment-16381244
]
yogesh garg commented on SPARK-18630:
-------------------------------------
I would like to take this. If I understand correctly, moving the `__del__` and
(deep) `copy` methods to `JavaWrapper` should address this potential issue. Is
there a reason why we might not want to do a deep copy of `JavaWrapper` class?
> PySpark ML memory leak
> ----------------------
>
> Key: SPARK-18630
> URL: https://issues.apache.org/jira/browse/SPARK-18630
> Project: Spark
> Issue Type: Bug
> Components: ML, PySpark
> Reporter: holdenk
> Priority: Minor
>
> After SPARK-18274 is fixed by https://github.com/apache/spark/pull/15843, it
> would be good to follow up and address the potential memory leak for all
> items handled by the `JavaWrapper`, not just `JavaParams`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
