This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 9254 - "Out of memory" was occured.
Summary: "Out of memory" was occured.
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P4 normal (vote)
Assignee: issues@platform
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-01-26 15:49 UTC by ehucka
Modified: 2008-12-22 16:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2001-01-26 15:49:19 UTC
I cannot reproduce it.
I have executed several times (about 20) some application with a lot of objects
by Internal execution.
Comment 1 Jesse Glick 2001-01-26 16:27:59 UTC
And did this application keep any static references to those objects?
Comment 2 ehucka 2001-01-29 16:20:59 UTC
Yes, some classes have static references to objects. Can classes remain loaded
in IDE if their internal executed process is finished?
Comment 3 Jesse Glick 2001-01-29 16:33:59 UTC
Well, two things can happen:

1. After the app is finished, the classloader used for the app will probably
stick around for a while, until you e.g. recompile some file in Filesystems and
use internal execution again, and a GC is run. So do not expect memory to be
released *immediately* in any case.

2. If any part of your app adds a static reference to some object it created to
some actual part of the IDE (including e.g. hidden but not disposed windows, I
think), those objects, their implementing classes, referred-to classes, the
classloader, etc. cannot be garbage-collected.

If either (1) or (2) covers your situation then please mark as INVALID.
Comment 4 ehucka 2001-01-31 10:48:59 UTC
It seems that it's the 1. There isn't any association to IDE. But memory still
remains occupied after e.g. 1 hour by this app. Memory usage isn't decreasing.
Comment 5 ehucka 2003-01-15 11:48:47 UTC
Verified invalid.
Comment 6 Quality Engineering 2003-07-01 16:26:41 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.