Date: Mon, 9 Sep 2013 14:09:25 -0700 From: Evan Martin <evan@chromium.org> To: Lapo Luchini <lapo@lapo.it> Cc: freebsd-chromium@freebsd.org Subject: Re: Problems with pkgng (pkg upgrade) Message-ID: <CAFzwtj3Q21fi=hZL-0_i67Qb7bsbUJ9bZj0Joq7p6XMuGc8NFw@mail.gmail.com> In-Reply-To: <l0kf3b$fka$1@ger.gmane.org> References: <l0kf3b$fka$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Updates are a tricky problem. I expect on FreeBSD some of the Linux-specific hacks we made in Chromium for updates aren't implemented. You can read more details here (imagine FreeBSD in place of "Linux" in the post): http://neugierig.org/software/chromium/notes/2011/08/zygote.html I believe there are pieces of Chromium that *don't* go through the preforked helper, for complicated reasons related to the sandbox; I expect those to be especially problematic on updates. On Mon, Sep 9, 2013 at 5:31 AM, Lapo Luchini <lapo@lapo.it> wrote: > Hi! > > I'm wondering why the chrome process has the habit of crashing when I do > "pkg upgrade" (last time, it was a signal 11). > > I certainly expect something like this during a "pkg upgrade" that involv= es > "chromium" package itself, but this also happens with updating something > totally unrelated, such as when "pkg upgrade" only upgrades "pkg" (in the > first run); or maybe upgrading "nano", or stuff like that. > > Is it expected? > Is it only me? > In that case, I can probably help with debug. > > -- > Lapo Luchini - http://lapo.it/ > > =93You don't have to distrust the government to want to use cryptography.= =94 > (Phil Zimmermann) > > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFzwtj3Q21fi=hZL-0_i67Qb7bsbUJ9bZj0Joq7p6XMuGc8NFw>