JDK-8218166 : com/sun/jdi/SimulResumerTest.java failure
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 12,13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-31
  • Updated: 2019-03-21
  • Resolved: 2019-03-14
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 13
13 b13Fixed
Related Reports
Relates :  
JDK-8196611 - [Graal] Tests unaware of objects allocation triggered by Graal
Description
----------System.err:(20/1274)----------
[1ms] run args: [SimulResumerTarg]
[33069ms] failure: Got exception from ownedMonitors(): com.sun.jdi.ObjectCollectedException
[33225ms] failure: Got exception from ownedMonitors(): com.sun.jdi.ObjectCollectedException
[33391ms] failure: Got exception from ownedMonitors(): com.sun.jdi.ObjectCollectedException
[33639ms] failure: Got exception from ownedMonitors(): com.sun.jdi.ObjectCollectedException
[33663ms] resumer Interrupted
java.lang.Exception: SimulResumerTest: failed; bkpts = 20000, iters = 204
	at SimulResumerTest.runTests(SimulResumerTest.java:281)
	at TestScaffold.startTests(TestScaffold.java:431)
	at SimulResumerTest.main(SimulResumerTest.java:120)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:567)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:246)
	at java.base/java.lang.Thread.run(Thread.java:835)
Comments
I removed the "graal" label.
07-03-2019
If this is not a Graal specific issue then please remove the graal label. If this is a Graal specific issue, then this is currently blocking integration of Graal into OpenJDK and should have the integration_blocker label.
06-03-2019
As far as I can tell, ObjectCollectedException means invalid object, which can only happen if we find a monitor owner object that then got collected. While the test code looks safe, this could happen if the target thread triggered a compile that called into Graal code. However, there have been at least one failure without Graal enabled, which may be harder to explain. If would be nice if the test could check which method the target thread was actually in when we called ownedMonitors, but since the test is racy we can't do that. To allow this test to run successfully with Graal, how about if we ignore ObjectCollectedException exceptions, just like we do for THREAD_NOT_SUSPENDED errors?
19-02-2019
> Can this be related to JDK-8217941 ? Looks different to me.
04-02-2019
Can this be related to JDK-8217941 ?
04-02-2019