JDK-6709152 : java.lang.OutOfMemoryError is still getting thrown while reloading some of the applets
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u10,7
- Priority: P3
- Status: Closed
- Resolution: Won't Fix
- OS: windows,windows_vista
- CPU: generic,x86
- Submitted: 2008-05-30
- Updated: 2010-11-16
- Resolved: 2010-11-16
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.
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.
| JDK 7 |
|---|
7Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Some of the applets are still throwing "java.lang.OutOfMemoryError: Java heap space" when page is refreshed or reloaded multiple times. Scenario I: Try loading the following applet inside the browser, If on refreshing the page java.lang.OutOfMemoryError exception is getting thrown then bug is reproduced: http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/ALC/MemoryTest.html or http://nicole1.sfbay.sun.com:8080/plugin_tests/JNLPSupport/DnD/ALC/MemoryTest.html Note: In this particular test we are defining a byte array, if we set array to null inside the destroy method then no "java.lang.OutOfMemoryError" is getting thrown.
Comments
|