JDK-8257761 : [mlvm] make JDI tests tolerate exceptions caused by code cache exhaustion
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 15,16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-12-04
  • Updated: 2020-12-07
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-8058176 - [mlvm] tests should not allow code cache exhaustion
Description
Created after the JDK-8058176

Hotspot can throw java.lang.VirtualMachineError or java.lang.InternalError around calls if there is no code cache space left. This can also cause a timeout in JDI test waiting for a specific breakpoint in the debuggee. The tests need to be hardened to tolerate such failures.

How to reproduce: run any vmTestbase/vm/mlvm/meth/stress/jdi/breakpointInt* test with restricted code cache -XX:ReservedCodeCacheSize=3M
Comments
Copying priority from the original case, the JDK-8058176: ILW=Test need to be more resilient, common problem, none=LHH=P4
04-12-2020