From owner-freebsd-chromium@FreeBSD.ORG Mon Sep 9 21:09:27 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 150C273E for ; Mon, 9 Sep 2013 21:09:27 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF51F2469 for ; Mon, 9 Sep 2013 21:09:26 +0000 (UTC) Received: by mail-qa0-f48.google.com with SMTP id k4so475966qaq.7 for ; Mon, 09 Sep 2013 14:09:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=zhuYEvuCMNN4TnAa1K7KR4t9THxydVj7V7bHvmN9FCg=; b=O9II0ZMzIeEIEL/CUtBC/mM0lRbSThbPMhK8CpMKkdwLV3edQj0Lap98cskg6IiQO0 nnCNqUaUZ3qBulDxe1ClSNxSxLpFK4cf2mgA3BGdhFbPk3t0w8BtEFt3VZsb7xbetDGb 4Md0pKqecLe1vO5esaPH1OC6ltuxw4MTKhwHWN+JzrwW063aHnijth+g/zKKWDi0KoVQ cKjRHlm4cqmNqbG+68b4DmRPOkQw49XHcWoRV7KL9NscbkVLieGjSjMoMGENk6RaEtBN 4s0gAS7V5ted2niqbfbzc7nDOsnisQjhxhYzdmj6/42ehjHlr6kIpt/efhyofV/gfBk7 aKog== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=zhuYEvuCMNN4TnAa1K7KR4t9THxydVj7V7bHvmN9FCg=; b=JBYtIYOeD+Q9RFkeq+5H0hB8xRwkGH3VMz9CNANwGNdnC+BpX1cqZArKqHMaSBFdd9 8PqXnEs+8h7wwvWID9stZ/hI8VRHRmxqKHNW7+2Ff1nHuIn/S+WnfJyHlIs688JslCVi mUGk9vqP+OPljpZa+PFvmKmy/iwCH8m+yP/5k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=zhuYEvuCMNN4TnAa1K7KR4t9THxydVj7V7bHvmN9FCg=; b=Sn5XXUTGn/1jOOKpmK/LHvgGu2fWEdn+waunNyUZb5z0rC4Q6Z2/zUHSfkRk7w1wwq FYFJwp20aLlRCc7SRn4kQRV3fd6/lPM5oh+pkkO9BH7CNrnKc3NLjBUMHEX+pLja8YEq qiY/I2wh6TFAL48Nyrb7AXqdP7Ooa8OqJmQmLUVNwjEAJx50lcF2xXU9xrqXu2mgMR1Z F89T7UFmLC/vxDhgbIn/23l36fiDJbyS2Xq7EeFxDl+vpEHrlnspptXXcnGH5W2Vuz2N 6LBiE15/Lxdp+MXGJiP6t8d30oB5fF7/htYdnpubWBPrAWGp/hSZ16kHj07NEt5fXovU 6gjA== X-Gm-Message-State: ALoCoQmtgLeWBNOZb5HcvMpTzOMIy9Ez+eLlbgFgzXUey0jCwipKjiEmr4JpHFv5CphveHoYdKmx+s4J43/ozxpCD6yknwV2rGihjranzxdVFCz964vogeXYI9GEV6Qhbaw6/0ueQnf+6yIysYnrjiWpXMB5G7Eqm4/w8GPcSW6/zUq/C7fILLyqY+5RQ3vcXXYKXRUoUgKgD2qImpkfFx2Pn4K+jU0OjA== MIME-Version: 1.0 X-Received: by 10.224.51.70 with SMTP id c6mr3531545qag.121.1378760965548; Mon, 09 Sep 2013 14:09:25 -0700 (PDT) Sender: evanm@google.com Received: by 10.229.207.8 with HTTP; Mon, 9 Sep 2013 14:09:25 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Sep 2013 14:09:25 -0700 X-Google-Sender-Auth: 135kUb-A8ThMreCiEE-OQ-bxOiA Message-ID: Subject: Re: Problems with pkgng (pkg upgrade) From: Evan Martin To: Lapo Luchini Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 21:09:27 -0000 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 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"