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 60902 - StackOverFlow when opening Netbeans
Summary: StackOverFlow when opening Netbeans
Status: CLOSED DUPLICATE of bug 61136
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@java
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-07-13 07:04 UTC by bonej010
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Messages.log requested in error (304.31 KB, text/plain)
2005-07-13 07:05 UTC, bonej010 		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 bonej010 2005-07-13 07:04:11 UTC 
Hi

I am getting the error 

"A java.lang.StackOverflowError exception has occurred.  Please report this at 
http://www.netbeans.org/issues.html, including a copy of your messages.log 
file as an attachment.  The messages.log file is located in your c:\documents 
and settings\sstair\.netbeans\4.1\var\log folder."

while netbeans is loading. Attached please find the messages.log file as
requested. Note that Netbeans does not load afterwards.

Thanks and Regards
Joseph.
Comment 1 bonej010 2005-07-13 07:05:34 UTC 
Created attachment 23072 [details]
Messages.log requested in error
Comment 2 Milan Kubec 2005-07-20 14:47:35 UTC 
Developers please evaluate. Would it help if reporter attaches his userdir or
project?

Reporter, are you able to reproduce this issue with clean userdir (use --userdir
argument on cmd line or modify etc/netbeans.conf file)?
Comment 3 Martin Matula 2005-07-20 15:21:04 UTC 
Sorry, without a stacktrace it is impossible to find out what's wrong - we are
not able to reproduce this. Could you please try to run NetBeans with
-J-Dperf.refactoring=true flag on the commandline and attach the new log file?
This could at least give us more information on mounting of which CP element is
failing.
Comment 4 Martin Matula 2005-09-06 13:49:25 UTC 

*** This issue has been marked as a duplicate of 61136 ***