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: | IDE froze when I attempted to close it while sources were being scaned | ||
---|---|---|---|
Product: | editor | Reporter: | Petr Dvorak <joshis> |
Component: | Parsing & Indexing | Assignee: | Vitezslav Stejskal <vstejskal> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | Keywords: | THREAD |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | threaddump |
Description
Petr Dvorak
2009-04-24 17:10:55 UTC
Created attachment 80875 [details]
threaddump
I've seen the same with in my daily Java env development. There are two long running Parsing API tasks where one of them is done in EDT (another is "Java Source Worker Thread") For me it appeared when I opened all CND projects and during "Scan in progress" phase closed IDE Are you sure that the IDE was really frozen? The threaddump shows no deadlock, the IDE was still indexing and may have eventually finished and closed. Vita, you are right. In my case (with Java project) I've taken dump and haven't seen any dead locks, so left IDE in "frozen" state to see what happened. I really closed after one minute or so. I think the user joshis wasn't so patient to wait so long of finish indexing => that's why his expression as this IZ. But I agree with him, that frozen UI is not very good (EDT was blocked in call org.netbeans.modules.parsing.impl.Installer.closing) Yes, I can confirm that I didn't wait too long - it might very well be less than a minute... The issue #163944 has been fixed (deadlock). I'll leave this one open to investigate further if closing the IDE properly cancels any outstanding indexing jobs. This seems to work fine in recent dev builds. Please reopen if this is still a problem. |