Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P2
Fix Version/s: 13
Affects Version/s: 11, 13, 14
Component/s: hotspot
Labels:

Subcomponent:
compiler
Resolved In Build:
b30
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8227620	14	Nils Eliasson	P2	Resolved	Fixed	b06
JDK-8228312	13.0.2	Nils Eliasson	P2	Resolved	Fixed	b01
JDK-8228096	13.0.1	Nils Eliasson	P2	Resolved	Fixed	b02
JDK-8250783	11.0.10-oracle	Jagjot Singh	P2	Closed	Fixed	b01
JDK-8251006	11.0.9	Nils Eliasson	P2	Resolved	Fixed	b02

A couple of test failed in the JDK-13 CI:

vmTestbase/gc/lock/malloc/malloclock02/TestDescription.java
vmTestbase/gc/lock/jniref/jnireflock01/TestDescription.java

with messages that look like this:

Exception in
gc.lock.LockerTest$Worker@16e53b61
Exception in
gc.lock.LockerTest$Worker@7440ac46
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Exception in
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Exception in
gc.lock.LockerTest$Worker@486b1597
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Exception in
gc.lock.LockerTest$Worker@7043894b
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Exception in
gc.lock.LockerTest$Worker@6086e1b3
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
gc.lock.LockerTest$Worker@2c310598
Exception in
gc.lock.LockerTest$Worker@ce338b5
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Exception in
gc.lock.LockerTest$Worker@1c9d5925
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
Failures summary:
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects
java.lang.OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects

I originally added these sightings to JDK-8214584, but Dean Long
requested that I move them to JDK-8192647. Steffan Karlsson does
not think these sightings match JDK-8192647 so I'm putting them
into their own bug.

backported by

JDK-8227620 Catch OOM from deopt that fails rematerializing objects

Resolved

JDK-8228096 Catch OOM from deopt that fails rematerializing objects

Resolved

JDK-8228312 Catch OOM from deopt that fails rematerializing objects

Resolved

JDK-8251006 Catch OOM from deopt that fails rematerializing objects

Resolved

JDK-8250783 Catch OOM from deopt that fails rematerializing objects

Closed

relates to

JDK-8192647 GClocker induced GCs can starve threads requiring memory leading to OOME

Open

JDK-8227309 Handle OOM when rematerializing objects less surprising

Open

JDK-8273095 vmTestbase/vm/mlvm/anonloader/stress/oome/heap/Test.java fails with "wrong OOME"

Resolved

(3 relates to)

Assignee:: Nils Eliasson (Inactive)

Reporter:: Daniel Daugherty

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2019-06-20 13:03

Updated:: 2022-10-06 17:35

Resolved:: 2019-07-10 09:50

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates