In this particular case we're throwing an OOM while inside the counter
overflow on entry to a method.  The exception appears to propagate up
from compile_method, presumably from the resolve_string_constants and
load_signature_classes calls.  compile_method_base is also declared
TRAPS though it can't actually throw an exception.  I think the whole
path from CompilationPolicy::event to compile_method_base should be
cleaned up so that exceptions can't propagate.  Any exception thrown
in the path are side effects and not exception that should even be
propagated to the regular Java code.  I'll file a separate bug for
this.