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 208497 - NullPointerException at org.openide.nodes.EntrySupport$Lazy.removeEntries
Summary: NullPointerException at org.openide.nodes.EntrySupport$Lazy.removeEntries
Status: RESOLVED DUPLICATE of bug 208587
Alias: None
Product: platform
Classification: Unclassified
Component: Nodes (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-16 11:28 UTC by Alexander Simon
Modified: 2012-03-05 09:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 185134

Attachments
stacktrace (3.22 KB, text/plain)
2012-02-16 11:28 UTC, Alexander Simon 		Details
stacktrace (7.83 KB, text/plain)
2012-02-17 10:45 UTC, Vladimir Voskresensky 		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 Alexander Simon 2012-02-16 11:28:25 UTC 
Build: NetBeans IDE Dev (Build 20120216-e2994eb17390)
VM: Java HotSpot(TM) Client VM, 20.5-b03, Java(TM) SE Runtime Environment, 1.6.0_30-b12
OS: SunOS

Stacktrace: 
java.lang.NullPointerException
   at org.openide.nodes.EntrySupport$Lazy.removeEntries(EntrySupport.java:1800)
   at org.openide.nodes.EntrySupport$Lazy.setEntries(EntrySupport.java:1411)
   at org.openide.nodes.EntrySupport.setEntries(EntrySupport.java:102)
   at org.openide.nodes.Children$Keys$2.run(Children.java:1555)
   at org.openide.util.Mutex$1Exec.run(Mutex.java:1244)
   at org.openide.nodes.Children$ProjectManagerDeadlockDetector.execute(Children.java:1920)
Comment 1 Alexander Simon 2012-02-16 11:28:27 UTC 
Created attachment 115805 [details]
stacktrace
Comment 2 Vladimir Voskresensky 2012-02-17 10:45:57 UTC 
Created attachment 115860 [details]
stacktrace

create new file in full remote folder
Comment 3 Jaroslav Tulach 2012-03-05 09:50:55 UTC 

*** This bug has been marked as a duplicate of bug 208587 ***