Date: Wed, 23 Mar 2011 08:50:53 +0000 From: Baptiste Daroussin <bapt@freebsd.org> To: George Liaskos <geo.liaskos@gmail.com> Cc: freebsd-chromium@freebsd.org Subject: Re: Chromium now works on CURRENT. Message-ID: <AANLkTi=OUz_K0SiHCvYkHVE-v6GmmJpVP14CaRQG1w=W@mail.gmail.com> In-Reply-To: <AANLkTimY8%2BLcY7suwtbN2phaK3y7wWvSD%2BbNRGq2-Kp8@mail.gmail.com> References: <AANLkTi=70MJ3EtGSXU_zib2h2K1nDbt_nV_MhOZRHULw@mail.gmail.com> <20110323073852.GA725@bsd.hu> <AANLkTimY8%2BLcY7suwtbN2phaK3y7wWvSD%2BbNRGq2-Kp8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/3/23 George Liaskos <geo.liaskos@gmail.com> > > Hi > > > > What does the v8 patches fix exactly? > > On FreeBSD amd64 a bug in V8 is triggered which causes mksnapshot to > crash with stack overflow. > > Patches from issue 6682026 [http://codereview.chromium.org/6682026] > resolve this. I don't know if openbsd is affected, are you able to > build V8? > Our node.js is marked with ONLY_FOR_ARCHS=i386 for this reason. > > I have not tried Chromium 10 on 8.x yet but with Chromium 9 a call to > pthread_cond_wait returns EPERM, if you start chromium with > --single-process it works, I've also used a build from 8x on CURRENT > with success just by using libmap.conf for libthr. > > Is there any known bugs in our libthr that could be causing this? > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " > That is exactly the problem I got 8.x running in single process mode. Let's investigate the difference in libthr between CURRENT and 8.x regards, Bapt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=OUz_K0SiHCvYkHVE-v6GmmJpVP14CaRQG1w=W>