From owner-freebsd-chromium@FreeBSD.ORG Mon Sep 9 13:29:36 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 46CFE7B for ; Mon, 9 Sep 2013 13:29:36 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D311424FB for ; Mon, 9 Sep 2013 13:29:35 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id w62so4325287wes.29 for ; Mon, 09 Sep 2013 06:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=aLxFHpfAsqxEi4duSf2q+L8HO7GQzNlAkTQje8emI9k=; b=qSMuY6A/OxCs75G2js8R3zWv3tgnp89aC/MiB8HZzWL/AA74yyng9ZKfnmjm7VSuIl 1Q//E65f1u+J62qQ4czNFqFFUiccQgt5sKkodvG/LO7LrMLEfAQdDLMwAXU44JXwEy2e 3WnupuqxgUcFDdqEZfCxlVjSZB1OAHmu9cgE3vb9Z6v0YfxkKT7N/Vw2oAOiY04U/Q2Q oF+9QOnQw75xtn4Eh3UwYvqllFiigxlIjb5H8qZOvkS/nL+ZkOqphX10VQfXeVecWZsb l1UFD8kcE+pZFZ7/04DT0zm+Yk2JGlfCVhTfVCeJd+BDd6cPKMc0L0LpmxanhPGIzXUh wwvA== X-Received: by 10.180.184.107 with SMTP id et11mr8599090wic.60.1378733374378; Mon, 09 Sep 2013 06:29:34 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id iz19sm14745964wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 09 Sep 2013 06:29:33 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 9 Sep 2013 15:29:30 +0200 From: Baptiste Daroussin To: Adam McDougall Subject: Re: Problems with pkgng (pkg upgrade) Message-ID: <20130909132930.GD40186@ithaqua.etoilebsd.net> References: <522DC5CD.3060006@egr.msu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lc9FT7cWel8HagAv" Content-Disposition: inline In-Reply-To: <522DC5CD.3060006@egr.msu.edu> User-Agent: Mutt/1.5.21 (2010-09-15) 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 13:29:36 -0000 --lc9FT7cWel8HagAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 09, 2013 at 08:57:49AM -0400, Adam McDougall wrote: > On 09/09/13 08:31, Lapo Luchini wrote: > > Hi! > >=20 > > I'm wondering why the chrome process has the habit of crashing when I do > > "pkg upgrade" (last time, it was a signal 11). > >=20 > > I certainly expect something like this during a "pkg upgrade" that > > involves "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. > >=20 > > Is it expected? > > Is it only me? > > In that case, I can probably help with debug. > >=20 >=20 > It is not only you, it happens on pretty much all my installs. It can > happen even if you pkg install something small and unrelated to > chromium. Last week I was shocked when I ran pkg upgrade and it did NOT > cause chromium to crash; it had even replaced chromium itself! I don't > think it crashes 100% of the time, but most. I don't have time to debug > it. Just in case it got fixed, be sure to test using the latest > chromium version from ports. > _______________________________________________ > 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" That is because pkgng overwrite the binaries during an upgrade instead of f= irst unlinking them then extract the new one. This is planned to be fixed soon. regards, Bapt --lc9FT7cWel8HagAv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlItzToACgkQ8kTtMUmk6Ez7sgCfWB+g+p+N5giYkK1HOH9Xkf/N xJwAniA2H6QCrvPraPCKkqwwJD2+OE+g =HBjy -----END PGP SIGNATURE----- --lc9FT7cWel8HagAv--