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.
Build: NetBeans IDE Dev (Build cnd-main-1751-on-090923) VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08 OS: Linux, 2.6.28-15-generic, i386 User Comments: GUEST: expanded the project navigation window and it took time to open. areeda: On loading with a php project Maximum slowness yet reported was 6219 ms, average is 4767
Created attachment 88265 [details] nps snapshot
This issue already has 6 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
Build: NetBeans IDE Dev (Build cnd-main-1751-on-090923) VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08 OS: Linux, 2.6.28-15-generic, i386 User Comments: Maximum slowness yet reported was 10919 ms, average is 5646
Created attachment 88266 [details] nps snapshot
This issue already has 7 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
This issue already has 8 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
VersioningAnnotationProvider.annotateNameHtml() takes too much time. Probably it should return immediately and fire change later.
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
This issue already has 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
This issue already has 12 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
This issue already has 13 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157698
*** Issue 173547 has been marked as a duplicate of this issue. ***
There are now 21 duplicates in the exception reports (don't know why this is not reflected in the issue here). Why is the target milestone TBD (shouldn't this be 6.8) ? How many duplicates are needed before the priority will be increased automatically ?
giorgio42: > There are now 21 duplicates in the exception reports Yes, but i detected at least 4 of them reported by you - a single user - so the exception reporter should count them as one and should not increase the priority > How many duplicates are needed before the priority will be increased automatically 25, i think, but unless i am mistaken, they all should be reported by different users - which in case of this issue they clearly are not. > Why is the target milestone TBD (shouldn't this be 6.8) i'm changing TM to next, this will not be fixed in 6.8, since it would require major changes, probably a change in the API of versioning systems and there are still some unresolved problems regarding the fix, which need to be discussed across several netbeans modules - versioning, core, nodes, editor, etc. There's simply not enough time till 6.8 release. You must understand that integrating the fix may cause 6.8 unstable and may cause more problems than it would resolve. If you use daily builds (from the reports i suspect that you do), you will get the fix soon after 6.8 is branched. You would probably get faster response from IDE if you disable versioning labels - View > Show Versioning Labels. BTW, we already have an issue with a higher priority filed for this - see issue 171410
Why should n exceptions that occurred to one user count only as 1 exception ? If there is a bug in NB causing an endless loop of exceptions rendering NB unuseable NB engineering would not even notice. I totally depend on versioning labels (one of the reasons to do versioning is to be easily able to find out what version a file has and to have this information available in a human readable format - which is the sucking aspect about systems like SVN, Mercurial and GIT). But I accept that there is not enough bandwidth to fix this issue in a diligent way for the NB 6.8 release.
*** Issue 174591 has been marked as a duplicate of this issue. ***
*** This bug has been marked as a duplicate of bug 171410 ***