StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POJava Suspect Memory Leak in Swing Components
primarykey
Id
18995022
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2013-09-25T02:03:20.787
FavoriteCount
0
LastActivityDate
2013-09-25T02:41:35.010
LastEditDate
2013-09-25T02:41:35.010
LastEditorUserId
1176061
OwnerUserId
2784961
ParentId
0
PostTypeId
1
Score
1
ViewCount
325
LastEditorDisplayName
text
Body
I have an out of memory exception when working with <code>javax.Swing</code> and here's what I did. I loaded 16 jpgs (70*70 pixels each) and had 16 <code>Jbuttons</code>. I set the <code>ImageIcon</code> of the <code>JButtons</code> to different jpgs very quickly in a loop, basically as quickly as my CPU can handle . The memory usage is increased radically. The problem is, I never reloaded image. There are only 16 images and all the assignments are passed by reference right? I run Eclipse Memory Analyzer and here's what I got: One instance of "java.awt.image.FilteredImageSource" loaded by " &lt system class loader &gt " occupies 703,066,368 (43.58%) bytes. The instance is referenced by sun.awt.image.ToolkitImage @ 0x7859cef60 , loaded by " &lt system class loader &gt ". The memory is accumulated in one instance of "java.util.Hashtable$Entry[]" loaded by "&lt system class loader &gt". Keywords java.awt.image.FilteredImageSource java.util.Hashtable$Entry[] Can I suspect there's a memory leak in Java's swing implementation? Any ideas? Basically the code looks like: <pre><code> public class Test{ private static ImageIcon[] imgIcon; private static JButton[] buttons; private static JFrame myFrame; public static void main(String[] args){ myFrame = new JFrame(new GridLayout()); for(int i = 0; i &lt 16; i ++){ imgIcon[i] = //load the imageIcons buttons[i] = new JButton(); myFrame.add(buttons[i]); } myFrame.pack(); myFrame.setVisible(true); new Thread(new Runnable(){ @Override public void run(){ while(true){ for(int i = 0; i &lt 16; i ++){ SwingUtilities.invokeAndWait(new Runnable(){ public void run(){ buttons[i].setIcon(imgIcon[/*random num 1-16*/]); }); } } } }).start(); } } </code></pre> Please disregard the apparent anti-pattern here because I abstracted away a lot of things going on in the new thread.
Tags
<java><swing><memory-leaks>
Title
Java Suspect Memory Leak in Swing Components
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDeadChex
UserOwnerUserId
1. USfleetC0m
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POJava Suspect Memory Leak in Swing Components
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
2. VO
 singulars
 PostPostId
 POJava Suspect Memory Leak in Swing Components
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.