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 142685 - javax.swing.text.BadLocationException: Invalid offset=1010 not within <0, 1007>
Summary: javax.swing.text.BadLocationException: Invalid offset=1010 not within <0, 1007>
Status: RESOLVED DUPLICATE of bug 138663
Alias: None
Product: ruby
Classification: Unclassified
Component: RHTML (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Torbjorn Norbye
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-02 16:41 UTC by igonef
Modified: 2008-08-04 14:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 66970


Attachments
stacktrace (7.10 KB, text/plain)
2008-08-02 16:41 UTC, igonef
Details

Note You need to log in before you can comment on or make changes to this bug.
Description igonef 2008-08-02 16:41:27 UTC
Build: NetBeans IDE Dev (Build 200807040101)
VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02
OS: Linux, 2.6.18-6-686, i386

User Comments: 


Stacktrace: 
javax.swing.text.BadLocationException: Invalid offset=1010 not within <0, 1007>
        at org.netbeans.editor.Utilities.checkOffsetValid(Utilities.java:1332)
        at org.netbeans.editor.Utilities.getLineOffset(Utilities.java:614)
        at org.netbeans.modules.ruby.rhtml.EmbeddedSectionsHighlighting$Highlights.moveNext(EmbeddedSectionsHighlighting.java:195)
        at org.netbeans.spi.editor.highlighting.support.OffsetsBag.addAllHighlightsImpl(OffsetsBag.java:723)
        at org.netbeans.spi.editor.highlighting.support.OffsetsBag.addAllHighlights(OffsetsBag.java:184)
        at org.netbeans.modules.editor.lib2.highlighting.CompoundHighlightsContainer.updateCache(CompoundHighlightsContainer.java:300)
Comment 1 igonef 2008-08-02 16:41:36 UTC
Created attachment 66387 [details]
stacktrace
Comment 2 Torbjorn Norbye 2008-08-04 14:55:48 UTC
This is a duplicate of issue 138663 which was fixed a couple of weeks ago.

*** This issue has been marked as a duplicate of 138663 ***