Date: Wed, 14 May 2003 03:32:20 -0500 From: Jeremy Messenger <mezz7@cox.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: freebsd-gnome@freebsd.org Subject: Re: seahorse crashes at the every exit in -CURRENT.. Message-ID: <opro5lz6cu8ckrg5@smtp.central.cox.net> In-Reply-To: <1052889730.60558.33.camel@shumai.marcuscom.com> References: <opro48bsb18ckrg5@smtp.central.cox.net> <1052885267.60558.6.camel@shumai.marcuscom.com> <opro5bdo058ckrg5@smtp.central.cox.net> <1052889730.60558.33.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 May 2003 01:22:10 -0400, Joe Marcus Clarke <marcus@marcuscom.com> wrote: > On Wed, 2003-05-14 at 00:42, Jeremy Messenger wrote: >> On 14 May 2003 00:07:47 -0400, Joe Marcus Clarke <marcus@marcuscom.com> >> wrote: >> >> > On Tue, 2003-05-13 at 23:36, Jeremy Messenger wrote: >> >> It just crashes at the every exit, which I just run and exit it. I >> have >> ran it under the gdb, so here's info. >> > >> > See if this fixes it. >> >> Nope, it doesn't fix. The result is same, crashed and I ran it under the >> gdb again. The info of gdb is same. > > Yeah. I thought it might be trying to double-free the sctx, but, in > fact, it looks like they have a bit of a race condition when quitting > the app. They unref the main widget, then try to destroy the context it > contained. If you comment out line 288 in > libseahorse/seahorse-widget.c, the problem goes away. File this with > the developers if a bug doesn't exist already. They either need to not > destroy the context, or fix line 545 of src/seahorse-key-manager.c not > to use seahorse_widget_destroy for the data_destroy...or something else > that tidies this up. Ok, thanks! Here's url in case if anyone want to follow it. http://bugzilla.gnome.org/show_bug.cgi?id=112958 Cheers, Mezz > Joe > >> >> Cheers, >> Mezz >> >> > Joe >> > >> >> >> >> ==================================== >> <snip> >> >> ==================================== >> >> >> >> I saw that '0xd0d0d0d0', so I disabled it by 'aj' in the mallco.conf >> and >> it doesn't crash anymore. It does fix the problem with the 'aj' >> in the >> malloc.conf. Let me know if I should report it to the bugzilla >> or so. >> >> >> >> Cheers, >> >> Mezz -- bsdforums.org 's moderator, mezz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opro5lz6cu8ckrg5>