-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0, 1.4.1, 1.4.2
-
beta2
-
generic, x86
-
generic, windows_2000, windows_xp
Creating a large number of JInternalFrames in SwingSet2 is causing the application to throw an OutOfMemoryError. This happens when running the scenario on a XP L&F. To reproduce, do the following:
- Create about 200+ internal frames while switching between JLF and the
Windows L&F (XP L&F since I was testing on an XP system). I noticed that
as the number of internal frames grew, the XP L&F became slower everytime
you requested SwingSet2 to create a new internal frame. When I switch to
JLF, though, I was able to click away full speed creating new internal
frames. However, when I switched back to XP L&F, it took time for it to
repaint, and when I monitored the memory usage in task manager, I can see
the memory usage grow slowly. On my machine, at about 80K to 85K, the
system finally threw an OutOfMemoryError when I switched from JLF to
XP L&F.
The problem was produced on the latest Mantis build, b18.
###@###.### 2003-03-24
- Create about 200+ internal frames while switching between JLF and the
Windows L&F (XP L&F since I was testing on an XP system). I noticed that
as the number of internal frames grew, the XP L&F became slower everytime
you requested SwingSet2 to create a new internal frame. When I switch to
JLF, though, I was able to click away full speed creating new internal
frames. However, when I switched back to XP L&F, it took time for it to
repaint, and when I monitored the memory usage in task manager, I can see
the memory usage grow slowly. On my machine, at about 80K to 85K, the
system finally threw an OutOfMemoryError when I switched from JLF to
XP L&F.
The problem was produced on the latest Mantis build, b18.
###@###.### 2003-03-24
- duplicates
-
JDK-4748141 First JInternalFrame added to a JDesktop causes memory leak
- Closed
- relates to
-
JDK-4984042 Reliability: SwingBasher throws OutOfMemoryError
- Closed