RFR(S): 8163994: Nightly test crashed in jvmtiAllocate
chris.plummer at oracle.com
Fri Aug 26 21:35:34 UTC 2016
Although the fix is addressing the specific issue described in the bug,
what about the general issue of referencing gdata after a call to
cbEarlyVMDeath(). Do more references to gdata need to be protected?
Also, is there the possibility of a multi-threading race condition here?
Could gdata be cleared by another thread after it is checked?
On 8/26/16 4:00 AM, Dmitry Samersoff wrote:
> Please review the fix.
> Under some circumstances, when JVMTI_ERROR_WRONG_PHASE(112) is received,
> jvmtiAllocate could be called after call to cbEarlyVMDeath.
> cbEarlyVMDeath set gdata->jvmti to NULL, so jvmtiAllocate crashes.
> The problem appears only once in nightly testing and I was not able to
> reproduce it locally.
> Guard added to jvmtiAllocate to get meaningful error message instead of
> These fix doesn't fix root cause - JVMTI_ERROR_WRONG_PHASE problem is
> going to be addressed under JDK-8134103.
More information about the hotspot-runtime-dev