You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org> on 2012/10/01 21:21:07 UTC
[jira] [Resolved] (PIG-2917) SpillableMemoryManager memory leak for
WeakReference
[ https://issues.apache.org/jira/browse/PIG-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy resolved PIG-2917.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.11
patch committed.
thanks Haitao.
> SpillableMemoryManager memory leak for WeakReference
> ----------------------------------------------------
>
> Key: PIG-2917
> URL: https://issues.apache.org/jira/browse/PIG-2917
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.11
> Reporter: Haitao Yao
> Assignee: Haitao Yao
> Fix For: 0.11
>
> Attachments: aa.jpg, SpillableMemoryManager.patch
>
>
> Sine the SpillableMemoryManager subscribed the memory notifications, and hold a weak reference of all the spillable, if there's too many weak reference and the memory exceeds the threshold, the current code will not clear the spillable weak references.
> the details is illustrated in the attached screenshot of a MemoryAnalyzer.
> So we need to clear the spillables when the memory notifications is received.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira