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 48300 - OutOfMemory Error
Summary: OutOfMemory Error
Status: CLOSED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-01 12:58 UTC by iformanek
Modified: 2007-02-20 18:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2004-09-01 12:58:05 UTC 
After a longer period of profiling, OutOfMemory 
error is thrown
Comment 1 mishadmitriev 2004-09-01 22:35:28 UTC 
Please provide additional information - what kind of profiling did you
use and what program you tried to profile. In some cases, e.g. when
profiling a program with a large and growing number of objects, an
OutOfMemoryError is inevitable if you have too small a heap assigned
to NB, since the profiler allocates some memory for each profiled
object. However, we can probably make it stop profiling (but not the
profiled application) and report the issue gracefully if it detects an
OutOfMemoryError internally. Does it look reasonable?
Comment 2 mishadmitriev 2004-09-18 01:34:40 UTC 
Since concrete data to reproduce this particular problem is not 
provided, I am closing this issue for now.
Comment 3 ehucka 2006-10-09 12:11:45 UTC 
Verification of old issues.
Comment 4 Alexander Kouznetsov 2007-02-12 22:39:02 UTC 
Closing old issues.
Comment 5 Alexander Kouznetsov 2007-02-20 18:32:57 UTC 
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.