JVMCI introduced the ability to rethrow an exception at the deopt point to support deoptimization during exception dispatch. The exception to be thrown is fetched from the top of stack. It's possible that exception has been escape analyzed and must be materialized. The current logic fetches the exception from the deopt state before materialization which will produce null in this case. Exception will eventually crash because we enter the exception machinery a NULL pointer and all those paths assume that it's non-null. The fix is simply to move the capture of the exception until after rematerialization.