public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abalkiss at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug SWING/22151] New: JInternalFrame causes OutOfMemory error when maximized.
Date: Wed, 22 Jun 2005 19:07:00 -0000	[thread overview]
Message-ID: <20050622190651.22151.abalkiss@redhat.com> (raw)

JInternalFrame causes OutOfMemory error when maximized.

Run the test case below, maximize the JInternalFrame, wait a while.  OutOfMemory
error.  

When the JInternalFrame is positioned at (10,10) rather than (60,60) the error
doesn't occur.

==TEST CASE==
import java.awt.*;
import javax.swing.*;
import java.io.*;

public class OutOfMemory {
   public static void main(String[] a) throws IOException{
      JFrame myFrame = new JFrame("Outer");
      myFrame.setSize(300,300);
      myFrame.setContentPane(new JDesktopPane());
      JInternalFrame f = new JInternalFrame("Internal");
      f.setSize(200,200);
      f.setVisible(true);
      f.setClosable(true);
      f.setMaximizable(true);
      f.setResizable(true);
      f.setIconifiable(true);
      /* IF THE FOLLOWING LINE IS CHANGED TO f.setLocation (10,10)
         no OutOfMemory error occurs! */
      f.setLocation(60,50);
      myFrame.add(f);
      myFrame.setVisible(true);
   }
}

-- 
           Summary: JInternalFrame causes OutOfMemory error when maximized.
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: SWING
        AssignedTo: abalkiss at redhat dot com
        ReportedBy: abalkiss at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22151


             reply	other threads:[~2005-06-22 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 19:07 abalkiss at redhat dot com [this message]
2005-06-23 17:20 ` [Bug SWING/22151] " abalkiss at redhat dot com
2005-06-23 18:21 ` abalkiss at redhat dot com
2005-06-23 18:22 ` abalkiss at redhat dot com
2005-09-01 18:27 ` [Bug swing/22151] " abalkiss at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050622190651.22151.abalkiss@redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).