Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2015801 | 1.2.0 | Ralph Kar | P1 | Closed | Fixed | 1.2beta4 |
"ANDERSON" has developed a big java application.
A lot of widgets are created.
When the PC is loaded, memory can be exhausted.
In this case, the application doesn't get an OutOfMemoryException as expected
per Java API and new method will just return a null.
The application can't handle properly this kind of situation.
The application then crashes or from time to time, Windows 95 hangs !
Configuration:
~~~~~~~~~~~~~
JDK 1.1.2 (this is worse with 1.1)
Windows 95 platform.
Test Case :
~~~~~~~~~
1 - Two files (Application.java, MainFrame.java) are in attachment
2 - when you run Application, a big frame is created.
3 - Enter le number of widgets you want to create (1000 / 2000).
4 - repeat step 3
During the widgets creation, you may run Netscape for example
in order to stress the PC.
Soon, program will stop with a NullPointerException.
Customer really need to have a OutOfMemoryException when memory
is exhausted. This is critical for him to handle this case.
A lot of widgets are created.
When the PC is loaded, memory can be exhausted.
In this case, the application doesn't get an OutOfMemoryException as expected
per Java API and new method will just return a null.
The application can't handle properly this kind of situation.
The application then crashes or from time to time, Windows 95 hangs !
Configuration:
~~~~~~~~~~~~~
JDK 1.1.2 (this is worse with 1.1)
Windows 95 platform.
Test Case :
~~~~~~~~~
1 - Two files (Application.java, MainFrame.java) are in attachment
2 - when you run Application, a big frame is created.
3 - Enter le number of widgets you want to create (1000 / 2000).
4 - repeat step 3
During the widgets creation, you may run Netscape for example
in order to stress the PC.
Soon, program will stop with a NullPointerException.
Customer really need to have a OutOfMemoryException when memory
is exhausted. This is critical for him to handle this case.
- backported by
-
JDK-2015801 Application doesn't get OutOfMemoryException as expected
-
- Closed
-
- duplicates
-
JDK-4034817 Too many dialogs cause out of memory errors.
-
- Closed
-