Date: Wed, 21 May 2014 23:03:23 +0200 From: Luigi Rizzo <rizzo@iet.unipi.it> To: freebsd-chromium@freebsd.org Subject: Re: lost chromium - chromium core dumps on stable/9 Message-ID: <20140521210323.GA67425@onelab2.iet.unipi.it> In-Reply-To: <CA%2BhQ2%2BgFhvSB4DquLkrQoM7%2Bzz7pY_uGYOH6s5ni4H7uvXxa7g@mail.gmail.com> References: <CA%2BhQ2%2BgFhvSB4DquLkrQoM7%2Bzz7pY_uGYOH6s5ni4H7uvXxa7g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 11, 2014 at 08:44:54AM +0200, Luigi Rizzo wrote: > hi, > i recently attempted to upgrade chromium from 31.x to 34.x > on my FreeBSD stable/9, through a svn update of the entire > ports tree, followed by a portupgrade -Rf www/chromium > > After that it seems i am no longer able to run chrome on that > machine, they all crash > shortly after starting with a few errors as listed below. ... for the records, since i got the same after upograding to 10.X, i decided to investigate more on the problem, and i found out that things go bad when i login into my chrome account and chrome starts downloading extensions from my other (unvoluntarily synced) chrome instances. Errors before the crash are the same pixman bugs i was seeing before: > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug > > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug > > *** BUG *** Disabling the app synchronization at least stops the panic. I have no idea what extension is giving trouble but i notice that right before the panic the 'Hola' icon appears (i have other things on my mac and Linux, including google drive, hangout and probably other extensions not supported on FreeBSD). One extension that is also active (the icon appears on the menubar, but not on the list of extensions) is "Hola", which has way too many permissions. I am not sure that is the culprit though. Anyways, for the time being the crashes are blocked. This said, they should not occur in the first place so there must be some underlying problem that needs to be addressed. cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140521210323.GA67425>