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 171789 - [closing IDE] closing increadibly slow while scanning the projects
Summary: [closing IDE] closing increadibly slow while scanning the projects
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-09-09 09:46 UTC by matusdekanek
Modified: 2009-09-26 21:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (452.19 KB, text/plain)
2009-09-09 09:47 UTC, matusdekanek 		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 matusdekanek 2009-09-09 09:46:56 UTC 
Product Version: NetBeans IDE Dev (Build 200909081533)
Java: 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02
System: Linux version 2.6.28-15-generic running on i386; UTF-8; en_US (nb)

-open IDE
-open some bigger project (so that the scanning will last lets say more than a minute)
-while scanning the project, close the IDE
The processor usage is 100% and the IDE does not close for a few minutes(3 minutes). Sometimes even the dialog about
closing the ide (and canceling tasks such as scanning) does not appear.

I will add messages.log as the attachment (logged with
-J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=INFO and -J-Dorg.netbeans.log.startup=print
switches), but I don`t know how to generate some profiler snapshot, as I want to measure the IDE closing.

My machine has P4 2.8 GHz processor and 1.0 RAM. Without the IDE running, the processor usage is about 20% or less.
Comment 1 matusdekanek 2009-09-09 09:47:38 UTC 
Created attachment 87336 [details]
messages.log
Comment 2 Vitezslav Stejskal 2009-09-09 11:09:09 UTC 
What project is it? The log file shows that 222521 ms was spent by resolving project dependencies. I'll fix
RepositoryUpdater and make this part of the job cancellable as well.
Comment 3 matusdekanek 2009-09-09 11:15:52 UTC 
hudson project (maven).
Comment 4 matusdekanek 2009-09-09 12:14:05 UTC 
I guess this may as well have something to do with closing a (big) project (without being scanned). Or should I post a
new bug?
Comment 5 Vitezslav Stejskal 2009-09-09 15:30:38 UTC 
"hudson project (maven)" - Maven's implementation of some vital queries is not very fast and so resolving dependencies
can be affected as well. I'll make this part of initial scan cancellable.

"I guess this may as well have something to do with closing a (big) project (without being scanned). Or should I post a
new bug?" - Not sure what you are talking about.
Comment 6 matusdekanek 2009-09-09 15:35:31 UTC 
only that if you try to close a maven project that is being scanned yet, the IDE will freeze and it will not close the
project until it is fully scanned.
Comment 7 Vitezslav Stejskal 2009-09-24 12:47:44 UTC 
http://hg.netbeans.org/jet-main/rev/2728c916dd81
Comment 8 Quality Engineering 2009-09-26 21:10:02 UTC 
Integrated into 'main-golden', will be available in build *200909251401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/2728c916dd81
User: Vita Stejskal <vstejskal@netbeans.org>
Log: #171789: making findDependencies cancellable when IDE shuts down