curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-487) GzipCompressionProvider produces a lot of finalizable objects
Date Mon, 10 Dec 2018 15:06:00 GMT


ASF GitHub Bot commented on CURATOR-487:

Github user Randgalt commented on the issue:
    Can you point to other libraries that have taken the approach of re-writing these APIs?
I see you opened Are they taking this
change as well?

> GzipCompressionProvider produces a lot of finalizable objects
> -------------------------------------------------------------
>                 Key: CURATOR-487
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>            Reporter: Roman Leventov
>            Assignee: Cameron McKenzie
>            Priority: Major
>             Fix For: 4.1.0
> GzipCompressionProvider.compress() and decompress() methods are called a lot inside and
outside of the framework and each such call produces a or Inflater
object that are finalizable, that is bad for GC.
> Compressing or decompressing a finite byte[] object (in contrast to compressing/decompressing
an InputStream or an OutputStream of unknown length) is actually a happy case because even
PhantomReference object could be avoided, the native resources could be created and freed
in a single try-finally block.
> Curator must avoid that. [] is a potential replacement,
for example.
> A similar issue could be also fixed in Apache Commons Compress: and
Curator is made to depend on Commons Compress.

This message was sent by Atlassian JIRA

View raw message