From owner-freebsd-x11@FreeBSD.ORG Sun Nov 10 17:40:01 2013 Return-Path: Delivered-To: freebsd-x11@smarthost.ysv.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 ESMTP id AE54BFCB for ; Sun, 10 Nov 2013 17:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B11626E7 for ; Sun, 10 Nov 2013 17:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rAAHe1de002077 for ; Sun, 10 Nov 2013 17:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rAAHe1lB002076; Sun, 10 Nov 2013 17:40:01 GMT (envelope-from gnats) Date: Sun, 10 Nov 2013 17:40:01 GMT Message-Id: <201311101740.rAAHe1lB002076@freefall.freebsd.org> To: freebsd-x11@FreeBSD.org Cc: From: "Sean C. Farley" Subject: Re: ports/183435: x11/xorg: 100% CPU use of xorg using firefox when showing large images (say 20 Mpixel) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: "Sean C. Farley" List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2013 17:40:01 -0000 The following reply was made to PR ports/183435; it has been noted by GNATS. From: "Sean C. Farley" To: bug-followup@FreeBSD.org, w-info2@xs4all.nl Cc: Subject: Re: ports/183435: x11/xorg: 100% CPU use of xorg using firefox when showing large images (say 20 Mpixel) Date: Sun, 10 Nov 2013 12:38:08 -0500 (EST) I have seen this before. It is related to the xrender capability of Firefox. Try disabling xrender within Firefox, by changing gfx.xrender.enabled to false. I am not sure if Firefox and/or the Nvidia driver is at fault for it. Does this workaround help you? Sean -- scf@FreeBSD.org