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 100731 - Creator not launching, A java.lang.OutOfMemoryError exception has occurred.
Summary: Creator not launching, A java.lang.OutOfMemoryError exception has occurred.
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2007-04-12 07:28 UTC by rainitin
Modified: 2007-04-25 01:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
/.Creator/2_1/var/log "Out of memory exception" (206.02 KB, application/octet-stream)
2007-04-12 07:30 UTC, rainitin 		Details
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 rainitin 2007-04-12 07:28:30 UTC 
The creatorIDE is not getting launched,a dialog box appears which says Out of
memory Exception and in details is says "java.lang.OutOfMemoryError: Java heap
space".I have restarted the syatem(Solaris sparc ) but the problem sustains.
Comment 1 rainitin 2007-04-12 07:30:31 UTC 
Created attachment 40798 [details]
/.Creator/2_1/var/log "Out of memory exception"
Comment 2 Milan Kubec 2007-04-12 07:38:33 UTC 
Please report this error to Creator team. Thanks.
Comment 3 Marian Mirilovic 2007-04-12 08:56:50 UTC 
rainitin,
could you please tell us what did you work on (steps) before this happened ?
Comment 4 _ rkubacki 2007-04-12 18:12:33 UTC 
http://wiki.netbeans.org/wiki/view/NetBeansUserFAQ#section-NetBeansUserFAQ-Performance
and especially http://wiki.netbeans.org/wiki/view/FaqNetBeansAndOOME contains
tips how to deal with this kind of errors.
Comment 5 Ch Nguyen 2007-04-25 01:56:42 UTC 
Please use the work around as indicated by rkubaki to configure the memory heap
size.  If the problem still occurs, you can reopen the bug and provide us the
steps how to reproduce it.