| View previous topic :: View next topic |
| Author |
Message |
adlepoo
Joined: 05 May 2009
Posts: 1
|
 Posted: Tue May 05, 2009 8:57 pm Post subject: netbeans 6.5.1 is unusable due to excessive project scanning |
 |
|
I have to move back to Netbeans 6.1.
The longer I have 6.5.1 open, the progressively longer the project scanning seems to take. Eventually it uses huge CPU and doesn't end, I can't even shut it down.
This problem does not occur in 6.1. (I had the same problem in 6.5, I was hoping 6.5.1 would fix it). |
|
| Back to top |
|
 |
tkellerer
Joined: 15 Aug 2008
Posts: 158
|
| Posted: Tue May 05, 2009 9:43 pm Post subject: |
|
|
Even more disappointing is the fact that it won't be addressed for 6.7 as well.
http://www.netbeans.org/issues/show_bug.cgi?id=134990
My experience is that the scanning in 6.7 is even worse than in 6.5. The initial delay is sometimes shorter after startup but then I get 5-10 seconds delays waiting when opening a single class 
And that is on a small project (~1000 classes) |
|
| Back to top |
|
|
Thomas Wolf
Posted via mailing list.
|
| Posted: Tue May 05, 2009 11:47 pm Post subject: netbeans 6.5.1 is unusable due to excessive project scanning |
|
|
I don't understand it either - it has 30 votes, most people have been
bitching about it for a year now, and it still doesn't get fixed Sun
must've already cut a lot of resources to make themselves look better
financially to the suitors (first IBM and now Oracle).
If you haven't voted for this issue yet, please do.
Has anyone tried the scan-on-demand module that the last poster to the
bug pointed to? Does it help?
Tom
On 05/05/2009 05:43 PM, tkellerer wrote:
| Quote: | Even more disappointing is the fact that it won't be addressed for 6.7 as well.
http://www.netbeans.org/issues/show_bug.cgi?id=134990
My experience is that the scanning in 6.7 is even worse than in 6.5. The initial delay is sometimes shorter after startup but then I get 5-10 seconds delays waiting when opening a single class :(
And that is on a small project (~1000 classes)
|
|
|
| Back to top |
|
|
Nigel Leck
Posted via mailing list.
|
| Posted: Wed May 06, 2009 1:06 am Post subject: netbeans 6.5.1 is unusable due to excessive project scanning |
|
|
It looks like Vita may have found the issue, waiting for daily build to check see
| Quote: | | http://www.netbeans.org/issues/show_bug.cgi?id=162706 |
tkellerer wrote: | Quote: | | Quote: | Even more disappointing is the fact that it won't be addressed for 6.7 as well.
http://www.netbeans.org/issues/show_bug.cgi?id=134990
My experience is that the scanning in 6.7 is even worse than in 6.5. The initial delay is sometimes shorter after startup but then I get 5-10 seconds delays waiting when opening a single class :(
And that is on a small project (~1000 classes)
|
|
--
Regards,
Nigel's STS email signature tag file
Nigel Leck
ST Software
t +61 2 9975 4648 f +61 2 9975 4652
Ground Floor / Suite 2 / Building C
No. 14 Rodborough Rd Frenchs Forest NSW 2086
PO Box 6275 Frenchs Forest NSW 2086
address-removed ([email]address-removed[/email]) www.stsoftware.com.au
If you receive this email by mistake, please notify us and do not use it. We do not waive any privilege, confidentiality or copyright associated with this email.
Liability limited by a scheme approved under Professional Standards Legislation. |
|
| Back to top |
|
|
mwildam
Joined: 16 Sep 2008
Posts: 19
|
| Posted: Wed May 06, 2009 9:31 am Post subject: |
|
|
What I found out is that most of the scanning seems to be the search for tasks.
If you switch to show only the todos for the currently open file then scanning time was reduced in my case (anyway still long time). My projects are not big, but I have at least 8 open at the same time (visible in the project tree).
_________________
Greetings, Martin Wildam. |
|
| Back to top |
|
|
tkellerer
Joined: 15 Aug 2008
Posts: 158
|
| Posted: Wed May 06, 2009 9:17 pm Post subject: |
|
|
| mwildam wrote: | What I found out is that most of the scanning seems to be the search for tasks.
If you switch to show only the todos for the currently open file then scanning time was reduced in my case (anyway still long time). My projects are not big, but I have at least 8 open at the same time (visible in the project tree). |
I have disabled the "Java Tasklist" completely, so the only scanning I have to wait for is the Java scanning for classes. |
|
| Back to top |
|
|
Melongo Annabel
Posted via mailing list.
|
| Posted: Thu May 07, 2009 12:52 am Post subject: netbeans 6.5.1 is unusable due to excessive project scanning |
|
|
You have encountered a known issue: http://www.netbeans.org/issues/show_bug.cgi?id=161367
Unfortunately, though this issue is being worked out, nobody knows when it will be corrected. Future updates on this issue will be made available. Thanks.
From: tkellerer <address-removed>
To: address-removed
Sent: Wednesday, May 6, 2009 4:17:31 PM
Subject: [nbusers] netbeans 6.5.1 is unusable due to excessive project scanning
mwildam wrote:
| Quote: | What I found out is that most of the scanning seems to be the search for tasks.
|
| Quote: | If you switch to show only the todos for the currently open file then scanning time was reduced in my case (anyway still long time). My projects are not big, but I have at least 8 open at the same time (visible in the project tree).
|
I have disabled the "Java Tasklist" completely, so the only scanning I have to wait for is the Java scanning for classes. |
|
| Back to top |
|
|
Gregg Wonderly
Posted via mailing list.
|
| Posted: Fri May 08, 2009 2:49 pm Post subject: netbeans 6.5.1 is unusable due to excessive project scanning |
|
|
tkellerer wrote:
Might I suggest that all of us having these problems run NB with a terminal
window open and anytime it's scanning and blocking work that you get a thread
dump, and post that thread dump to this issue as a commment. I think this will
start to make it more clear exactly where the problems are and specifically what
netbeans is reacting too.
Might I also suggest that the NB team plan for 6.7 to use Thread.setName() on
threads that are doing scanning with the name of the file/directory that was the
stimulus for the scan so that both users and developers can get a better idea
about what things are prompting these activities?
Gregg Wonderly |
|
| Back to top |
|
|
mwildam
Joined: 16 Sep 2008
Posts: 19
|
| Posted: Wed Jun 03, 2009 6:54 am Post subject: |
|
|
Issue 161367 seems to be fixed with 6.7 release, for issue 134990 it seems that you have to wait for 6.8.
_________________
Greetings, Martin Wildam. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
