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.
55 duplicates so far ... It looks like similar issue was fixed for NB 6.0 (issue 119557), but few reports are from NB 6.0 FCS builds and few from 6.0.1 builds built after NB 6.0 had released. Build: NetBeans IDE 6.0 RC1 (Build 200711131200) VM: Java HotSpot(TM) Client VM, 1.6.0-b105 OS: Windows XP, 5.1, x86 User comments: STACKTRACE: (first 10 lines) java.lang.ArrayIndexOutOfBoundsException: -1 at org.netbeans.lib.editor.util.GapList.get(GapList.java:459) at org.netbeans.lib.editor.util.FlyOffsetGapList.elementOffset(FlyOffsetGapList.java:133) at org.netbeans.lib.lexer.EmbeddedTokenList.tokenOffset(EmbeddedTokenList.java:228) at org.netbeans.lib.lexer.inc.TokenListUpdater.update(TokenListUpdater.java:218) at org.netbeans.lib.lexer.TokenHierarchyUpdate.updateTokenListByModification(TokenHierarchyUpdate.java:338) at org.netbeans.lib.lexer.TokenHierarchyUpdate$TLLInfo.update(TokenHierarchyUpdate.java:507) at org.netbeans.lib.lexer.TokenHierarchyUpdate.processLevelInfos(TokenHierarchyUpdate.java:314) at org.netbeans.lib.lexer.TokenHierarchyUpdate.update(TokenHierarchyUpdate.java:143) at org.netbeans.lib.lexer.TokenHierarchyOperation.textModified(TokenHierarchyOperation.java:429) at org.netbeans.spi.lexer.TokenHierarchyControl.textModified(TokenHierarchyControl.java:99)
Created attachment 61390 [details] stacktrace
*** Issue 133279 has been marked as a duplicate of this issue. ***
This issue has already 100 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=12049
I'm not able to reproduce the problem in the recent daily builds. Could anyone please attach a source file and instructions of how the problem can be reproduced? I've tried without success to simulate according to the reports at the statistics page. BTW today's fixing of issue 137579 might influence this problem too (in case the problem would no longer be reproducible).
Should be fixed by changes in issue 137685.
v