From owner-freebsd-gecko@FreeBSD.ORG Wed Jun 4 22:17:26 2014 Return-Path: Delivered-To: freebsd-gecko@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5808791F; Wed, 4 Jun 2014 22:17:26 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 3D9CE2AC9; Wed, 4 Jun 2014 22:17:25 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7A4FC3AE61; Wed, 4 Jun 2014 15:17:25 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-gecko@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Firefox chokes up for several seconds... frequently In-Reply-To: <20140604195803.GJ2341@home.opsec.eu> Date: Wed, 04 Jun 2014 15:17:25 -0700 Message-ID: <41957.1401920245@server1.tristatelogic.com> X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 22:17:26 -0000 In message <20140604195803.GJ2341@home.opsec.eu>, Kurt Jaeger wrote: >Hi! > >> > I spoke too soon. >> > >> > The problem is back again. >> > >> > As a friend of mine used to say "Problems that go away by themselves >> > come back by themselves". >[...] >> Try changing "gfx.xrender.enabled" from True to False in about:config. >> This solved a similar problem with scaled images for me a couple years ago. > >I have seen the same problem (freezes for several seconds) >and changed this config. OK, I changed it. Now I guess I'll see what happens. >My firefox process currently has 3.6 GB RAM with 3.1 GB RSS (!) Jesus! Yes! Mine is showing up (under top) as follows: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 58591 rfg 47 52 0 2811M 2328M uwait 2 690:23 44.19% firefox Jesus! 2.8 GIGABYTES !?!?!?! No wonder the thing runs like a pig. Probably half of it is swapped out at any given time. What the hell could it possibly be using so much memory for? Is it trying to cache every blessed last bit of crap it has received?? >That was much better in the past. I had firefox running for several >month with heavy browsing. Now I need to restart it every 1-2 weeks. Have you mentioned this to anybody? I mean like, you know, anbody who is involved with Firefox development? >Hmm, one thing: I had gnash-0.8.10_10 installed. Deleted it now. I don't have any gnash\* anything installed.