JDK-8163999 : Workaround intermittent failures of TreePosTest.java due to C2 memory usage
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2016-08-12
  • Updated: 2017-01-24
  • Resolved: 2016-08-15
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
9 b133Fixed
Related Reports
Relates :  
JDK-8165193 - Workaround intermittent failures of JavacTreeScannerTest and SourceTreeScannerTest due to C2 memory usage
Relates :  
JDK-8168499 - Workaround intermittent failures of IntersectionTargetTypeTest.java
Relates :  
JDK-8143321 - Reduce the C2 compiler's memory usage
Relates :  
JDK-8166002 - Emulate client build on platforms with reduced virtual address space
Relates :  
JDK-8173305 - Trial reversion of langtools test changes for limited win32 address space
Description
The test

tools/javac/tree/TreePosTest.java

has been seen to fail intermittently (JDK-8162907) recently on test systems using the default JVM and -Xmx512m for memory. With a change in win32 from the C1 to C2 compiler (JDK-8154209), the C2 compiler seems to need more memory to run.

A workaround until the underlying issues are addressed (JDK-8143321), is to try to modify the jtreg options for this test.
Comments
While the test could be seen as a "canary in the cage" for C2 memory usage, we might also want to investigate the memory usage for the test, to see if it can be reduced without significantly changing the functionality of the test. For example, is the test "leaking" memory?
15-08-2016