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.
Build 200409061800 Random behavior, happend twice (only in this build) - maybe caused by issue 47568 fix. 1) There's exception in IDE startup -- see attached IDE log 2) Since this exception you can't change browser - similar exceptions appear, no IDE restart helps. Notice: I can provide saved userdirs with this problem. This should be fixed in beta2.
Created attachment 17432 [details] IDE log with IllegalStateException
I found reproducible steps: 1) Run IDE with clean userdir 2) Change 'Web Browser' to MS IE (Options|IDE Configuration|System|System Settings|Web Browser) 3) Invalidate MS IE path - change the path (in Options|IDE Configuration|Server and External Tool Settings|Web Browsers|Internet Explorer) e.g. to "...\_iexplorer.exe ..." 4) Exit IDE 5) Run IDE 6) EXCEPTION on startup (see previous attached IDE log) BTW: My first experience with this bug was in userdir where I didn't change the Web Browsers pathes (I only set default Web Browser, restarted IDE with different JDK 1.4/1.5 and did some other web related stuff) and this exception was there too.
Would there be a way to simulate this on linux?
The bug report says that somebody has to change the browser command line to point to non existing file (_iexplorer.exe), if this is true, then this is not p2 and maybe even p3.
*** Issue 48690 has been marked as a duplicate of this issue. ***
I still have no idea how situation like this can happen. I cannot simulate the problem. Definitively not on linux, but I also tried that on win2000 and everything worked. I'll attach a patch that might fix the problem.
Created attachment 17572 [details] Please try to simulate the problem with this patch
Until further info given, I have to close this as works for me, as I was unable to simulate the problem.
*** Issue 48562 has been marked as a duplicate of this issue. ***
Martin, I believe it is safe to say the problem is not fixed yet. I remember seeing it in a build two days ago. When I see it again I will reopen this issue.
Oops, mistakenly reopened issue. Reverting back to closed until I can reproduce it on newest build.
Reproducible scenario works fine now with the patch. I hope it will help also in cases which are not based on invalid browser path.
AFAIK, the patch was not applied, so I am reopening. Also raising priority because it is random but frequent issue and no workaround exists. I am able to reproduce it the following way: - set Swing HTL Browser in the Setup Wizard - open browser (View|Web Browser) - restart IDE - close browser, restart IDE, open browser etc. (play a while with IDE and you will get the exception) With the patch I haven't faced it so far. IMO it should be fixed in beta2 too.
I think you can reproduce it fairly easily in the following manner: When you ask Netbeans to shut down, it pops up some dialog about "serializing your settings" or something similar. If you then launch a new instance of Netbeans while this is running, the new instance will say it detected Netbeans was not properly shut down, are you sure you wish to continue? Say no (don't clobber any settings). Both instances should have shut down at this point. Now, restart Netbeans a 3rd time and you should end up with the corrupt settings. A workaround for this bug is to wipe out the <userdir>/dev/var/cache directory but the next time you restart it needs to rebuild the classpath and this takes a long while so this workaround is painful as well. Anyway, assuming you are able to reproduce the bug using the aforementioned method, you should now be able to fix it. You should make absolutely sure that the shutdown/startup operations are atomic and one can not clobber the settings of the other. I suspect this can be very hard/impossible to do under pure Java but you guys probably know more about this than I.
openide$ cvs -q ci -m "#48590: People report that this is the fix for multiple equal pairs in the AbstractLookup. I have never seen such problem, so I cannot judge. The way I manage to simulate it in unit tests is pretty ugly and relies on changing of behaviour of equals during the life time of the pair. Well, maybe someone in the IDE is really doing that" ? X.diff ? TestThatCanBeAddedIntoLookup.diff ? ${build.test.unit.results.dir} Checking in src/org/openide/util/lookup/InheritanceTree.java; /cvs/openide/src/org/openide/util/lookup/InheritanceTree.java,v <-- InheritanceTree.java new revision: 1.34; previous revision: 1.33 done Processing log script arguments... More commits to come... Checking in test/unit/src/org/openide/util/lookup/AbstractLookupBaseHid.java; /cvs/openide/test/unit/src/org/openide/util/lookup/AbstractLookupBaseHid.java,v <-- AbstractLookupBaseHid.java new revision: 1.15; previous revision: 1.14
It is no longer considered as beta2-candidate since it doesn't occur so often in pre-beta2 builds. Should be mentioned in Release notes with workaround: "If you get this exception (java.lang.IllegalStateException: Duplicate pair in treePair1: ...) with any browser, exit IDE and delete files folder-lookup.ser and lookup-stamp.txt in $USERDIR/var/cache" BTW: Jirka Skrivanek's steps are reproducible on 200409061800 build in several IDE restarts, with the patch they work fine.
*** Issue 49083 has been marked as a duplicate of this issue. ***
Verified.
*** Issue 49015 has been marked as a duplicate of this issue. ***
*** Issue 49758 has been marked as a duplicate of this issue. ***
*** Issue 49866 has been marked as a duplicate of this issue. ***
*** Issue 49925 has been marked as a duplicate of this issue. ***
*** Issue 50016 has been marked as a duplicate of this issue. ***
As of 4.0 beta 2, this is still an issue. The workaround (deleting folder-lookup.ser and lookup-stamp.txt from <userdir>\var\cache) *does* work, or at least it did in my case. I am unable to test the patch because I'm not working with the NB source. If they would be helpful to anyone else testing this, I saved copies of the two files I deleted. Just let me know.
The patch has been verified in trunk (hence the VERIFIED status). You can download latest daily build of NetBeans where this patch is applied (even in all daily builds since 2004-09-15).
*** Issue 50238 has been marked as a duplicate of this issue. ***
*** Issue 50210 has been marked as a duplicate of this issue. ***
*** Issue 50449 has been marked as a duplicate of this issue. ***
*** Issue 50450 has been marked as a duplicate of this issue. ***
*** Issue 50448 has been marked as a duplicate of this issue. ***
*** Issue 50535 has been marked as a duplicate of this issue. ***
*** Issue 50190 has been marked as a duplicate of this issue. ***
*** Issue 50678 has been marked as a duplicate of this issue. ***
*** Issue 50424 has been marked as a duplicate of this issue. ***
*** Issue 50726 has been marked as a duplicate of this issue. ***
*** Issue 50836 has been marked as a duplicate of this issue. ***
*** Issue 50918 has been marked as a duplicate of this issue. ***
*** Issue 51032 has been marked as a duplicate of this issue. ***
*** Issue 51144 has been marked as a duplicate of this issue. ***
*** Issue 51237 has been marked as a duplicate of this issue. ***
*** Issue 51232 has been marked as a duplicate of this issue. ***
*** Issue 51213 has been marked as a duplicate of this issue. ***
*** Issue 51165 has been marked as a duplicate of this issue. ***
*** Issue 51351 has been marked as a duplicate of this issue. ***
*** Issue 51493 has been marked as a duplicate of this issue. ***
*** Issue 51494 has been marked as a duplicate of this issue. ***
*** Issue 51515 has been marked as a duplicate of this issue. ***
*** Issue 51592 has been marked as a duplicate of this issue. ***
*** Issue 51594 has been marked as a duplicate of this issue. ***
*** Issue 51785 has been marked as a duplicate of this issue. ***
*** Issue 51548 has been marked as a duplicate of this issue. ***
*** Issue 51546 has been marked as a duplicate of this issue. ***
*** Issue 51860 has been marked as a duplicate of this issue. ***
*** Issue 51915 has been marked as a duplicate of this issue. ***
*** Issue 51816 has been marked as a duplicate of this issue. ***
*** Issue 52074 has been marked as a duplicate of this issue. ***
*** Issue 51009 has been marked as a duplicate of this issue. ***
*** Issue 51538 has been marked as a duplicate of this issue. ***
*** Issue 51383 has been marked as a duplicate of this issue. ***
*** Issue 51985 has been marked as a duplicate of this issue. ***
*** Issue 52309 has been marked as a duplicate of this issue. ***
*** Issue 52290 has been marked as a duplicate of this issue. ***
Wow, 51 duplicates so far!
*** Issue 52359 has been marked as a duplicate of this issue. ***
*** Issue 52734 has been marked as a duplicate of this issue. ***
*** Issue 52630 has been marked as a duplicate of this issue. ***
*** Issue 53849 has been marked as a duplicate of this issue. ***
*** Issue 55108 has been marked as a duplicate of this issue. ***