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.
This issue was reported manually by jhavlin. It already has 1 duplicates Build: NetBeans IDE 7.2 (Build 201207171143) VM: Java HotSpot(TM) 64-Bit Server VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b05 OS: Windows 7 User Comments: pfabier: Impossible to stop "Background scanning of projects" Stacktrace: javax.swing.text.BadLocationException: Invalid offset=320 not within <0, 317> at org.netbeans.editor.Utilities.checkOffsetValid(Utilities.java:1345) at org.netbeans.editor.Utilities.checkOffsetValid(Utilities.java:1340) at org.netbeans.editor.Utilities.getRowStart(Utilities.java:198) at org.netbeans.editor.Utilities.getRowStart(Utilities.java:181) at org.netbeans.modules.groovy.editor.api.StructureAnalyzer.addFolds(StructureAnalyzer.java:346) at org.netbeans.modules.groovy.editor.api.StructureAnalyzer.addFolds(StructureAnalyzer.java:371)
Created attachment 134467 [details] stacktrace
This bug contains exception reports extracted from bug 218281. StructureAnalyzer.addFolds probably doesn't handle BadLocationException correctly. Please evaluate. Thank you.
It would be great to have a reproducible test case. pfabier, do you know what code have you been editing when the exception occurs?
Created attachment 136137 [details] stacktrace I have PHP file with following structure: <?php ?> | Place cursor instead of | and try to make comment with comment button or via CTRL+SHIFT+C and this exception appears => expected behaviour after the pushing comment button is that nothing will be happened
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=200666
Created attachment 136859 [details] stacktrace .
After separating PHP part and showtodos part, only one report remains from groovy area (from NB 7.2). It's not simple to fix the problem without reproducible test case, so closing the issue as INCOMPLETE for now. Please if anyone will get into this again (using groovy support), attach the source code you were editing when the exception occurs and reopen the issue. Thanks in advance!