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.
Summary: | NullPointerException at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.getFileObject | ||
---|---|---|---|
Product: | platform | Reporter: | tk_fhd_aui <tk_fhd_aui> |
Component: | Filesystems | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | exceptions_reporter, jglick, mutchd, tk_fhd_aui |
Priority: | P3 | ||
Version: | 7.2 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 185100 |
Bug Depends on: | |||
Bug Blocks: | 213562 | ||
Attachments: |
stacktrace
stacktrace |
Description
tk_fhd_aui
2012-03-12 13:17:53 UTC
Created attachment 116607 [details]
stacktrace
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=185100 Created attachment 116795 [details]
stacktrace
I've addded an assert with detailed info: ergonomics#57c1c0679540 *** Bug 208580 has been marked as a duplicate of this bug. *** Integrated into 'main-golden', will be available in build *201204040400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/57c1c0679540 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #209466: More detailed assert when factory is nul I can still recreate this issue in the latest dev build (20120411) Create/open a maven project and then expand the project files folder. Should happen first time it's opened. Will then happen every time the settings file is selected. Don't know if this is something peculiar with my settings file? (In reply to comment #7) > I can still recreate this issue in the latest dev build (20120411) Then you should open a new bug with the more detailed assertion message included. Normally you would just use the automated exception reporter, which would upload your log file for diagnosis. Trivially reproducible by running unit tests on a UNC drive as mentioned in bug #207060 comment #24. *** This bug has been marked as a duplicate of bug 207060 *** *** Bug 213628 has been marked as a duplicate of this bug. *** *** Bug 213673 has been marked as a duplicate of this bug. *** *** Bug 219621 has been marked as a duplicate of this bug. *** |