In JvmtiExport::post_vm_object_alloc we trace the "oop object" klass name.
This is not done correctly anymore, hence we crash.
The issue was found running jvmti tests (tonga nsk.jvmti) with full jvmti trace on.
This is not something we normally do, so the issue can have been lingering for some time.
This is not done correctly anymore, hence we crash.
The issue was found running jvmti tests (tonga nsk.jvmti) with full jvmti trace on.
This is not something we normally do, so the issue can have been lingering for some time.