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 212149 - IllegalStateException: Instance already exists
Summary: IllegalStateException: Instance already exists
Status: VERIFIED INCOMPLETE
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-07 06:24 UTC by Jiri Skrivanek
Modified: 2012-05-14 07:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 187701

Attachments
stacktrace (2.16 KB, text/plain)
2012-05-07 06:24 UTC, Jiri Skrivanek 		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 Jiri Skrivanek 2012-05-07 06:24:21 UTC 
This bug was originally marked as duplicate of bug 193017, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201205060400)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b20
OS: Windows 7

User Comments:
jskrivanek: After JUnit was installed in freshly started IDE.




Stacktrace: 
java.lang.IllegalStateException: Instance already exists
   at org.netbeans.core.windows.WindowManagerImpl.<init>(WindowManagerImpl.java:124)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
   at java.lang.Class.newInstance0(Class.java:372)
Comment 1 Jiri Skrivanek 2012-05-07 06:24:42 UTC 
Created attachment 119138 [details]
stacktrace
Comment 2 Stanislav Aubrecht 2012-05-07 06:39:53 UTC 
I've fixed the diagnostics code in core-main 6e77855b7ffa
Please reopen when reproduced again, thanks.