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 126119 - Updating project 'Libraries' takes a VERY LONG time.
Summary: Updating project 'Libraries' takes a VERY LONG time.
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 6.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: David Konecny
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2008-01-28 16:20 UTC by markjl9
Modified: 2008-02-27 20:55 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description markjl9 2008-01-28 16:20:46 UTC
I've noticed that if you happen to have a bunch of jar files (20-30) added as part of the project: 'Project Properties
-> Libraries' and you remove these (or even half of them) and add others...you basically lose control over Netbeans for
a  VERY LONG time. You can manage to do other things but the CPU is pegged at 100% for about 3-4 minutes.
Comment 1 Tomas Zezula 2008-01-28 17:47:57 UTC
Can you add more information?
Which project are you using (j2se, web, j2me, j2ee)?
Can you attach several successive thread dumps?
Comment 2 markjl9 2008-01-28 17:54:41 UTC
My project is a 'web' project. I don't really have time to generate the thread dumps right now. I will try to do this later.
Comment 3 Tomas Zezula 2008-01-29 07:59:14 UTC
OK, thanks
Comment 4 markjl9 2008-01-29 13:40:51 UTC
In the meantime, this is something that is very easy to duplicate.
Comment 5 Tomas Mysik 2008-01-29 14:35:47 UTC
I will look at this, thanks.
Comment 6 Tomas Mysik 2008-02-13 17:46:32 UTC
Could you please verify it with the latest development build of NB?
I tried this:
- create new Web project
- Properties -> add 17 libraries and 28 jars -> OK
time: 12 seconds
- Properties -> remove 8 libraries, remove 8 jars, add 14 new jars -> OK
time: 31 seconds

I agree that these times are not perfect but I cannot reproduce your times. Could you attach several successive thread 
dumps please? Thanks.

Product Version: NetBeans IDE Dev (Build 080213)
Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03
System: Linux version 2.6.23-gentoo-r6 running on i386; UTF-8; cs_CZ (nb)
Comment 7 markjl9 2008-02-13 18:28:01 UTC
Did you try doing the same thing on a windows 2000 OS?
Comment 8 Tomas Mysik 2008-02-13 19:32:36 UTC
As you can see - not. Reassigning to David, please try to reproduce on Windows. Thanks.
Comment 9 markjl9 2008-02-15 19:08:54 UTC
As anyone had a chance to reproduce this issue (on windows OS) yet? This is a VERY serious issue. Sometimes after I
change jar files in my web project (as described above) I never regain control over my Netbeans again and I have to kill
it. When it comes back up...all is well. 
Comment 10 David Konecny 2008-02-26 03:15:10 UTC
Sorry it took me so long to get back to you!

It is the same problem which was fixed for J2SE Project as issue 47910. All web/j2ee project types are now using
optimized classpath provider from java.project (ProjectClassPathSupport.createPropertyBasedClassPathImplementation).

changeset:   69746:0242aa03c81c
user:        dkonecny@netbeans.org
date:        Tue Feb 26 15:55:04 2008 +1300
summary:     #126119 - use optimized classpath implementation from java.project
Comment 11 markjl9 2008-02-26 15:51:49 UTC
How do I get this update?
Comment 12 Tomas Mysik 2008-02-26 16:41:32 UTC
You can donwload daily build from http://bits.netbeans.org/dev/nightly/latest/ (the fix should be there tomorrow) or 
dev build directly from http://deadlock.netbeans.org/hudson/job/trunk/.

Thanks for reporting.
Comment 13 markjl9 2008-02-26 17:38:44 UTC
When you say "the fix should be there tomorrow" do you mean that it be part of the automatic updates in the Netbeans GUI
or do I actually have to download the daily build?
Comment 14 David Konecny 2008-02-26 20:31:21 UTC
You actually have to download the daily build or wait week or two for NB6.1 M2 release.
Comment 15 markjl9 2008-02-27 12:57:16 UTC
I currently have v6.0...are you saying that this update will not be available for it? Considering how serious this issue
is I would have expected it to be.
Comment 16 David Konecny 2008-02-27 20:55:21 UTC
I afraid it is too late to include this in NB601 Patch2, but we will see.