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 105809 - Random NoSuchElementException while typing
Summary: Random NoSuchElementException while typing
Status: RESOLVED DUPLICATE of bug 94397
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2007-06-06 05:13 UTC by _ tboudreau
Modified: 2007-11-05 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2007-06-06 05:14:00 UTC
Saw this while I was on an airplane several times while typing (I don't think
the airplane has anything to do with it, but I couldn't tell you now what
exactly I was doing).  It seemed to happen when a java reparse was happening, so
I'd guess the data the error stripe was displaying was out of date.  

Given that it happens inside a TreeMap, the likely cause is one thread modifying
the map while the event thread is iterating it.

java.util.NoSuchElementException
	at java.util.TreeMap.key(TreeMap.java:1204)
	at java.util.TreeMap$NavigableSubMap.firstKey(TreeMap.java:1429)
	at
org.netbeans.modules.editor.errorstripe.AnnotationViewDataImpl.findNextUsedLine(AnnotationViewDataImpl.java:332)
	at
org.netbeans.modules.editor.errorstripe.AnnotationViewDataImpl.getMainMarkForBlockImpl(AnnotationViewDataImpl.java:244)
	at
org.netbeans.modules.editor.errorstripe.AnnotationViewDataImpl.getMainMarkForBlock(AnnotationViewDataImpl.java:225)
	at
org.netbeans.modules.editor.errorstripe.AnnotationView.paintComponent(AnnotationView.java:283)
	at javax.swing.JComponent.paint(JComponent.java:1022)
	at javax.swing.JComponent.paintToOffscreen(JComponent.java:5104)
	at
javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:285)
	at javax.swing.RepaintManager.paint(RepaintManager.java:1132)
	at javax.swing.JComponent._paintImmediately(JComponent.java:5052)
	at javax.swing.JComponent.paintImmediately(JComponent.java:4862)
	at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:727)
	at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:683)
	at javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java:663)
[catch] at
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:128)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
	at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Comment 1 Vitezslav Stejskal 2007-10-12 15:17:48 UTC
Looks like slightly different reincarnation of the same synchronization problem.

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