The problem was that when Java is shut down, constant pools are nilled out. I there's a Java code runnning (in some process), then the interpreter tries to reference nil and - naturally - crashes.
The solution is to check for this situation. The downside is that it makes the interpreter slower. This may be one of the reasons why in Java, runtime structures not visible to the programmers and are kept at separate heap. Then they are solely under JVM control and JVM does not need to perform these checks.
The problem was that when Java is shut down, constant pools are nilled out. I there's a Java code runnning (in some process), then the interpreter tries to reference
niland - naturally - crashes.The solution is to check for this situation. The downside is that it makes the interpreter slower. This may be one of the reasons why in Java, runtime structures not visible to the programmers and are kept at separate heap. Then they are solely under JVM control and JVM does not need to perform these checks.
Anyways, addressed in:
CONSTANTPOOL_AT()