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.
I mounted new filesystem under Filesystems tab, during "mounting" number of various exceptions (the primary was ArrayIndexOutOfBoundsExc) was thrown, then all filesystems were unmounted and then IDE deadlocked.
Created attachment 7571 [details] excs stack traces
Created attachment 7572 [details] full thread dump
Milan, this looks like duplicate of issue 27518 which I fixed on Monday. Could you please try it on the latest build and reopen if necessary. Thanx, David *** This issue has been marked as a duplicate of 27518 ***
Well, I reproduced those exceptions on yesterdays build 20021002-1458. I will test todays build and we'll see.
Are you really sure it's duplicate of #27518? I just "generated" new set of exceptions (will attach) on todays build by simple mounting of filesystem.
Created attachment 7579 [details] exc stack traces
ArrayIndexOutOfBounds is also thrown when I do unmount on filesystem.
Created attachment 7582 [details] umount exc stack trace
I closed this because in your first attachments I saw NPE in ContainersList$Updater which I fixed in issue 27518. In your new attachments they gone, but the ArrayOOB exception is still there. I'm going to work on it. The filesystem you are mounting/unmounting - do they have any relevance to your opened projects? Are you for example unmounting filesystem with opened projects on it or something like that? Because just by mounting a new FS and unmount I do not get any exceptions. Also is order of your steps: start the clean IDE, mount FS, unmount FS. Or do you also must do something on projects tab? Thanx for info.
I mounted and unmounted the same dir. The dir was irelevant to project contents.
Very important step is missing: to reproduce those excs you need to do something with projects, at least expand all project nodes, or create some project.
This is most probably side effect of issue 27815. Please reopen if it happens again after issue 27815 was fixed. *** This issue has been marked as a duplicate of 27815 ***
Verified.