See Thread at: http://www.techienuggets.com/Detail?tx=70547
Posted on behalf of a User
I had exactly the same problem here and managed to reduce it (using strace) to timeouts
communicating with another host on our network - which turned out to be configured as the
eclipse host's print server in /etc/cups/client.conf.
After upgrading the printing configuration "as it should be" - using localhost
in /etc/cups/client.conf and setting up browsing in the local cups configuration to
automagically attach the printers exported by the network cups server - opening new
editors in eclipse became instantaneous.
strace -f -tt -o /tmp/eclipse eclipse
- reproduce the delay
cat /tmp/eclipse | grep AF_INET
This will show all network communication performed by eclipse. You'll be looking for
'connect' calls returning EINPROGRESS / EALREADY followed by a delay (cf. time
stamps in the second column).
In Response To:
Before I file this in bugzilla, I wanted to check if it's just my
problem ... Lately, in Eclipse (3.4.1 on Fedora 10), I've been
noticing that it takes several seconds to open a new editor. So if I
click on a Java source file (in Java perspective), the new tab appears
immediately, but it takes several seconds for the actual editor to
finish rendering. In the meantime, the tab just says "Java editor".
Similar things happen with the Ant buildfile editor.
I have several third-party plugins installed that I don't want to
remove unless I have to, which is why I wanted to check first -- is
anyone else seeing similar symptoms?
Mary Ellen Foster -- http://homepages.inf.ed.ac.uk/mef/
Informatik 6: Robotics and Embedded Systems, Technische UniversitÃ¤t MÃ¼nchen
and ICCS, School of Informatics, University of Edinburgh
fedora-devel-java-list mailing list