Open JasonFengJ9 opened 3 months ago
There is OOM an attempt to allocate ~1G bytes object:
1STGCHTYPE GC History
3STHSTTYPE 02:49:06:305487362 GMT j9mm.101 - J9AllocateIndexableObject() returning NULL! 1073741840 bytes requested for object of class 0000FFFF9C215A00 from memory space 'Generational' id=0000FFFF9C0C53B0
3STHSTTYPE 02:49:06:305338239 GMT j9mm.134 - Allocation failure end: newspace=11665408/13238272 oldspace=520267304/1601568768 loa=16016384/16016384
3STHSTTYPE 02:49:06:305299871 GMT j9mm.470 - Allocation failure cycle end: newspace=11665408/13238272 oldspace=520267304/1601568768 loa=16016384/16016384
If it is intentional, so test should expect heap (Tenure really) is almost empty.
The test is allocating memory until an OOM occurs. https://github.com/ibmruntimes/openj9-openjdk-jdk11/blob/openj9/test/jdk/java/util/ResourceBundle/Bug4168625Test.java#L532
The test failed because it timed out, not because of the intentional OOMs. There is no indication or diagnostics to show what it was doing when it timed out. Given we couldn't reproduce it, we couldn't be overly concerned.
Failure link
From an internal build:
Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - passed