From owner-freebsd-current@FreeBSD.ORG Fri Mar 2 00:08:01 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1904F106564A for ; Fri, 2 Mar 2012 00:08:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id A26268FC13 for ; Fri, 2 Mar 2012 00:08:00 +0000 (UTC) Received: by wgbds10 with SMTP id ds10so66856wgb.1 for ; Thu, 01 Mar 2012 16:07:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=lonprFNlA6SXJlBGgorK7ULhKLNxL304ZF+adT+AyAU=; b=JwY5AyGF0G0V1Lin4lhhN+OHrKg/JDj7i3/t/6knZW+ZXjzCgvbRpD2AQpStxUQwt/ uzGEaOW4Pf+4R9h8Plm7BbiHmc81JkxjpHCnoB+Tg1UnV4ZULuK3+FehwHsh5paecqHZ 2UQ8QokdWzluG9KIIhjJQt/wvWFAL49QCjvTjbEaEJh8v1cyfzTZD6rYl2dPTUVKDrY+ Iny9H0Iwh31Mw7ffSF9F4pkUb4+VPJGi4ELZGNsbhZMJwNx1AXspPb609AgVhV+hkycS 78Xo1GOegYZr7XuKKQUwyZIRFcRP03jqYyDL4WCZpZPf1WFgqf1HSieFXZdVcdHE6TSQ 9/EA== MIME-Version: 1.0 Received: by 10.180.96.8 with SMTP id do8mr10724wib.21.1330646879595; Thu, 01 Mar 2012 16:07:59 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.198.81 with HTTP; Thu, 1 Mar 2012 16:07:59 -0800 (PST) In-Reply-To: References: Date: Thu, 1 Mar 2012 16:07:59 -0800 X-Google-Sender-Auth: Z69aZAYtEFiJqDGt-PwV7Ivl0jY Message-ID: From: Adrian Chadd To: "deeptech71@gmail.com" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: SeaMonkey eats the CPU as of r232144 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 00:08:01 -0000 This is totally reproducable? Can you switch back/forth? Adrian On 29 February 2012 04:24, deeptech71@gmail.com wrote: > As of r232144, SeaMonkey (a web browser) runs rather slowly and is > constantly eating 100% CPU time. Before r232144, SeaMonkey would start > up and run faster, and when it is not in use (is idling), its CPU > usage would slowly converge to 0. > > I have a P4 processor [with HT], an r232012 world, and similarly recent ports. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"