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.
Product Version = NetBeans IDE 3.6 RC1 (Build 200403161736) Operating System = Linux version 2.4.20-18.9 running on i386 Java; VM; Vendor = 1.4.2_03; Java HotSpot(TM) Client VM 1.4.2_03-b02; Sun Microsystems Inc. Java Home = /usr/local/java/j2sdk1.4.2_03/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /usr/local/home/delphym; /usr/local/home/delphym/NetBeans3.6/bin IDE Install; User Dir = /usr/local/home/delphym/NetBeans3.6; /usr/local/home/delphym/.netbeans/3.6rc1 ================================================== Description: ============= I don't have reproduction procedure. IMHO it could be result of few actions, mainly of interupting commands and disconnectiong of network. IDE then was almost dead, but still response, but finaly I had to kill it. before I've got to this state I almost unmount almost all VCS FSs and left only mounted: CVS-EXT: nbextra CVS-EXT: all sources of netbeans "nb_all" CVS-INT: Beetle In nb_all FS I've found I have some [local] folders which shouldn't be [local] but up-to-date (in fact they have not status at all) So, I've executed Refresh (not sure it it was Recursively). But it run's quite long and I had to leave (with my laptop in which I run the ide). So, from Runtime TAB I kill one of 2 running Refresh commands imediately butg second Refresh was not easy to kill it cause it didn't react imediately. I double click the Running refresh command and VCS Output Windows opened with still running Refresh. I several press STOP button but nothing happened. But I had to leave so, I stop my network interfaces and disconnected net.cable, suspend my laptop. When I came home and woke up it the IDE occupied almost 100% of my CPU. It was slowly responding, so I did a FTD. I find that Refresh was finished, but IDE was still almost unusable. Within c. 20 minutes I created 2 more FTD.
Created attachment 14048 [details] 3 FTD during 30 minutes
Created attachment 14050 [details] ide.log from my last run of ide
In fact there's no deadlock, but because of performance problem within cvs cache it get almost unusable and unresponding so thus it looked like there was deadlock. Am I right, Martin?
Yes, correct. Scheduling for promo-D. Depends on cache redesign.
Should be fixed after the cache redesign.