JDK-8040247 : vm/gc/containers/LinkedBlockingDeque_Arrays fails when shutting down
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • Submitted: 2014-04-15
  • Updated: 2016-04-06
  • Resolved: 2016-04-06
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 9
9Resolved
Related Reports
Relates :  
Description
#  Internal Error (C:\jprt\T\P1\081437.ehelin\s\src\share\vm\gc_implementation\g1\g1CollectedHeap.cpp:3492), pid=24988, tid=20676
#  guarantee(!failures) failed: there should not have been any failures

Given that the test is being run for 30 minutes and we see the following events:

Events (10 events):
Event: 30.333 loading class java/lang/Shutdown
Event: 30.334 loading class java/lang/Shutdown done
Event: 30.334 loading class java/lang/Shutdown$Lock
Event: 30.334 loading class java/lang/Shutdown$Lock done
Event: 33.600 Executing VM operation: CGC_Operation
Event: 33.604 Executing VM operation: CGC_Operation done
Event: 33.604 Executing VM operation: CGC_Operation
Event: 33.608 Executing VM operation: CGC_Operation done
Event: 33.612 Thread 0x00000000176f3000 Thread exited: 0x00000000176f3000
Event: 33.613 Thread 0x00000000183ae000 Thread exited: 0x00000000183ae000

it seems like VM is shutting down when the failure happens.
Comments
This issue was seen once, two years ago. The code in question has gone through a lot of changes since then. Given that we haven't seen the issue again it was likely fixed by some other change. Doing further investigation on this issue at this point is will not be worth the effort.
06-04-2016

Stefan, since that failure happened way back in 2015.07 and only with an Aurora adhoc job, I simply deleted the comment.
05-04-2016

Dan, you are referring to a completely different guarantee. Your comment should be added do a new bug report. Could you remove your comment from this bug report? I think the solaris-sparc crash happened because of the compiler upgrade bug: JDK-8131330
05-04-2016

RULE "vm/gc/containers/LinkedBlockingDeque_Arrays" Crash Internal Error ...g1CollectedHeap.cpp...guarantee(!failures) failed: there should not have been any failures I don't think this is related to the VM shutdown issue, since it fails in a guarantee rather than hanging. I=Crash -> H L = Failed only once so far -> L W = None known -> H HLH=P2
05-04-2016

This might be related to the issues we are having when trying to shut down the GC cleanly.
15-04-2014