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 171229 - java.util.NoSuchElementException at java.util.AbstractList$Itr.next
Summary: java.util.NoSuchElementException at java.util.AbstractList$Itr.next
Status: VERIFIED WONTFIX
Alias: None
Product: javafx
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Michal Skvor
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-01 10:25 UTC by Lukas Hasik
Modified: 2009-10-13 14:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 157576

Attachments
stacktrace (3.33 KB, text/plain)
2009-09-01 10:25 UTC, Lukas Hasik 		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 Lukas Hasik 2009-09-01 10:25:36 UTC 
Build: NetBeans IDE 6.7.1 (Build 200907230233)
VM: Java HotSpot(TM) Client VM, 14.1-b02, Java(TM) SE Runtime Environment, 1.6.0_15-b03
OS: Windows Vista, 6.0, x86

User Comments:
lhasik: -NB6.7.1 all + javafx patch (SDK1.2.1+debugger)
-debugging an FX application with F8 and some watches (non-existing names)



Stacktrace: 
java.util.NoSuchElementException
        at java.util.AbstractList$Itr.next(AbstractList.java:350)
        at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010)
        at org.netbeans.api.javafx.source.JavaFXSource.getFileObject(JavaFXSource.java:357)
        at org.netbeans.api.javafx.source.JavaFXSource.moveToPhase(JavaFXSource.java:240)
        at org.netbeans.api.javafx.source.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:131)
        at org.netbeans.api.javafx.source.CompilationController.toPhase(CompilationController.java:72)
Comment 1 Lukas Hasik 2009-09-01 10:25:41 UTC 
Created attachment 86896 [details]
stacktrace
Comment 2 Michal Skvor 2009-10-13 14:27:26 UTC 
The new debugger will be rewritten.
Comment 3 Lukas Hasik 2009-10-13 14:54:49 UTC 
please, TM is important as it defines in what scope the issue wont be fixed