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.

Bug 163624 - IDE froze when I attempted to close it while sources were being scaned
Summary: IDE froze when I attempted to close it while sources were being scaned
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2009-04-24 17:10 UTC by Petr Dvorak
Modified: 2009-09-23 16:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
threaddump (17.46 KB, text/plain)
2009-04-24 17:11 UTC, Petr Dvorak 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Dvorak 2009-04-24 17:10:55 UTC 
NB 200904240201
JDK 1.6.0_11
WinXP

I have created a project from existing sources (kdelibs frm SVN). The files were being parsed and the project scanned
(these 2 actions were running in the progressbar in the statusbar). While these operations were still in progress, I
decided to close the IDE, but it froze, I had to kill it from the task manager.

Thread dump follows.
Comment 1 Petr Dvorak 2009-04-24 17:11:30 UTC 
Created attachment 80875 [details]
threaddump
Comment 2 Vladimir Voskresensky 2009-04-24 18:19:00 UTC 
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
Comment 3 Vitezslav Stejskal 2009-04-27 15:13:57 UTC 
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.
Comment 4 Vladimir Voskresensky 2009-04-27 15:59:49 UTC 
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)
Comment 5 Petr Dvorak 2009-04-28 00:38:50 UTC 
Yes, I can confirm that I didn't wait too long - it might very well be less than a minute...
Comment 6 Vitezslav Stejskal 2009-05-06 13:10:18 UTC 
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.
Comment 7 Vitezslav Stejskal 2009-09-23 16:37:32 UTC 
This seems to work fine in recent dev builds. Please reopen if this is still a problem.