Community
Participate
Working Groups
Build ID: M20070921-1145 Steps To Reproduce: 1.Create a build.xml file with the following target: <target name="check_connections"> <condition property="db_offline"> <not> <socket server="208.248.106.42" port="1800" /> </not> </condition> </target> 2.When viewed in the Ant Editor, Eclipse will try and establish a connection to the server. (Verified using netstat -o 2) Modifying the build.xml with the Ant Editor, particularly the socket parameters, will cause the connection event again. 3. If the server can not be reached, Eclipse will become unresponsive for several seconds (P4 - 3.2Ghz 1G RAM). This occurs periodically (every 10-20 seconds) while trying to modify the build.xml file. More information: The same problem seems to exist with the <html> condition.
The following task in a given (locally stored) build.xml causes Eclipse to hang periodically for 1-2 seconds whenever the build.xml is edited: <available file="/smbshare/projectfiles" property="smb.dir.available"/> Wireshark packet sniffer shows that it is making SMB queries out to the file system. Again, this is just while editing the local build.xml. The following example is much worse... it causes a 30-second freeze in Eclipse, where src.dir is a heavily populated Windows share on the network: <fileset id="duplicate.files" dir="${src.dir}" includes="**/*"> <present present="both" targetdir="${target.dir}"/> </fileset> <pathconvert property="duplicates.out" pathsep="${line.separator}" refid="duplicate.files"/> Wireshark shows that Eclipse is recursively querying the contents of every subdirectory on the hierarchy each time this build.xml is edited. In fact I cannot even get control of Eclipse unless I disable my network adapter.
I believe this is the same issue as https://bugs.eclipse.org/bugs/show_bug.cgi?id=256260 and I will put my comments there as well because this was actually on 3.4.0
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
