Date: Fri, 13 Jan 2006 16:20:49 -0800 From: Pascal Hofstee <caelian@gmail.com> To: Jason Evans <jasone@freebsd.org> Cc: gnome@freebsd.org, src-committers@freebsd.org Subject: Re: cvs commit: src UPDATING Message-ID: <d8a0b7620601131620n69b889d6g6080516dc583ebfc@mail.gmail.com> In-Reply-To: <200601132237.k0DMbmgQ094378@repoman.freebsd.org> References: <200601132237.k0DMbmgQ094378@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/13/06, Jason Evans <jasone@freebsd.org> wrote: > jasone 2006-01-13 22:37:48 UTC > > FreeBSD src repository > > Modified files: > . UPDATING > Log: > Note that libc's malloc implementation has been replaced. > > Approved by: markm (mentor) > > Revision Changes Path > 1.434 +5 -0 src/UPDATING Well .. i decided to take the plunge and the core system seems to be as stable as always however i have found that after the jemalloc import anything that uses GTK refuses to start and it looks like all coredumps seem to boil down to the exact same chain of function calls. I have CC-ed the gnome@ list in the hope that they can get a better informed clue about what's going on here, as i have been having some minor issues with the latest set of gnome-updates on the MC-ports-tree ... but nothing of this magnitude as i am now experiencing after the jemalloc update. i have put a full backtrace of one of the observed crashes up at=20 http://phoenix.student.utwente.nl/~daeron/gtk-demo.txt I am very curious to know wether this is a gtk20/glib20 issue .. or a potential jemalloc bug. I am running FreeBSD/amd64 built shortly after the jemalloc import and have tried both no malloc.conf and an "aj" malloc.conf but the problem remains identical. If you need any additional information please contact me. -- Pascal Hofstee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8a0b7620601131620n69b889d6g6080516dc583ebfc>