JDK-8061495 : NEED tests for 8041984
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7u80,8u60,9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2014-10-20
  • Updated: 2021-10-22
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8041984 - CompilerThread seems to occupy all CPU in a very rare situation
Description
As promised I am asking for help to write a regression test for this bug.

First, I want to make sure that time spent in EA does not exceed EscapeAnalysisTimeout. Also this is new product flag and needs to be tested.

Second I need a stress test for EA. Next class which implements BTree shows the problem - a lot of array allocations and arraycopy (Arrays.copyOf()) in compiled method (after inlining):

https://github.com/karussell/graphhopper/blob/master/core/src/main/java/com/graphhopper/coll/GHLongIntBTree.java

Also it is not clear what our interaction process is.
Should I file a separate bug for new test or I should wait when the test is ready and integrate it together with the fix?

Note, I reproduced the failure using 7u80 sources and steps described in 8041984 bug report. After building graphhopper binaries you can run standalone java application and observe long compilation time.