From owner-freebsd-gnome@FreeBSD.ORG Mon May 1 22:28:17 2006 Return-Path: X-Original-To: gnome@FreeBSD.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91FFA16A402; Mon, 1 May 2006 22:28:17 +0000 (UTC) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3808043D45; Mon, 1 May 2006 22:28:17 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 06254F27B7; Mon, 1 May 2006 15:28:17 -0700 (PDT) X-Virus-Scanned: by amavisd-new at mcneil.com Received: from mail.mcneil.com ([127.0.0.1]) by localhost (triton.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOXdjgJqH3ei; Mon, 1 May 2006 15:28:16 -0700 (PDT) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 88D56F26AA; Mon, 1 May 2006 15:28:16 -0700 (PDT) From: Sean McNeil To: Joe Marcus Clarke In-Reply-To: <44568AA2.5080800@FreeBSD.org> References: <1146517148.65163.3.camel@triton.mcneil.com> <1146519451.11475.3.camel@triton.mcneil.com> <1146520007.61567.29.camel@ikaros.oook.cz> <1146520272.11633.3.camel@triton.mcneil.com> <1146520798.61567.31.camel@ikaros.oook.cz> <1146521990.13629.13.camel@triton.mcneil.com> <1146522119.61567.33.camel@ikaros.oook.cz> <44568AA2.5080800@FreeBSD.org> Content-Type: text/plain; charset=iso-8859-2 Date: Mon, 01 May 2006 15:28:16 -0700 Message-Id: <1146522496.14105.5.camel@triton.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: gnome@FreeBSD.org, pav@FreeBSD.org Subject: Re: liferea crashing X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 22:28:17 -0000 On Mon, 2006-05-01 at 18:24 -0400, Joe Marcus Clarke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pav Lucistnik wrote: > > Sean McNeil píše v po 01. 05. 2006 v 15:19 -0700: > >> On Mon, 2006-05-01 at 23:59 +0200, Pav Lucistnik wrote: > >>> Sean McNeil píše v po 01. 05. 2006 v 14:51 -0700: > >>>> On Mon, 2006-05-01 at 23:46 +0200, Pav Lucistnik wrote: > >>>>> Sean McNeil píše v po 01. 05. 2006 v 14:37 -0700: > >>>>> > >>>>>> On Mon, 2006-05-01 at 13:59 -0700, Sean McNeil wrote: > >>>>>>> I get intermittent crashes with liferea when I try to read new items: > >>>>>>> > >>>>>> Another one. This happens almost every time I get a new article, click > >>>>>> on the tray icon, then hit the next button. Looks like src_buf is null: > >>>>> Can't reproduce. Liferea works just fine here on GNOME 2.14 and amd64. > >>>>> Sorry. > >>>> Are you using the standard theme? I think perhaps there might have been > >>>> some changes to the file structure for theme support. I've changed my > >>>> selection slightly to see if it makes a difference. I was using: > >>>> > >>>> MardiGras Controls > >>>> Smokey Window Borders > >>>> Lila Icons > >>> I'm pretty much on the stock GNOME, minus Mist window borders (one of > >>> the stock themes). > >>> > >>> You could try to create a new user, copy over your ~/.liferea and try it > >>> out there. > >> Standard "Smokey" theme causes same problem. I tried to attach > >> my .liferea (as liferea.zip), but the freebsd mail filter blocked it. I > >> thought it might be the cache, but I deleted that and next'd through > >> everything then hopped around a little and it crashed. I can crash it > >> in less than a minute clicking the next button and all around on the > >> panels and categories. Usually I have to delete the window first and > >> hit the tray icon to bring it back. > >> > >> The only other thing that might be related is that I have an SMP machine > >> (amd64 athlon 2x). This could be a threading issue with memory freed too > >> soon. As Marcus stated, it looks like memory corruption. So this might > >> fit. > > > > I'm on SMP too. Well, it's a mystery :) > > Maybe not. Non-CURRENT machines should not see this crash. Machines > with jemalloc should almost always see crashes like this even with > malloc flags set to aj (though setting them to AJ does help things along). Just tried with AJ (was aj) and got the same thing crash.