Performance: jweak references not suitable for robust cache architecture
#1 Contrary to the expectations, jweak objects that are destroyed with DeleteWeakGlobalRef() take more GC time than alive one, but with dead objects (see attached test case)
#2 DeleteWeakGlobalRef() does not actually free the memory
#3 jweaks are processed single threaded by the GC
#1 Contrary to the expectations, jweak objects that are destroyed with DeleteWeakGlobalRef() take more GC time than alive one, but with dead objects (see attached test case)
#2 DeleteWeakGlobalRef() does not actually free the memory
#3 jweaks are processed single threaded by the GC
- is blocked by
-
JDK-8072498 Multi-thread JNI weak reference processing
- Resolved
- is cloned by
-
JDK-8204505 Performance: jweak references not suitable for robust cache architecture
- Resolved
- relates to
-
JDK-8072498 Multi-thread JNI weak reference processing
- Resolved
-
JDK-8194312 Support parallel and concurrent JNI global handle processing
- Resolved