457439 - FF stops loading *any* pages after a short while, ONLY after upgrade from 2.0.0.16 to 2.0.0.17

Status: RESOLVED DUPLICATE of bug 456705

(Firefox :: General, defect)

Description

[a_geek]

User-Agent:       Mozilla/5.0 (X11; Linux i686; U; en; rv:1.8.1) Gecko/20061208 Firefox/2.0.0 Opera 9.52
Build Identifier: Mozilla/5.0 (X11; Linux i686; U; en; rv:1.8.1) Gecko/20061208 Firefox/2.0.0 Opera 9.52

I've determined that, after installing the upgrade, FF stops handling the network after a few page requests. "A few" can mean as little as one or two pages. Using tcpdump, this event looks like this (this is a complete FF session, from start to hang):
# tcpdump -ni ppp0 port 80 or port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
15:46:33.094968 IP 87.186.107.30.57823 > 193.99.144.85.80: S 2265277712:2265277712(0) win 5808 <mss 1452,sackOK,timestamp 1070309 0,nop,wscale 6>
15:46:33.139297 IP 193.99.144.85.80 > 87.186.107.30.57823: S 2890723062:2890723062(0) ack 2265277713 win 4356 <mss 1452,nop,wscale 0,nop,nop,timestamp 2693559215 1070309,sackOK,eol>
15:46:33.139367 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 1 win 91 <nop,nop,timestamp 1070320 2693559215>
15:46:33.139930 IP 87.186.107.30.57823 > 193.99.144.85.80: P 1:1058(1057) ack 1 win 91 <nop,nop,timestamp 1070320 2693559215>
15:46:33.290242 IP 193.99.144.85.80 > 87.186.107.30.57823: . 1:1441(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559362 1070320>
15:46:33.290310 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 1441 win 136 <nop,nop,timestamp 1070358 2693559362>
15:46:33.290898 IP 193.99.144.85.80 > 87.186.107.30.57823: P 1441:1449(8) ack 1058 win 5413 <nop,nop,timestamp 2693559362 1070320>
15:46:33.290921 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 1449 win 136 <nop,nop,timestamp 1070358 2693559362>
15:46:33.294269 IP 193.99.144.85.80 > 87.186.107.30.57823: . 1449:2889(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559362 1070320>
15:46:33.294322 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 2889 win 181 <nop,nop,timestamp 1070359 2693559362>
15:46:33.294517 IP 193.99.144.85.80 > 87.186.107.30.57823: . 2889:4329(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559362 1070320>
15:46:33.294532 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 4329 win 226 <nop,nop,timestamp 1070359 2693559362>
15:46:33.298589 IP 193.99.144.85.80 > 87.186.107.30.57823: . 4329:5769(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559362 1070320>
15:46:33.298640 IP 87.186.107.30.57823 > 193.99.144.85.80: . ack 5769 win 271 <nop,nop,timestamp 1070360 2693559362>
15:46:33.298811 IP 87.186.107.30.57823 > 193.99.144.85.80: R 1058:1058(0) ack 5769 win 271 <nop,nop,timestamp 1070360 2693559362>
15:46:33.339274 IP 193.99.144.85.80 > 87.186.107.30.57823: . 5769:7209(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559411 1070358>
15:46:33.339330 IP 87.186.107.30.57823 > 193.99.144.85.80: R 2265278770:2265278770(0) win 0
15:46:33.341957 IP 193.99.144.85.80 > 87.186.107.30.57823: . 7209:8649(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559414 1070359>
15:46:33.341971 IP 87.186.107.30.57823 > 193.99.144.85.80: R 2265278770:2265278770(0) win 0
15:46:33.344332 IP 193.99.144.85.80 > 87.186.107.30.57823: . 8649:10089(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559416 1070359>
15:46:33.344345 IP 87.186.107.30.57823 > 193.99.144.85.80: R 2265278770:2265278770(0) win 0
15:46:33.347108 IP 193.99.144.85.80 > 87.186.107.30.57823: . 10089:11529(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559419 1070360>
15:46:33.347121 IP 87.186.107.30.57823 > 193.99.144.85.80: R 2265278770:2265278770(0) win 0
15:46:33.349350 IP 193.99.144.85.80 > 87.186.107.30.57823: . 11529:12969(1440) ack 1058 win 5413 <nop,nop,timestamp 2693559419 1070360>
15:46:33.349362 IP 87.186.107.30.57823 > 193.99.144.85.80: R 2265278770:2265278770(0) win 0



Reproducible: Always

Steps to Reproduce:
1. Start Firefox
2. Surf to a website
3. make a few clicks there -> hang
Actual Results:  
Firefox hangs and will not surf any other web page as well while eating (on my computer) some 10% CPU time over hours.

Expected Results:  
Firefox keeps working normally, and terminates without a problem when asked to terminate.

If one clicks the "close" button in the window manager, Firefox keeps running in the background and must be killed from the shell. The problem occurred after upgrading from 2.0.0.16 to 2.0.0.17. An upgrade to 3.x is not possible at the moment because the system requirements of 3.x are incompatible with Debian Etch (which is what I'm using).

Comment 1

[Tyler Downer [He/Him]]

Please try starting in Safe Mode, and with a new profile. Also, check firewalls, internet connections, etc.

Comment 2

[a_geek]

Ok... trying with a new, empty profile in safe mode (I assume -safe-mode) worked, but this is unsatisfactory. It looks like going SSL immediately provokes the problem, and, fwiw, initially, some of the libs were inaccessible to FF (I fixed that by adding FF's installation path to the system's config and ran 'ldconfig' again.

I now checked which other libs might be missing, but didn't find any (or at least, not in the top level directory. I'm currently using Opera on the same system for the same purposes, which doesn't have any of these problems (at least), but would (obviously) like to switch back to FF ASAP.

Please find a sane way to upgrade w/o losing "everything", and/or some better debug&repair mechanisms for Joe Average User. Thanks!

Comment 3

[a_geek]

ok, debugged more: it seems to be this problem: bug #456705

Comment 4

[a_geek]

The fix on bug #456705 makes this a duplicate.