RFR: 8146416: java.lang.OutOfMemoryError triggers: assert(current_bci == 0) failed: bci isn't zero for do_not_unlock_if_synchronized

Roland Westrelin rwestrel at redhat.com
Wed Jun 1 13:55:28 UTC 2016

>> I noticed you added a
>> test case (DeoptReallocFailureUncommonTrap). Is that one expected to
>> fail with the same assert as well? I tried it but it seems to run fine.
> no its not expected to give same assert. as exception handling and
> poping will not work as in case of non uncommon_trap case.
> uncommon_trap case don't have exception handling and return pc is never
> set to Interpreter::_rethrow_exception_entry. so normal execution will
> continue with (failed realloc) interpreter frames.
> classloading will be triggered here in failed realloc execution. may be
> it will again throw exception, which clears pending_exception field and
> rethrow. may be poping starts here(whihc will work fine) but incorrect.

So is the test expected to fail at all? Is the failure intermittent? And
the problem this test triggers is that class loading clears the pending


More information about the hotspot-compiler-dev mailing list