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 242965 - IllegalArgumentException: bad position: 162
Summary: IllegalArgumentException: bad position: 162
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-17 13:31 UTC by petrk
Modified: 2015-07-20 14:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 208444

Attachments
stacktrace (3.00 KB, text/plain)
2014-03-17 13:31 UTC, petrk 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description petrk 2014-03-17 13:31:44 UTC 
Build: NetBeans IDE Dev (Build 20140312-845024ec5fd4)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13
OS: Linux

User Comments:
petrk: Navigated back from extract_optional_type.hpp to mutable_iterator.hpp in boost 1.55




Stacktrace: 
java.lang.IllegalArgumentException: bad position: 162
   at javax.swing.text.JTextComponent.setCaretPosition(JTextComponent.java:1678)
   at org.netbeans.modules.editor.impl.actions.NavigationHistoryBackAction.show(NavigationHistoryBackAction.java:301)
   at org.netbeans.modules.editor.impl.actions.NavigationHistoryBackAction.actionPerformed(NavigationHistoryBackAction.java:196)
   at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1662)
   at javax.swing.JComponent.processKeyBinding(JComponent.java:2878)
   at javax.swing.JComponent.processKeyBindings(JComponent.java:2925)
Comment 1 petrk 2014-03-17 13:31:46 UTC 
Created attachment 146071 [details]
stacktrace
Comment 2 Milutin Kristofic 2015-07-20 14:14:21 UTC 
I am sorry I didn't try to solve it back to day when you reported this. You have a lot of errors in messages.log I think there was a corrupt files, or something else. If you can reproduce this, pls reopen we can search for culprit. Otherwise I am closing this since you are only reporter without enough leads to solve this.