JDK-8193879 : Java debugger hangs on method invocation
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 8,10.0.1,11
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-12-20
  • Updated: 2020-04-21
  • Resolved: 2018-10-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 12
11.0.8-oracleFixed 12 b15Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Fix request (11u) This bug was recently opened by Oracle. It already had jdk11u-fix-yes classification but was obviously not backported yet. I worked on a backport and got it reviewed: https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-March/002667.html I think the bugfix is a viable candidate for backporting. The new test succeeds with the fix.

This could be possibly duplicate of JDK-8156498 which is yet to be fixed.

I have verified this issue with 11 ea b19, and issue is still reproducible. It still hangs, captured couple of last transactions from JDI [JDI: Looking up Class, id=472] [JDI: Looking up Class, id=325] [JDI: Looking up ArrayType, id=230] [JDI: Looking up Class, id=346] [JDI: Looking up Class, id=347] [JDI: Looking up Class, id=357] [JDI: Looking up ArrayType, id=283] [JDI: Looking up Class, id=3] [JDI: Looking up Class, id=319] [JDI: Looking up Class, id=353] [JDI: Looking up ArrayType, id=182] [JDI: Looking up Class, id=349] [JDI: Looking up ArrayType, id=278] [JDI: Looking up Class, id=323] [JDI: Looking up ArrayType, id=265] [JDI: Looking up ArrayType, id=365] [JDI: Looking up ArrayType, id=361] [JDI: Looking up ArrayType, id=364] [JDI: Looking up ArrayType, id=359] [JDI: Looking up ArrayType, id=360] [JDI: Looking up ArrayType, id=358] [JDI: Looking up ArrayType, id=363] [JDI: Looking up ArrayType, id=362] [JDI: Sending Command(id=415) JDWP.ClassType.Superclass] [JDI: Sending: clazz(ClassTypeImpl): ref=325] [JDI: Receiving Command(id=415) JDWP.ClassType.Superclass] [JDI: Looking up Class, id=357] [JDI: Receiving: superclass(ClassTypeImpl): ref=357] [JDI: Sending Command(id=417) JDWP.ThreadReference.Name] [JDI: Sending: thread(ThreadReferenceImpl): ref=1] [JDI: Receiving Command(id=417) JDWP.ThreadReference.Name] [JDI: Receiving: threadName(String): main] [JDI: Sending Command(id=419) JDWP.ClassType.InvokeMethod] [JDI: Sending: clazz(ClassTypeImpl): ref=472] [JDI: Sending: thread(ThreadReferenceImpl): ref=1] [JDI: Sending: methodID(long): 139651063031216] [JDI: Sending: arguments(ValueImpl[]): ] [JDI: Sending Command(id=420) JDWP.ThreadReference.Name] [JDI: Sending: ==== Hang====

If I remember correctly, we already fixed some of the method invocation sync issues in 9 & 10. These are the bug ID's: JDK-8154529 JDK-8181419 Most likely, the fix of JDK-8154529 was not back ported to 8. We need to check if this issue is present in 9, 10 and 11 first. If - not then this has to be targeted just to 8. Also, this bug can be a dup of the JDK-8156498 that has not been fixed yet.

It would probably be a good idea to create a jtreg testcase for this.