Git Product home page Git Product logo

java-native-memory-leaks's Introduction

Java native memory leaks

Testing native heap memory leaks caused by:

  • class java.util.zip.Inflater and its native method java.util.zip.Inflater.init(boolean),
  • class java.util.zip.ZipInputStream using the first one.

Remember: proper way to avoid memory leaks is deallocating memory by calling methods Inflater#end() or ZipInputStream#close(). But sometimes it's necessary to use a workaround for a legacy or thid-party code with bugs.

refs:

Building and running

mvn install

Go to target directory to run jar file:

cd target

Show commands:

java -jar memory-leaks.jar

Next sections shows commands to run tests with 5 different garbage collectors and some results.

Testing memory utilisation with Inflater class

Instance is not properly ended

Be careful, it really may cause memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (2)
Parallel GC leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (2)
Old Parallel GC leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (2)
CMS (Concurrent Mark Sweep) GC leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (2)
G1 (Garbage First) GC leak and error (1) leak and error (1) leak and error (1) leak and error (1) leak and error (1) no leak leak and error (2)

Table legend:

  • leak and error (1) - whole OS memory allocated, OutOfMemoryError
  • leak and error (2) - part of OS memory allocated, OutOfMemoryError or Exception

Potential workaround: GC is called periodically

It's usually safe workaround, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithCollectingRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithCollectingRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithCollectingRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithCollectingRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithCollectingRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak no leak
Parallel GC no leak no leak no leak no leak no leak no leak no leak
Old Parallel GC no leak no leak no leak no leak no leak no leak no leak
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak no leak
G1 (Garbage First) GC no leak no leak no leak no leak no leak no leak no leak

Potential workaround: Objects intentionally litter Java heap

It's usually safe workaround, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithLitteringRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithLitteringRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithLitteringRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithLitteringRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterNotProperlyEndedWithLitteringRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak leak and error
Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
Old Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak leak and error
G1 (Garbage First) GC leak and error leak and error no leak no leak no leak no leak leak and error

Instance is properly ended

It's safe, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterProperlyEndedRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterProperlyEndedRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterProperlyEndedRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterProperlyEndedRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.InflaterProperlyEndedRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak no leak
Parallel GC no leak no leak no leak no leak no leak no leak no leak
Old Parallel GC no leak no leak no leak no leak no leak no leak no leak
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak no leak
G1 (Garbage First) GC no leak no leak no leak no leak no leak no leak no leak

Testing memory utilisation with ZipInputStream class

Instance is not properly closed

Be carefull, it really may cause memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak leak and error
Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
Old Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak leak and error
G1 (Garbage First) GC leak and error leak and error no leak no leak no leak no leak leak and error

Potential workaround: GC is called periodically

It's usually safe workaround, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithCollectingRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithCollectingRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithCollectingRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithCollectingRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithCollectingRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak no leak
Parallel GC no leak no leak no leak no leak no leak no leak no leak
Old Parallel GC no leak no leak no leak no leak no leak no leak no leak
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak no leak
G1 (Garbage First) GC no leak no leak no leak no leak no leak no leak no leak

Potential workaround: Objects intentionally litter Java heap

It's usually safe workaround, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithLitteringRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithLitteringRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithLitteringRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithLitteringRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamNotProperlyClosedWithLitteringRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak no leak
Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
Old Parallel GC leak and error leak and error no leak no leak no leak no leak leak and error
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak leak and error
G1 (Garbage First) GC leak and error leak and error no leak no leak no leak no leak leak and error

Instance is properly closed

It's safe, no memory leak:

java -XX:+UseSerialGC        -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamProperlyClosedRunner
java -XX:+UseParallelGC      -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamProperlyClosedRunner
java -XX:+UseParallelOldGC   -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamProperlyClosedRunner
java -XX:+UseConcMarkSweepGC -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamProperlyClosedRunner
java -XX:+UseG1GC            -cp memory-leaks.jar pl.kordulewski.memory.leaks.runners.ZipInputStreamProperlyClosedRunner
Garbage Collector Java 6 @ Linux Java 6 @ Windows Java 7 @ Linux Java 7 @ Windows Java 8 @ Linux Java 8 @ Windows Java 8 @ Solaris
Serial GC no leak no leak no leak no leak no leak no leak no leak
Parallel GC no leak no leak no leak no leak no leak no leak no leak
Old Parallel GC no leak no leak no leak no leak no leak no leak no leak
CMS (Concurrent Mark Sweep) GC no leak no leak no leak no leak no leak no leak no leak
G1 (Garbage First) GC no leak no leak no leak no leak no leak no leak no leak

Alternative flags

-XX:+AggressiveHeap

Error messages

java.lang.OutOfMemoryError
    at java.util.zip.Inflater.init(Native Method)

Exception in thread "main" #
# There is insufficient memory for the Java Runtime Environment to continue.

#
# There is insufficient memory for the Java Runtime Environment to continue.

Used JVMs

description JVM version of JVM OS version of OS
Java 6 @ Linux HotSpot 1.6.0_45 OpenSuse 42.2 x64
Java 7 @ Linux HotSpot 1.7.0_79 OpenSuse 42.2 x64
Java 8 @ Linux HotSpot 1.8.0_131 OpenSuse 42.2 x64
Java 6 @ Windows HotSpot 1.6.0_45 Windows 7 x64
Java 7 @ Windows HotSpot 1.7.0_79 Windows 7 x64
Java 8 @ Windows HotSpot 1.8.0_45 Windows 7 x64
Java 8 @ Solaris HotSpot 1.8.0_60 Solaris 11.3 x86

Mapping different GCs to flags

Garbage Collector flag
Serial GC -XX:+UseSerialGC
Parallel GC -XX:+UseParallelGC
Old Parallel GC -XX:+UseParallelOldGC
CMS (Concurrent Mark Sweep) GC -XX:+UseConcMarkSweepGC
G1 (Garbage First) GC -XX:+UseG1GC

G1 GC was called with flags:

  • HotSpot 6: -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions
  • all other cases: -XX:+UseG1GC

All java classes ready to run

Class names are self-describing:

class safe? description
InflaterProperlyEndedRunner safe instance is properly ended
InflaterNotProperlyEndedRunner may cause leak instance is not properly ended
InflaterNotProperlyEndedWithCollectingRunner tested as a workaround - potentially safe GC is called periodically
InflaterNotProperlyEndedWithLitteringRunner tested as a workaround - potentially safe objects intentionally litter Java heap
ZipInputStreamProperlyClosedRunner safe instance is properly closed
ZipInputStreamNotProperlyClosedRunner may cause leak instance is not properly closed
ZipInputStreamNotProperlyClosedWithCollectingRunner tested as a workaround - potentially safe GC is called periodically
ZipInputStreamNotProperlyClosedWithLitteringRunner tested as a workaround - potentially safe objects intentionally litter Java heap

java-native-memory-leaks's People

Contributors

mkordulewski avatar

Stargazers

avatar avatar

Watchers

avatar

Forkers

bothdev

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.