JDK-8153194 : [TEST_BUG] PreserveFPRegistersTest.java runs out of memory in the nightlies
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8u172,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-03-31
  • Updated: 2019-01-14
  • Resolved: 2016-07-01
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
8u192Fixed 9 b131Fixed
Related Reports
Relates :  
JDK-8148175 - C1: G1 barriers don't preserve FP registers
Sub Tasks
JDK-8153195 :  
Quarantine compiler/gcbarriers/PreserveFPRegistersTest.java - Resolved
Description
The recently added test compiler/gcbarriers/PreserveFPRegistersTest.java runs out of memory in the compiler nightlies.
Comments
<webrev.02> : http://cr.openjdk.java.net/~rraghavan/8153194/webrev.02/ http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-June/023592.html
01-07-2016
<RFR> : http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-June/023516.html <webrev.01> : http://cr.openjdk.java.net/~rraghavan/8153194/webrev.01/
23-06-2016
Notes: Confirmed from history that test failed for 64-bit targets only with -XX:-UseCompressedOops enabled. Root cause of the failure seems to hard coded Reference size value as 4 in test. int refSize = 4; (tested manually that temporary change of refSize to 8 solved failing case issue) Work in progress for correct fix. [i. may be adding -XX:+UseCompressedOops to VM options OR setting default referenceSize to 8 OR ii. detecting CompressedOops state within VM and setting refSize accordingly - checking usages of wb.getHeapOopSize() ]
20-06-2016
Hi Vladimir, this issue has just shown up. The push job hs-comp -> hs is already underway and I don't want to stop it (let's get some changes into hs this week). Also, there are some changes in hs-comp that have not been fully tested yet. Can you fix this test in the next couple of hours or so (and then push the fix directly into hs)? If not, I'll quarantine the test (also directly in hs). Thank you! Best regards, Zoltan
31-03-2016