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

[Christian Thalinger]

> On Oct 29, 2014, at 9:39 AM, MacGregor, Duncan (GE Energy Management) <duncan.macgregor at ge.com> wrote:
> 
> 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.

Over a minute?!?  What is the JVM doing during this time?  Class loading?  Garbage collection?

The only thing that comes to mind is that methods with breakpoints are not compiled but interpreted.  But even if you had a lot of breakpoints in core methods I don’t see how that would explain pauses of over a minute.

> 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.
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev