Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 04 Nov 2003 22:42:59 -0500
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        Simon Barner <barner@in.tum.de>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: gnome 2.4 freezee some apps
Message-ID:  <1068003779.67120.14.camel@shumai.marcuscom.com>
In-Reply-To: <20031105032628.GA2172@zi025.glhnet.mhn.de>
References:  <1067954680.878.1.camel@debianito.inferno> <20031104161405.GJ96543@toxic.magnesium.net> <20031104180053.GA47902@zi025.glhnet.mhn.de> <20031105032628.GA2172@zi025.glhnet.mhn.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-1D6L4XH8GVE+nB8l8htJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2003-11-04 at 22:26, Simon Barner wrote:

> I think this whole story is related with recent changes to some bonobo st=
uff
> that is documented in the GNOME cvs repository:
>=20

Exactly what versions of libbonobo[ui] do you have installed?

> I ran galeon under gdb (on -CURRENT). I have attached the full backtrace
> of a crash (with debugging symbols for galeon2, glib20 and libbonobo.

Looks like a race to free an object.  I've seen this before in
gnome-panel.

>=20
> I found a work-around for this bug: Commenting out the explicit
> destruction of automation factory (patch that also enables additional
> debugging output is attached) makes the Galeon process terminate quickly
> and cleanly (on both -STABLE and -CURRENT).
>=20
> I know that this is a really ugly `solution', and I wonder whether this
> will leak some memory in libbono (the Galeon process is doomed to die at
> this time of the execution anyway, so there should be no problem - of
> course from the memory point of view).

Yep.  It would be better to make sure we free what we malloc, and only
do so once.  The crash only occurs on -CURRENT due to extra malloc
debugging.  Doing:

# ln -s aj /etc/malloc.conf

Will most likely prevent the bus error.

> Well, perhaps you or someone can find the real cause of the troubles from
> the attached material - for now the proposed patch will do for me.

I'll take a look, but I first need to know the exact version of all your
installed ports.

Joe

>=20
> Simon
--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-1D6L4XH8GVE+nB8l8htJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/qHHDb2iPiv4Uz4cRAkPcAJ91ueGsDNtM44tcsav+fTKzJm58+gCbBU7T
kNKzi+WbDGKV4kDmgZiv7EA=
=pK24
-----END PGP SIGNATURE-----

--=-1D6L4XH8GVE+nB8l8htJ--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1068003779.67120.14.camel>