From owner-freebsd-chromium@FreeBSD.ORG Mon Jan 14 22:08:12 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EF7CA8BF for ; Mon, 14 Jan 2013 22:08:12 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by mx1.freebsd.org (Postfix) with ESMTP id 84541E6F for ; Mon, 14 Jan 2013 22:08:12 +0000 (UTC) Received: by mail-oa0-f41.google.com with SMTP id k14so4605425oag.14 for ; Mon, 14 Jan 2013 14:08:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=OvQdQzKfF6ByC5ZC+ujAtAFhHw4nvZ2t7u8hZiD26jQ=; b=iCDh8sHXUfneGIZkTR6+XQFatyMz9rkimTH2Cjs1U5bCo+P99pcXFdZL5Yk4VYhAZT RoaP2cMrpm10JKMxRGcMV1C987PnK1f2HB5y+p3a7IIH6xCcZdazBH3LQvK2gDvR4o4F KMzfgG89/2+ExKSdfCEwlsU3LM9kClZRF4bd49HCI1N6g9/WDQdrUQpBbtpwpjrKGHIE nmuZ3XI3E5obc+yfsjSoo/tW+HRBMq247nQhUHNu7OKgHWIoYcRlAHFQoWG4FQ0UsgS2 BpqTrjR0/FpPeEBk6GdIbB34eFwOmA+w9QpPtWBiI0FoYFCqSwi1elf5VTRgbjeT6q3z LdeA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=OvQdQzKfF6ByC5ZC+ujAtAFhHw4nvZ2t7u8hZiD26jQ=; b=JXahzbuzoXREdJ08iTRfr0LwMOTorNF1ZtH1lPYQ/nYkZKkncY6LIQQdNpOB2qldJ/ /EagrKMC/5n+PjkJSYZC/4MeEW4Ace2mcNkZqpe9Ssi3ky4t2NxK+WxPY0chMRoCS5k5 HVL1CugaG7VDjs7JcTGGt+pNHrvsXZ6npE3Mw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=OvQdQzKfF6ByC5ZC+ujAtAFhHw4nvZ2t7u8hZiD26jQ=; b=i3O70jXIeOvZB3M376Tpu9kRq6vn07Qh5uhQPqZ3Mqtdf8af390Ya/OO4XXGpV6Ceu 8xRSQP53x47KHXd2vxavFXVQMybGxYbE+WDw46YD5IhQpBh9KMlherHMLFF+0qGQG0Lj jhIJIBl5BGiBAudymslUDW6358F2NC9yANCbDbAvi7tzhd16UIDJQeQsJMSTmrHsR+oV hoqh4srY5WVfK0GMFngtf4Paclgoq3QIV9ELkLeqkxZ7h787YfCZQfK87HxyS3Iq46Ex j4LggFiPOW0fsIeE/QTwNmiYIRoDz80Kug8IFXrfYecSmqrxXI9uXEKMQFXRfwkXdTgS mP7w== MIME-Version: 1.0 Received: by 10.182.174.34 with SMTP id bp2mr62346694obc.16.1358201286230; Mon, 14 Jan 2013 14:08:06 -0800 (PST) Sender: evanm@google.com Received: by 10.76.129.101 with HTTP; Mon, 14 Jan 2013 14:08:06 -0800 (PST) In-Reply-To: <50F47E0F.9070900@rawbw.com> References: <50F3B4EF.6090206@chen.org.nz> <50F47E0F.9070900@rawbw.com> Date: Mon, 14 Jan 2013 14:08:06 -0800 X-Google-Sender-Auth: oT1sd0e2k68NHGSs7kqhfDL6_LU Message-ID: Subject: Re: Oddness with latest chromium From: Evan Martin To: Yuri Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkb5hJHFyZa+/5dscIyz8FzpiTi+54/rGGAQkqyY2r4/yNEdAlyT0ZwRT7pPX5Q1eAwHAn19ueNljUO5zlZxpPlufTQzJGoF9zUluvp397wbtNyw01OarRr7gpHEiCkVG+aOsPau4cPTvqhNtue5/r9QSiuxJCWA8JxKY9Z1WBJXcuua6K27KVI4BFgePyS9XLrS6F5f0cfnMeA2JU2XTVSTv3DTg== Cc: freebsd-chromium@freebsd.org, Jonathan Chen 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, 14 Jan 2013 22:08:13 -0000 (I wrote some of the code in this area for Chrome, but all my code has likely been removed by this point. It's used for better graphics performance -- reducing copies of pixels rendered by WebKit as they make their way to the X server.) It looks like there's some explicit attempt by Chrome to detect FreeBSD and work around this area. It wouldn't surprise me if the fallback codepath was wrong in some way. http://code.google.com/searchframe#OAMlx_jo-ck/src/ui/base/x/x11_util.cc&exact_package=chromium&q=shmget&type=cs&l=391 It appears that this code attempts to detect if you have this flag set and if so it falls back to a slower codepath. It wouldn't surprise me at all if this slower codepath had bitrotted in some way. It appears the Opera browser relies on it as well: http://forums.pcbsd.org/showthread.php?t=8018 One ChangeLog of theirs says "Note: On FreeBSD shared memory doesn't work by FreeBSD design." which seems a bit sad. Here's the Chrome code that relies on the detachment behavior, which has a comment describing why it does it: http://dxr.mozilla.org/mozilla-central/ipc/chromium/src/chrome/common/transport_dib_linux.cc.html#l39 >From some discussion in other bug trackers, it appears the behavior Chrome (and other tools like VMWare) rely upon isn't allowed by POSIX, which is why you can toggle the strict behavior with a flag on FreeBSD. But that's just my impression from reading some random forum posts. On Mon, Jan 14, 2013 at 1:52 PM, Yuri wrote: > > On 01/14/2013 13:30, Jonathan Chen wrote: >> >> Ok, that appears to be the key tunable that starts to make everything work >> again. I've been using chromium for about an hour now and haven't >> encountered any unexpected behaviour so far. > > > This also means that some error condition due to the lack of this tunable setting went unnoticed and chrome was malfunctioning instead of warning about the issue. > > Yuri > > _______________________________________________ > 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"