User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:220.127.116.11) Gecko/20101203 Firefox/3.6.13; Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:18.104.22.168) Gecko/20101123 SeaMonkey/2.0.11 For the past few months now, both Firefox 3.6.13 and SeaMonkey 2.0.11 under Windows Vista and 64-bit Linux (Ubuntu) will occasionally "freeze" while web browsing, the "freeze" will last anywhere from 10 seconds to 1 minute, sometimes even longer. What occurs when this "freeze" happens, is that I will select a Bookmark, the browser will display "Looking for www.whatever.com..." then sit there doing nothing. If I then open new tabs and manually type in a URL or (via IP address) access either or both of the cable modem and router status screens, nothing happens in those tabs either, until the browser magically "wakes up" and everything on those tabs starts loading in. I have replaced the cables, router and NIC, with this problem remaining. The system is a Compaq CQ5110F desktop with an AMD Athlon X2 64 dual-core 64-bit CPU with 3Gb of RAM. Windows Vista 32-bit was pre-installed on it when it was purchased and I subsequently installed the 64-bit version of Ubuntu Linux, currently at version 10.10. I have ruled out data connection issues, where the cables, router and NIC were replace - with the same results, plus the fact that during the time that the browsers "freeze", in a console window - telnet, ftp, traceroute and ping all work and respond/connect accordingly, so there is no data connection loss. I have a 32-bit laptop also with Ubuntu Linux 10.10 installed and an older desktop containing an AMD K6-2 CPU with Windows XP Home and Ubuntu 10.04 installed and on these other two systems, this issue is not occuring. This only occurs on the 64-bit hardware. I have also tried non-Mozilla browsers on the 64-bit hardware: Internet Explorer 8 under Windows; and Chromium on the Linux side, neither of these browsers exhibit the same behavior, even after a good hour of solid use. Did something change with these Firefox and SeaMonkey versions that would cause the browsers to act this way on this particular hardware? Reproducible: Always
On the Linux side, the Firefox being used is the one supplied by Ubuntu and the version of SeaMonkey used is the x86_64 contributed build.
Thunderbird 3.1.7 in Windows (have not used it in Linux) also froze yesterday on the same hardware, while loading in an HTML e-mail. Could this possibly be plugin-related?
Do you still see the same behavior ?
No. No longer use Ubuntu as well.