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: | 6s - project.ui.actions.OpenProjectFolderAction.createContextAwareInstance() | ||
---|---|---|---|
Product: | projects | Reporter: | dds.dhawal |
Component: | Generic Infrastructure | Assignee: | Tomas Stupka <tstupka> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | b-k-m, davideconsonni, dds.dhawal, jtulach, pjiricka, roger_rf, sreder, vv159170, williambacchi |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 177836 |
Attachments: |
nps snapshot
nps snapshot nps snapshot |
Description
dds.dhawal
2011-03-23 12:09:10 UTC
Created attachment 107212 [details]
nps snapshot
Created attachment 108995 [details]
nps snapshot
Created attachment 110389 [details]
nps snapshot
in most recent cases (7.2 beta and 7.1.x), often the problem is that ProjectManager.isProject() is called in AWT (under READ mutex) while another thread is using WRITE project mutex for a long time. No real solution in sight as some of the usages just have to happen in AWT. Eg. in DirectoryChooserUI.handleDblClick() via DirectoryNode.isNetBeansProject(). Only half-hacky solution I can imagine is to somehow tag the Icon returned by ProjectChooserAccessory.ProjectFileView and associate it with the DirectoryNode and only when the proper project action is there, enable the double click. last report 2012-09-27, oldest build 7.2 beta closing |