From owner-freebsd-questions@FreeBSD.ORG Tue Jul 17 14:59:20 2012 Return-Path: Delivered-To: questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEBBA106564A; Tue, 17 Jul 2012 14:59:19 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) by mx1.freebsd.org (Postfix) with ESMTP id 77DBD8FC14; Tue, 17 Jul 2012 14:59:19 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.5/8.14.5) with ESMTP id q6HEqkjL074591; Tue, 17 Jul 2012 15:52:46 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <50057C3E.1030409@qeng-ho.org> Date: Tue, 17 Jul 2012 15:52:46 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120626 Thunderbird/13.0.1 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <20120717145613.20783z1jrv0xapyc@webmail.raad.tartu.ee> <50056D2C.7050508@FreeBSD.org> In-Reply-To: <50056D2C.7050508@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: questions@FreeBSD.org Subject: Re: "Twitter.com is loading slowly" after updating to Firefox 13.0.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 14:59:20 -0000 On 07/17/12 14:48, Greg Larkin wrote: > On 7/17/12 7:56 AM, Toomas Aas wrote: >> I'm having this problem on two different computers, one running >> 8.3-STABLE and the other running 9.0-STABLE. After updating Firefox >> from 12.0 to 13.0.1, whenever I access twitter.com, I can log in >> but after that a message appears saying that "Twitter.com is >> loading slowly", and the site is practically unusable - clicking on >> any of the links has no effect. >> >> Various support sites say that this may be a problem with Firefox >> extensions or plugins, or some difficult-to-find problem which may >> be worked around by clearing cache and cookies, or trying with a >> new Firefox profile. >> >> For testing, I have disabled all extensions and plugins. I have >> also tried moving my ~/.mozilla directory out of the way so that >> new empty profile is created. None of this has helped. The fact >> that this is happening on two totally different machines is leading >> me to think that maybe this is some peculiarity in a way that >> Firefox is compiled on FreeBSD, so I decided to ask if anyone else >> is seeing this. >> >> When updating Firefox to 13.0.1, I didn't change any port >> configuration options from what I was using previously: cat >> /var/db/ports/firefox/options # This file is auto-generated by >> 'make config'. # Options for firefox-13.0.1,1 >> _FILE_COMPLETE_OPTIONS_LIST=DBUS PGO DEBUG LOGGING >> OPTIMIZED_CFLAGS OPTIONS_FILE_SET+=DBUS OPTIONS_FILE_UNSET+=PGO >> OPTIONS_FILE_UNSET+=DEBUG OPTIONS_FILE_UNSET+=LOGGING >> OPTIONS_FILE_SET+=OPTIMIZED_CFLAGS >> > > Hi Toomas, > > I ran into this problem with FF13 on OS X over the weekend, and I > fixed it with a suggestion I found somewhere online: > > Open the about:config preference pane in FF. Change the > http.keep-alive property to "true", and you should be all set. > > Hope that helps, My FF 13.0.1 shows true as the default state for network.http.keep_alive