Is there any obvious reason why Seamonkey (2.5) should use 100% CPU while "Looking up smtp.gmail.com" ? I don't pretend to know very much about TCP, but I would have thought that a DNS lookup would have involved sending a few packets and then sitting there waiting for a response, presumably re-trying if no response is received within (say) 5 seconds. So what is it doing while "Looking up smtp.gmail.com" that requires 100% CPU ?
Philip Taylor _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
