-
Bug
-
Resolution: Won't Fix
-
P3
-
6u10, 7
-
generic, x86
-
windows, windows_vista
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2202270 | 7 | Henry Jen | P3 | Closed | Fixed | b134 |
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.
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.
- backported by
-
JDK-2202270 java.lang.OutOfMemoryError is still getting thrown while reloading some of the applets
-
- Closed
-
- relates to
-
JDK-6671092 java.lang.OutOfMemoryError thrown with new plugin
-
- Closed
-
-
JDK-6703401 Strong reference to RepaintManager in AppContext keeps components alive too long
-
- Closed
-
-
JDK-6922320 plugin2 should take available heap into consideration when choosing VM to be used for applet
-
- Resolved
-