In the interpreter at back branches, the invocation counter is tested for OSR overflow, but not for interpreter profiling. This makes it possible to to OSR a method without a methodDataOop -- not a complete disaster, but it could hamper optimization.