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 183625 - [69cat] StackOverflowError
Summary: [69cat] StackOverflowError
Status: RESOLVED DUPLICATE of bug 183607
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-07 07:37 UTC by Peter Nabbefeld
Modified: 2010-04-08 07:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
My log (481.30 KB, text/plain)
2010-04-07 07:37 UTC, Peter Nabbefeld
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2010-04-07 07:37:50 UTC
Created attachment 96845 [details]
My log

See http://statistics.netbeans.org/analytics/exception.do?id=366971

Exception reporter told me:
Please update your build of NetBeans to the latest build of 6.5 where bug #111722 is fixed. If you are already using a newer build new bug will be filled automatically. 

That's wrong, as I've used latest daily build (201004070201).
Exception pops up on first start.
Comment 1 Peter Pis 2010-04-07 07:51:01 UTC
Any steps to reproduce?
Comment 2 Peter Nabbefeld 2010-04-07 10:40:05 UTC
1. Did You probably install and start the build? As it has popped up on startup,
   You'd get the exception, too.

2. Did You look at the IDE log?
Comment 3 Peter Nabbefeld 2010-04-07 14:56:39 UTC
Looking again at the exceptions report, there're now much more, and it seems related to parsing.FileObject. If possible, please also have a look at those reports, and move them to a different id, assigned to this bug.
Comment 4 Peter Pis 2010-04-08 07:07:50 UTC
Of course I installed and started that build with no exception.

Couldn't it happen that you nb user directory is somehow corrupted? Could you please try to start NB with another fresh nb user directory?
Comment 5 Peter Pis 2010-04-08 07:53:14 UTC

*** This bug has been marked as a duplicate of bug 183607 ***