MemberName$Factory.resolve() and the Eclipse debugger.

[MacGregor, Duncan (GE Energy Management)]

When we’ve tried to debug some of our Java core in the context of running a large application we’ve been seeing long pauses (sometime very long pauses of over a minute) due to java.lang.invoke.MemberName$Factory.resolve() apparently taking ages to complete. Testing with an openjdk build I see the reported line number in thread dumps is 962 of MemberName.java, which is where Factory.resolve() calls MethodHandleNatives.resolve().

Anybody else seen this, and is it even worth investigating further without David’s change to intern MemberNames?

Regards, Duncan.