InstanceKlass has a jmethodID cache that lazily grows after redefinition upon request for a new jmethodID. This lazy growth is because for obsolete methods, the method idnum is incremented.
This lazy growth requires that jmethodIDs may have to be deleted if there's a race in creating them.
Since redefinition is at a safepoint, we can just extend the jmethodID cache then since we know the count.
- relates to
-
JDK-6404550 Cannot implement late attach in NetBeans Profiler due to missing functionality in JVMTI
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
JDK-8268406 Deallocate jmethodID native memory
-
- Open
-
(1 relates to, 2 links to)