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.
Summary: | task scanning locks up IDE completely for many minutes | ||
---|---|---|---|
Product: | java | Reporter: | nleck <nleck> |
Component: | Source | Assignee: | Jan Lahoda <jlahoda> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
a number of ctrl+\ while the IDE was scanning (locked up)
Screen shot while IDE is locked up |
Description
nleck
2008-10-23 10:19:48 UTC
Thanks you for the report but we need more info. Could you please enclose thread dump when IDE gets frozen ? http://wiki.netbeans.org/GenerateThreadDump We have a source tree of some 6,000 Java files. Our home directory is mounted via NFS on a couple of large Solaris boxes. The task scan took about 10 minutes ( actually killed the ide a number of times thinking it was deadlocked), it took 10 minutes once I stopped killing it. The IDE was unusable during this time. I've now disabled the task list feature but had to wait for the first scan to complete to do this. I guess I'm really just saying it gives a very bad first impression. PS. This project is shared between Netbeans and Eclispe. There are more users on Eclispe so we can't change the project around just for netbeans. The thread dump would really help. Created attachment 73109 [details]
a number of ctrl+\ while the IDE was scanning (locked up)
The IDE really isn't usable while the scanning in running. Reassigning to java for evaluation. Created attachment 75687 [details]
Screen shot while IDE is locked up
Need to disable "Task List" to prevent the lock up. The "Task List" module seems to lock up the IDE on both Solaris and Windose. Overtake. Evaluated. 6.1 seems better behaved this way Reassigning all moonko's java/source bugs to myself. This is fixed I believe in the 6.8beta... should we just close ? Closing the issue. |