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.
dev build 200708271200 When I open certain Java files the attached exception is thrown once every three seconds, rendering the editor totally unusable. This seems to be dependent on the contents of the Java file but it is reproducible 100% of the time.
Created attachment 47552 [details] stack-trace
Created attachment 47553 [details] Source-code which triggers the exception
*** Issue 113749 has been marked as a duplicate of this issue. ***
Build: NetBeans IDE Dev (Build 200708271200) VM: Java HotSpot(TM) Client VM, 1.7.0-ea-b18 OS: Windows XP, 5.1, x86 User Comments:
Created attachment 47557 [details] stacktrace
*** Issue 113940 has been marked as a duplicate of this issue. ***
Should be OK now: Checking in src/org/netbeans/modules/java/hints/StaticAccess.java; /cvs/java/hints/src/org/netbeans/modules/java/hints/StaticAccess.java,v <-- StaticAccess.java new revision: 1.11; previous revision: 1.10 done Checking in test/unit/src/org/netbeans/modules/java/hints/infrastructure/TreeRuleTestBase.java; /cvs/java/hints/test/unit/src/org/netbeans/modules/java/hints/infrastructure/TreeRuleTestBase.java,v <-- TreeRuleTestBase.java new revision: 1.8; previous revision: 1.7 done
Build: NetBeans IDE Dev (Build 200708250000) VM: Java HotSpot(TM) Client VM, 1.5.0_07-87 OS: Mac OS X, 10.4.10, i386 User Comments: typing in the damn editor :)... the ide seems to go crazy when I have a groovy file open for editing (no plugin)
Created attachment 47739 [details] stacktrace
*** Issue 114177 has been marked as a duplicate of this issue. ***
Build: NetBeans IDE Dev (Build 200708280000) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b06 OS: Windows Vista, 6.0, x86 User Comments:
Created attachment 47883 [details] stacktrace
Build: NetBeans IDE Dev (Build 200708270000) VM: Java HotSpot(TM) Client VM, 1.6.0_02-b05 OS: Linux, 2.6.20-gentoo-r6, i386 User Comments:
Created attachment 47947 [details] stacktrace
Reopening - reproduced in NetBeans IDE Dev (Build 200809281401) http://statistics.netbeans.org/exceptions/detail.do?id=124888
http://hg.netbeans.org/main?cmd=changeset;node=359277a61c8c
Integrated into 'main-golden', will be available in build *200810090201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/359277a61c8c User: Jan Lahoda <jlahoda@netbeans.org> Log: #113933: correct translation of offsets.
This issue is marked as the fix for there stacktraces: http://statistics.netbeans.org/analytics/detail.do?id=1722 but these traces still appear, so either the fix did not fix everything or the stacktraces are assigned the wrong issue.
The exception reporter should have create a new issue, as the important part of the new exceptions are different that the original ones: java.lang.IndexOutOfBoundsException: Illegal OffsetKind[offset=-1] in org.netbeans.modules.editor.NbEditorDocument@1672664, mimeType = 'text/x-jsp', kitClass = null, length = 1640, file=org.netbeans.modules.web.core.jsploader.JspDataObject@18b3e8b[/home/kiroffbg/Projects/webdine/trunk/web/pages/setup/loyalty/main.jsp] used by org.netbeans.modules.web.core.jsploader.BaseJspEditorSupport@1768f6e. at org.openide.text.PositionRef$Manager$OffsetKind.(PositionRef.java:657) at org.openide.text.PositionRef.(PositionRef.java:84) at org.openide.text.CloneableEditorSupport.createPositionRef(CloneableEditorSupport.java:1432) at org.netbeans.modules.editor.hints.HintsControllerImpl.linePart(HintsControllerImpl.java:229) at org.netbeans.spi.editor.hints.ErrorDescriptionFactory.createErrorDescription(ErrorDescriptionFactory.java:127) at org.netbeans.spi.editor.hints.ErrorDescriptionFactory.createErrorDescription(ErrorDescriptionFactory.java:120) at org.netbeans.modules.csl.hints.infrastructure.GsfHintsManager.createDescription(GsfHintsManager.java:513) at org.netbeans.modules.csl.hints.GsfHintsProvider$2.run(GsfHintsProvider.java:316) at org.netbeans.modules.csl.hints.GsfHintsProvider$2.run(GsfHintsProvider.java:338) at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:129) at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:113)
http://hg.netbeans.org/jet-main/rev/6b589056c5fc
Integrated into 'main-golden', will be available in build *200909131354* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/6b589056c5fc User: Vita Stejskal <vstejskal@netbeans.org> Log: #113933: better check for invalid hint ranges supplied by language hints providers
Build: NetBeans IDE Dev (Build 200909220201) VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02-92, Java(TM) SE Runtime Environment, 1.6.0_15-b03-226 OS: Mac OS X, 10.5.8, x86_64 User Comments: Stacktrace: org.netbeans.modules.parsing.spi.ParseException at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:192) at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:99) at org.netbeans.modules.csl.hints.GsfHintsProvider.run(GsfHintsProvider.java:293) at org.netbeans.modules.csl.hints.GsfHintsProvider.run(GsfHintsProvider.java:98) at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:654) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
Created attachment 88204 [details] stacktrace
Created attachment 94292 [details] stacktrace
Created attachment 94293 [details] stacktrace
Created attachment 94295 [details] Sample class file which trigger the exception
Created attachment 95011 [details] stacktrace
Created attachment 95012 [details] stacktrace
Created attachment 95013 [details] stacktrace
Created attachment 97728 [details] stacktrace
Created attachment 97729 [details] stacktrace
Still present in 7.0.1.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/351260216703 User: Jan Lahoda <jlahoda@netbeans.org> Log: #113933: ErrorDescriptionFactory.createED(..., int start, int end) should check that start >= 0 and end >= start, so that the stack traces are as useful as possible.
This looks like going through the hints - please have a look and potentially reassign if the problem should be fixed elsewhere. Thanks.
Or maybe it is already fixed - I did not notice any new reports after 10.10.2011 - if it is the case please close. I am not sure why it was reopened.
Typically, this is a problem in the caller to ErrorDescriptionFactory.create, but as the part of the stacktrace inside EDF.create had too much elements, all were duplicated to this one. In 351260216703 I have put asserts much higher in the stacktrace, so if this happens, separate bugs should be created for separate callers. I have also found a few exceptions coming from java.hints, corrected in: http://hg.netbeans.org/jet-main/rev/61067eb21735
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/61067eb21735 User: Jan Lahoda <jlahoda@netbeans.org> Log: #113933: making some more Java hints immune to -1 positions in the trees.