JDK-8158064 : MemoryMXBean/Pending.java gets unexpected RuntimeException
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 9
  • Priority: P5
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2016-05-27
  • Updated: 2016-07-14
  • Resolved: 2016-07-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 9
9Resolved
Related Reports
Duplicate :  
JDK-8158837 - java/lang/management/MemoryMXBean/Pending.java fails with -limitmods
Relates :  
JDK-8158837 - java/lang/management/MemoryMXBean/Pending.java fails with -limitmods
Description
----------System.err:(15/1155)----------
java.lang.RuntimeException: Unexpected finalized objects: Current finalized = 600 Current pending = 0 but expected = 0
	at Pending.checkFinalizerCount(Pending.java:146)
	at Pending.test(Pending.java:113)
	at Pending.main(Pending.java:71)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-internal/Native Method)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-internal/NativeMethodAccessorImpl.java:62)
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-internal/DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(java.base@9-internal/Method.java:531)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
	at java.lang.Thread.run(java.base@9-internal/Thread.java:843)
Comments
Duplicate of JDK-8158837
14-07-2016
This should be closed as a dup of JDK-8158837 I think.
23-06-2016
Impact - L, Likelihood - L, Workaround - H. Changing priority to P5
01-06-2016
Since all 600 objects were finalized, it is possible that GC got a chance to run before we check for number of finalized objects @ Pending.checkFinalizerCount(Pending.java:146) . Does not look like an integration blocker. Test-case needs to be made more robust against these race-conditions. Can integration-blocker label be removed?
30-05-2016
Untriaged nightly test failure marked as integration_blocker == P1 until shown to be otherwise.
30-05-2016