JDK-8042310 : TestStringDeduplicationMemoryUsage test failing
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 8u20,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-05-02
  • Updated: 2014-07-29
  • Resolved: 2014-05-30
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 8 JDK 9
8u20Fixed 9 b19Fixed
Related Reports
Duplicate :  
JDK-8044031 - Test gc/g1/TestStringDeduplicationMemoryUsage.java is still failing due to unexpected memory usage
Description
execStatus=Failed. Execution failed\: `main' threw exception\: java.lang.Exception\: Unexpected memory usage, heapMemoryUsageWithDedup should be less or equal to heapMemoryUsageWithDedupExpected

Memory usage summary:
   heapMemoryUsageWithoutDedup:      1767168
   heapMemoryUsageWithDedup:         671352
   heapMemoryUsageWithDedupExpected: 647280
----------System.err:(16/1112)----------


java.lang.Exception: Unexpected memory usage, heapMemoryUsageWithDedup should be less or equal to heapMemoryUsageWithDedupExpected
	at TestStringDeduplicationTools.testMemoryUsage(TestStringDeduplicationTools.java:520)
	at TestStringDeduplicationMemoryUsage.main(TestStringDeduplicationMemoryUsage.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:484)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:745)
Comments
This has happened more than once now, so raising likelihood from L to M. MMH=P3
28-05-2014
I=Test issue, but causes noise in nightly tests -> M L=Seen only once so far -> L W=Unknown -> H MLH=P4
05-05-2014
Looks like a problem with the test. It seems ManagementFactory.getMemoryMXBean().getHeapMemoryUsage().getUsed() just doesn't provide the precision/exactness that the test relies on. Unless we can come up with a way to make it stable we should just remove this test.
05-05-2014