From owner-freebsd-questions@FreeBSD.ORG Tue Aug 2 10:39:55 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEC3B106566B for ; Tue, 2 Aug 2011 10:39:55 +0000 (UTC) (envelope-from ttsestt@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 70B638FC0C for ; Tue, 2 Aug 2011 10:39:55 +0000 (UTC) Received: by gxk28 with SMTP id 28so5064488gxk.13 for ; Tue, 02 Aug 2011 03:39:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:message-id:user-agent :mime-version:content-type; bh=lsg4wiCgwQTCaheo8aKV4LAqLRFmezFa7CwFi1l4dUk=; b=FtaHHjV8DHEPoC89GYdsCd+N1wNNHFtUh9LRGq1iFlO89bTq8Crmifvvc4b0DfAL2r q4pEPMWh8o72NMd5T/ySWg4/mrgjPNa92QJ/pul7huqaRow71MedZbQTRJQ9nY4Opv3a yAc6pO9GpFM/+qOQTLD5jtevNqPTTuQMqWay4= Received: by 10.91.160.6 with SMTP id m6mr3822198ago.199.1312279770330; Tue, 02 Aug 2011 03:09:30 -0700 (PDT) Received: from localhost (zoe.desire.se [85.8.28.11]) by mx.google.com with ESMTPS id j16sm2752101ank.23.2011.08.02.03.09.25 (version=SSLv3 cipher=OTHER); Tue, 02 Aug 2011 03:09:29 -0700 (PDT) From: Test Rat To: Yuri References: <4E364E1C.7040800@rawbw.com> Date: Tue, 02 Aug 2011 14:09:18 +0400 Message-ID: <86zkjsrupd.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD Questions Subject: Re: Xorg at 100%CPU when browser is on 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, 02 Aug 2011 10:39:55 -0000 Yuri writes: > I saw this with firefox, now I see the same with chrome. > > After a while when the browser is launched with ~10 tabs open, Xorg > begins to consume 100% CPU and all graphics apps get > sluggish. Quitting the browser brings situation back to normal. [...] Have you tried to reproduce with a more simple test case after looking at what sorts of requests firefox/chrome sends to Xserver via xscope/xmon? You can also trace what it's doing with pmcstat/dtrace. I don't see your issue, only rarely the one in ports/156889.