We are seeing this assert fire after the changes from JDK-8238988

--------------- T H R E A D ---------------

Current thread (0x000000d56ca0c800): JavaThread "MainThread" [_thread_in_vm, id=14104, stack(0x000000d56ec70000,0x000000d56ed70000)] _threads_hazard_ptr=0x000000d56966a5a0, _nested_threads_hazard_ptr_cnt=0

Stack: [0x000000d56ec70000,0x000000d56ed70000]
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x9ebd61] os::platform_print_native_stack+0xf1 (os_windows_x86.cpp:369)
V [jvm.dll+0xbebe0b] VMError::report+0xf0b (vmerror.cpp:725)
V [jvm.dll+0xbed6be] VMError::report_and_die+0x8ae (vmerror.cpp:1533)
V [jvm.dll+0xbeddb4] VMError::report_and_die+0x64 (vmerror.cpp:1317)
V [jvm.dll+0x414632] report_vm_error+0x102 (debug.cpp:264)
V [jvm.dll+0xb8b38e] JavaThread::is_lock_owned+0x4e (thread.cpp:2243)
V [jvm.dll+0xb8d194] Threads::owning_thread_from_monitor_owner+0x74 (thread.cpp:4703)
V [jvm.dll+0x7e7863] JvmtiEnvBase::get_object_monitor_usage+0x1e3 (jvmtienvbase.cpp:996)
V [jvm.dll+0x7dea7c] JvmtiEnv::GetObjectMonitorUsage+0x4c (jvmtienv.cpp:2847)
V [jvm.dll+0x79de96] jvmti_GetObjectMonitorUsage+0x136 (jvmtienter.cpp:4105)
C [objmonusage003.dll+0x118a]

Test: vmTestbase/nsk/jvmti/GetObjectMonitorUsage/objmonusage003/TestDescription.java