###@###.### discovered a bug in the implicit null handling path rewritten in 5.0 under 4826722. In the case where a monomorphic inline cache call site in C1-generated code dispatching to an interpreted method through the ientries gets a null receiver, the SEGV will be taken in the ientries code and mishandled by SharedRuntime::continuation_for_implicit_exception. It turns out that we usually get lucky and consider this fault to be in the inline cache check of an nmethod, but since the code blob we're dealing with isn't an nmethod this is prone to failure at any point.