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.
My general approach up to now has been: * Login to Linux box * Check out project from CVS into directory shared by Samba * From WinXP box, open projects in NB. I've always done it this way because the Java is part of a larger project that requires compilers only available on the Linux host. As of the "2" update, this has become unusable. Every few keystrokes NB hangs for 10-50 seconds. I took a look at the network with Wireshark and for the file currently open for editing I'm seeing the following stream of packets: 13:06:02.864174 SMB QUERY_PATH_INFO, Query File Basic Info, Path: \longpath\file.java 13:06:02.865062 SMB QUERY_PATH_INFO, Query File Network Open Info, Path: \longpath\file.java 13:06:02.865933 SMB QUERY_PATH_INFO, Query File Basic Info, Path: \longpath\file.java 13:06:02.869242 SMB QUERY_PATH_INFO, Query File Network Open Info, Path: \longpath\file.java 13:06:02.870169 SMB QUERY_PATH_INFO, Query File Basic Info, Path: \longpath\file.java 13:06:02.871019 SMB QUERY_PATH_INFO, Query File Network Open Info, Path: \longpath\file.java 13:06:02.871738 SMB QUERY_PATH_INFO, Query File Basic Info, Path: \longpath\file.java 13:06:02.874278 SMB QUERY_PATH_INFO, Query File Network Open Info, Path: \longpath\file.java 13:06:02.875622 SMB QUERY_PATH_INFO, Query File Basic Info, Path: \longpath\file.java 13:06:02.876304 SMB QUERY_PATH_INFO, Query File Network Open Info, Path: \longpath\file.java Note #1:The first column is seconds and microseconds from the start of the capture Note #2: This is only the outbound traffic, not the return traffic Note #3: I replaced the actual path & file names to save space, but all packets are regarding the same file. This trace was with exactly 1 file open and that produced 10 network hits over a period of 12 milliseconds! The more files I have open for editing, the more network activity. What's even worse, is the activity doesn't stop when I close the file. Not even closing the project stops it. I have to shut down NB to make it stop. I understand checking to see if the file was changed outside of NB, but there's no reason to do so that frequently! I'm currently managing by working on a local filesystem but having to copy files back and forth is no fun.
Created attachment 59635 [details] My var/log/messages.log showing the startup options & modules
We are generally slower on network, additional disk touches made by cvs don't make it better... However, we did several improvements in this area for NB 6.1 and 6.5. Could you possibly try some later 6.5 build (or wait for Beta which should come in about 2 weeks) and check how it behaves? Then we would know if there's a real improvement in your scenario and possibly do some more analysis. Thanks. > I'm currently managing by working on a local filesystem but having to copy files back and forth is no fun. Just wondering - if your sources are in cvs why don't you check out a copy to your local filesystem and synchronize via cvs?
I'll be glad to investigate more, but I need you to confirm that the problem still persist even in latest 6.5beta version. If that is the case, please add more logs and reopen this bug. Thanks.