You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/11/24 20:46:16 UTC

[jira] [Updated] (SPARK-4090) Memory leak in snappy-java 1.1.1.4/5

     [ https://issues.apache.org/jira/browse/SPARK-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell updated SPARK-4090:
-----------------------------------
    Fix Version/s: 1.2.0

> Memory leak in snappy-java 1.1.1.4/5
> ------------------------------------
>
>                 Key: SPARK-4090
>                 URL: https://issues.apache.org/jira/browse/SPARK-4090
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.2.0
>            Reporter: Davies Liu
>            Priority: Blocker
>             Fix For: 1.2.0
>
>         Attachments: screenshot-12.png
>
>
> There is memory-leak bug in snappy-java 1.1.1.4/5, we should rollback to 1.1.1.3 or wait for bugfix.
> The jenkins tests timeouted or OOM multiple times recently. While test it locally, I got the heap dump of leaked JVM:
> Then found that it's a bug in recent releases of snappy-java:
> {code}
> +        inputBuffer = inputBufferAllocator.allocate(inputSize);
> +        outputBuffer = inputBufferAllocator.allocate(outputSize);
> {code}
> The outputBuffer is allocated from inputBufferAllocator but released to outputBufferAllocator: https://github.com/xerial/snappy-java/issues/91



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org