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 195666 - [70cat] ArrayIndexOutOfBoundsException: 3
Summary: [70cat] ArrayIndexOutOfBoundsException: 3
Status: RESOLVED INVALID
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: David Strupl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-18 17:45 UTC by alied
Modified: 2011-02-20 19:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 176792

Attachments
stacktrace (1.93 KB, text/plain)
2011-02-18 17:45 UTC, alied 		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 alied 2011-02-18 17:45:26 UTC 
Build: NetBeans IDE Dev (Build 201101100000)
VM: Java HotSpot(TM) Client VM, 19.1-b02, Java(TM) SE Runtime Environment, 1.6.0_24-b07
OS: Windows XP

User Comments:
alied: I can't tell. I just noticed the red mark in the status bar and reported. I promess to pay more attention the next time




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 3
   at org.netbeans.lib.editor.util.GapList.get(GapList.java:462)
   at org.netbeans.modules.editor.lib2.view.EditorBoxView.getView(EditorBoxView.java:203)
   at org.netbeans.modules.editor.lib2.view.DocumentView.getView(DocumentView.java:1136)
   at org.netbeans.editor.EditorUI$3.run(EditorUI.java:778)
   at org.netbeans.modules.editor.lib2.view.DocumentView.runTransaction(DocumentView.java:329)
   at org.netbeans.editor.Utilities$3.run(Utilities.java:1407)
Comment 1 alied 2011-02-18 17:45:34 UTC 
Created attachment 106163 [details]
stacktrace
Comment 2 alied 2011-02-18 18:38:59 UTC 
After downloading and installing NetBeans IDE Dev (Build 201102180501), It hasn't happened anymore.
It happened after a (very) outdated build of NB dev updated rg.netbeans.modules.editor.lib2/1 [1.36.0.6 6 201102180501]
I hope that's the reason. I'll keep a eye on it.
Comment 3 alied 2011-02-20 19:47:51 UTC 
Since it has not happened again after instaling the latest build (201102180501), change it to invalid.