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
- clones
-
JDK-8176454 Performance: jweak references not suitable for robust cache architecture
-
- Closed
-
- is blocked by
-
JDK-8072498 Multi-thread JNI weak reference processing
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-