About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Publication
USENIX ATC 2007
Conference paper
Improved JNI Memory Management Using Allocations from the Java Heap
Abstract
JAVA, as a development platform provides a number of programmer friendly capabilities, including Platform neutrality, Garbage collection, Unicode support, Regular expressions, and Multi-threading support. The Java Native Interface (JNI) to allow Java to interact with libraries written in other languages. However, JNI introduces platform specific dependencies that mitigate some of Java’s benefits. In particular: Java’s garbage collection system and heap management has no awareness or control over the use of dynamic memory in the native code. A JNI library can easily cause the Java program to exceed its maximum specified heap.