Memory leaks in methods looking up Class objects about jni-rs HOT 1 CLOSED

Which client code is NOT affected (benign leaks)

Such leaks can be considered benign if all created local references are freed later:

* Refs created in native methods called from Java — freed by the JVM when the native method returns.

If the native method implementation deals with large arrays of objects, then it might run out of local references storage sooner.

To ensure that programmers can manually free local references, JNI functions are not allowed to create extra local references, except for references they return as the result.

From a library user perspective, it is reasonable to assume this.

1. Always perform lookups in a local frame to ensure we delete refs _if_ we create them. _Likely to be a performance regression — need to evaluate._

Also likely to consume more memory due to the additional local references stacks created.

from jni-rs.