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: | Sniffing resolver works in AWT thread; this freezes UI in the case file system is slow | ||
---|---|---|---|
Product: | platform | Reporter: | Vladimir Kvashin <vkvashin> |
Component: | Data Systems | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | jglick |
Priority: | P3 | Keywords: | PERFORMANCE, THREAD |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 184196 | ||
Attachments: | AWT thread dump |
Description
Vladimir Kvashin
2010-02-27 05:09:38 UTC
Created attachment 94582 [details]
AWT thread dump
This one will be harder to solve. Leaving for later version. My current idea is to display dummy node and later replace it with real one (with icon, properties, actions). I am not sure how reliable that is going to be. I am working on a less-blocking-189979-and-181300 branch at http://hg.netbeans.org/core-main/shortlog/eb9a806f0c37 There is a builder at http://deadlock.netbeans.org/hudson/job/prototypes-less-blocking-189979-and-181300/ I tried to delay call to Dataobject.find and do it later from non-AWT thread. The code seems to get far more fragile and I am afraid to do that. So rather then fixing, let's try some defence: How often this happens? How much files your directories contain? What is their mime type? What are their extensions? Can you genereate self-profiling snapshot? Btw. when you browse the same directory in Files tab, is it as slow as in Favorites one? If not, then I know what to solve... No cooperation, no fix. Correcting resolution. |