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: | Duplicate file object, duplicate FileName | ||
---|---|---|---|
Product: | platform | Reporter: | budgie67 <budgie67> |
Component: | Filesystems | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cbohme, maghiel, rmatous |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 166458 |
Attachments: | stacktrace |
Description
budgie67
2010-03-15 19:08:00 UTC
Created attachment 95212 [details]
stacktrace
Log file at #353266 exception report shows that there is duplicated item for image-58.jpg: [_big\image-58.jpg@1d7a25b:af47f8,valid=true] [_big\image-58.jpg@1e4230e:1cb05b9,valid=true] both hashcodes are different. This means that the file object itself is different: String mineHex = Integer.toHexString(System.identityHashCode(this)); as well as internal filename is different: String fnHex = Integer.toHexString(System.identityHashCode(getFileName())); I don't think there shall be two different name objects for the same file. So it seems to indicate the bug is in FileName cache(!?). CCing Radek Matouš. *** Bug 180388 has been marked as a duplicate of this bug. *** Integrated into 'main-golden', will be available in build *201003190200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/691904c7af0a User: Jaroslav Tulach <jtulach@netbeans.org> Log: #182069: Ensuring access to nameMap is always under proper lock. Probably not full fix, but a step forward. Looks fixed. No new report since the last improvement in synchronization. *** Bug 179655 has been marked as a duplicate of this bug. *** |