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 130354 - NullPointerException at org.netbeans.spi.project.ui.support.NodeFactorySupport$DelegateChildren.addNotify
Summary: NullPointerException at org.netbeans.spi.project.ui.support.NodeFactorySuppor...
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milos Kleint
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on: 193065
Blocks:
  Show dependency tree
 
Reported: 2008-03-18 02:00 UTC by _ pcw
Modified: 2012-04-13 21:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 27861

Attachments
stacktrace (4.44 KB, text/plain)
2008-03-18 02:00 UTC, _ pcw 		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 _ pcw 2008-03-18 02:00:25 UTC 
Build: NetBeans IDE Dev (Build 080313)
VM: Java HotSpot(TM) Client VM, 10.0-b19
OS: SunOS, 5.10, x86

User Comments: 
Opened a project node that was closed.
Comment 1 _ pcw 2008-03-18 02:00:34 UTC 
Created attachment 58534 [details]
stacktrace
Comment 2 Milan Kubec 2008-03-18 09:25:31 UTC 
I don't know how the result could be null (lazy project loading?). Milosi, you know more about this code than I do.
Comment 3 Milos Kleint 2008-03-18 09:54:51 UTC 
the only way to get the NPE in this place is the situation when removeNotify() is called within the time the addNotify()
call is processing.
Comment 4 Milos Kleint 2008-03-18 11:34:18 UTC 
fixed the immediate problem by synchronization. On a more general level, it's questionable if removeNotify() shall be
allowed to execute while addNotify() is running.
http://hg.netbeans.org/main/rev/1f70f13bd8f8