-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b52
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084509 | emb-9 | Volker Simonis | P4 | Resolved | Fixed | team |
JDK-8298653 | openjdk8u372 | Qi Ao | P4 | Resolved | Fixed | b01 |
JDK-8274720 | 8u321 | Anto J | P4 | Resolved | Fixed | b01 |
The three Introspector test:
java/beans/Introspector/7064279/Test7064279.java
java/beans/Introspector/Test7172865.java
java/beans/Introspector/Test7195106.java
provoke an OutOfMemory situation by repeatedly allocating constantly growing arrays with the following loop:
int[] array = new int[1024];
while (true) {
array = new int[array.length << 1];
}
However if we're running on a machine with plenty of RAM the default Java heap will be bigger than ~4GB and we will get a NegativeArraySizeException instead of an OutOfMemoryError because the array length which is a signed int will wrap around and become negative.
The fix is easy - just specify a concrete -Xmx value for the test.
java/beans/Introspector/7064279/Test7064279.java
java/beans/Introspector/Test7172865.java
java/beans/Introspector/Test7195106.java
provoke an OutOfMemory situation by repeatedly allocating constantly growing arrays with the following loop:
int[] array = new int[1024];
while (true) {
array = new int[array.length << 1];
}
However if we're running on a machine with plenty of RAM the default Java heap will be bigger than ~4GB and we will get a NegativeArraySizeException instead of an OutOfMemoryError because the array length which is a signed int will wrap around and become negative.
The fix is easy - just specify a concrete -Xmx value for the test.
- backported by
-
JDK-8084509 [TESTBUG] Some Introspector tests fail with a Java heap bigger than 4GB
- Resolved
-
JDK-8274720 [TESTBUG] Some Introspector tests fail with a Java heap bigger than 4GB
- Resolved
-
JDK-8298653 [TESTBUG] Some Introspector tests fail with a Java heap bigger than 4GB
- Resolved