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 148674

Summary: [65cat] ArrayIndexOutOfBoundsException: 2174
Product: editor Reporter: goeh <goeh>
Component: LexerAssignee: Miloslav Metelka <mmetelka>
Status: RESOLVED FIXED    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: All   
OS: All   
URL: http://statistics.netbeans.org/exceptions/detail.do?id=120423
Issue Type: DEFECT Exception Reporter: 120423
Attachments: stacktrace

Description goeh 2008-09-29 20:16:30 UTC
Build: NetBeans IDE Dev (Build 200809231435)
VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Windows XP, 5.1, x86

User Comments:
goeh: Editing a Grails WebFlow controller.
Double-clicked the word Integer in Integer.valueOf(s) and was about to replace Integer with Long. First I got ArrayIndexOutOfBoundsException then a half second later I got NullPointerException.



Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 2174
        at org.netbeans.lib.lexer.LAState$LargeState.state(LAState.java:408)
        at org.netbeans.lib.lexer.inc.IncTokenList.state(IncTokenList.java:246)
        at org.netbeans.lib.lexer.inc.IncTokenList.replaceTokens(IncTokenList.java:353)
        at org.netbeans.lib.lexer.inc.TokenListUpdater.updateRegular(TokenListUpdater.java:279)
        at org.netbeans.lib.lexer.inc.TokenHierarchyUpdate$UpdateItem.update(TokenHierarchyUpdate.java:346)
        at org.netbeans.lib.lexer.inc.TokenHierarchyUpdate.processLevelInfos(TokenHierarchyUpdate.java:221)
Comment 1 goeh 2008-09-29 20:16:42 UTC
Created attachment 70832 [details]
stacktrace
Comment 2 Miloslav Metelka 2008-10-06 11:56:42 UTC
This should be eliminated by fix of issue 144258.
Comment 3 Miloslav Metelka 2008-10-06 12:01:16 UTC
Since issue 144258 was integrated almost at the time like your testing build was created I would like to ask you to get
a newer dev build and if you would be able to reproduce the problem there please reopen the issue. Thanks.