RFR: 8146416: java.lang.OutOfMemoryError triggers: assert(current_bci == 0) failed: bci isn't zero for do_not_unlock_if_synchronized
rwestrel at redhat.com
Thu May 26 11:27:23 UTC 2016
>>> >my worry is this, we do all computation (vframe array) using one
>>> >exception or no exception at all.. and later change it to realloc
>>> >exception.. wouldn't this cause and issue at unpack.
>> JVMCI does something similar so we can suppose it's safe.
> some checks in unpack "(exec_mode == Unpack_exception) &&
> iframe->interpreter_frame_expression_stack_size() == 0)"
> JVMCI code is for an already thrown exception right ?
> expression stack is expected to have exception object...
> what about a normal expression stack in unpack?
We are replacing an existing exception with another one. Why would the
expression stack matter?
More information about the hotspot-compiler-dev