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: NetBeans IDE Dev (Build 201002152000) VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07 OS: Windows 7 User Comments: jasonlotito: Closing a project GUEST: When I am trying to diff the file from the CVS Stacktrace: java.lang.IndexOutOfBoundsException: Index: 3, Size: 3 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.netbeans.swing.tabcontrol.DefaultTabDataModel.fireIndicesChanged(DefaultTabDataModel.java:490) at org.netbeans.swing.tabcontrol.DefaultTabDataModel.setTabs(DefaultTabDataModel.java:120) at org.netbeans.core.windows.view.ui.tabcontrol.TabbedAdapter.setTopComponents(TabbedAdapter.java:234) at org.netbeans.core.windows.view.ui.TabbedHandler.setTopComponents(TabbedHandler.java:154)
Created attachment 94332 [details] stacktrace
Created attachment 94391 [details] stacktrace Closed java source file
Created attachment 95164 [details] stacktrace
Created attachment 95255 [details] stacktrace double clicked on an entry in the Call Stack tab in the debugger in order to go to the relevant code associated with the entry in the java editor
Created attachment 95402 [details] stacktrace tried double-click-opening a .java file?
Created attachment 96663 [details] stacktrace Closing a file within the editor.
Created attachment 96802 [details] stacktrace double clicked on an item in the Mercurial status pane in order to open the diff tool
Created attachment 97260 [details] stacktrace
Created attachment 97305 [details] stacktrace
Created attachment 97747 [details] stacktrace opening a file from the mercurial status window
Created attachment 97921 [details] stacktrace opening .java file into editor?
Created attachment 98467 [details] stacktrace Tried to close all documents.
Created attachment 98637 [details] stacktrace
Created attachment 98837 [details] stacktrace I double-clicked on a JSP file in the Projects view. The JSP file was inside a Maven web project. Before that, there were 17 files opened in the editor area (.java, .jsp, .xml, .jpg) and I was about to open a yet another JSP file.
Created attachment 99405 [details] stacktrace
Created attachment 99513 [details] stacktrace 1) in the Services tab, I established a connection to a database 2) expanded some of the database's node's subnodes 3) right-clicked on a node representing a database table 4) from the context menu, I selected "View Data..."
This bug has 142 duplicates in the exception reporter and 37 people on the Cc: list so this is clearly a highly annoying bug - raising priority to P2.
core-main b2b1a0f3ef6c
Integrated into 'main-golden', will be available in build *201005280001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/b2b1a0f3ef6c User: S. Aubrecht <saubrecht@netbeans.org> Log: #180960 - thread synchronization
*** Bug 186913 has been marked as a duplicate of this bug. ***
*** Bug 186701 has been marked as a duplicate of this bug. ***
reopening to be fixed in 6.9 release
The patch look for me, reviewed.
fixed in release69 clone as 6ceef8c0ee69
*** Bug 190112 has been marked as a duplicate of this bug. ***
*** Bug 180957 has been marked as a duplicate of this bug. ***
The bug is reported multiple times to occur in NB 6.9.1 (here or in #190112 or in #180957) so either this is a regression since NB 6.9 or the bug was not fixed properly in NB 6.9. I confirm this happens in NB 6.9.1. It happened several times today in NB 6.9.1 to me (JDK 6u21 32-bit, Windows XP SP3 32-bit). When this (the exception) happens, files cannot be saved. Neither Save nor Save All action works. The IDE detects that there are unsaved files while closing and displays the Save dialogue - but it does not save the files even if the user asks to save all unsaved files. Reopened.
the bug is fixed in release69 but for some reason the changeset didn't make it to the release691 clone
switching target to 6.10 so that exceptions reporter doesn't open new issues with the same stack trace
*** Bug 185962 has been marked as a duplicate of this bug. ***
*** Bug 183940 has been marked as a duplicate of this bug. ***
*** Bug 190256 has been marked as a duplicate of this bug. ***
Agreed with integration into Patch 2
*** Bug 191261 has been marked as a duplicate of this bug. ***
Are you really sure you have included the fix in Patch 3? I encountered the exception the first day I applied Patch 3 (of NB 6.9.1). Before the last update, I did not see the exception for weeks.
(In reply to comment #35) > Are you really sure you have included the fix in Patch 3? I encountered the > exception the first day I applied Patch 3 (of NB 6.9.1). Before the last > update, I did not see the exception for weeks. i didn't build the patch, you need to check with RE
*** Bug 186669 has been marked as a duplicate of this bug. ***