From owner-freebsd-chromium@FreeBSD.ORG Sun Feb 3 17:29:18 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 2063BDC for ; Sun, 3 Feb 2013 17:29:18 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id D28AD224 for ; Sun, 3 Feb 2013 17:29:17 +0000 (UTC) Received: from pool-151-203-245-187.bos.east.verizon.net ([151.203.245.187] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U23NV-000BGq-1D for freebsd-chromium@freebsd.org; Sun, 03 Feb 2013 17:29:17 +0000 Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:4:221:63ff:fe5a:c9a7]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r13HTETE054139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 3 Feb 2013 12:29:15 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 151.203.245.187 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18OHbaZmiLDLNYPdG13Apmd Date: Sun, 3 Feb 2013 12:29:13 -0500 From: "J.R. Oldroyd" To: freebsd-chromium@freebsd.org Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 Message-ID: <20130203122913.6c0cf4e9@shibato> In-Reply-To: References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [IPv6:2001:470:8cb8:4::1]); Sun, 03 Feb 2013 12:29:15 -0500 (EST) X-Spam-Status: No, score=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com 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: Sun, 03 Feb 2013 17:29:18 -0000 On Sat, 2 Feb 2013 09:16:36 -0500 Eitan Adler wrote: > > I am seeing the same issue. And +1 here. I think the problem may be related to files/patch-ui__surface__transport_dib_linux.cc which replaces the immediate removal of the shm after attaching to it with removal in the destructor iff we're the last who is attached to it. The comment states: // On BSD we can't access the shared memory after is marked for deletion. but this is not true if kern.ipc.shm_allow_removed=1 which we are told to set in the pkg-message. I have removed this patch and am running with the original code. All appears well so far, but perhaps I have not been running long enough for the problem to recur. I'll post back if it it does. Of course, the original code is defensive to ensure that the shm is removed if there's a crash. Presumably, the fact that the code in the patch isn't working suggests that something is, in fact, crashing. Perhaps this is what really should be debugged. -jr From owner-freebsd-chromium@FreeBSD.ORG Sun Feb 3 17:29:37 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 C1D78EC for ; Sun, 3 Feb 2013 17:29:37 +0000 (UTC) (envelope-from joedapro9999@gmail.com) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by mx1.freebsd.org (Postfix) with ESMTP id 48ED6227 for ; Sun, 3 Feb 2013 17:29:36 +0000 (UTC) Received: by mail-bk0-f53.google.com with SMTP id j10so2494309bkw.12 for ; Sun, 03 Feb 2013 09:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7yqKmr+DhSmIYhop5ulGavbZwDiiJ46DqYP6yE9T3sc=; b=dNfHMOzR8TRKrgcyOHlBLm3sUD35r+TFc1ReXX016npWX21GmBU3pGq2YZ/X8gpeVd IfY9mKV1tMfNoxaHiXC3L7VWE8uGOI4z5ZSXLfFxvIpWYgVE0z9zPcy+H2VpPMLbTx+W 1QdYD08IkVGac44+bdJ+m2dpTlbcwxWX2FXycDNdBc/vn6jHCXc02D+7VCI4UTuGaGTw LzS/JMrVkDzvtwktDA+mVk8oaNoaVffO7jC6/BXaFhb43lLnuHyqtfLs9Dql4pkctCbB fqsPaK2z3webQHb1S0TKomxtHoTpFhxsR1Uq3laS90Ljg1JDgelWeiqB26Dm1rrZKyMg Ie4g== MIME-Version: 1.0 X-Received: by 10.204.147.5 with SMTP id j5mr4908313bkv.49.1359912569666; Sun, 03 Feb 2013 09:29:29 -0800 (PST) Received: by 10.204.49.132 with HTTP; Sun, 3 Feb 2013 09:29:29 -0800 (PST) In-Reply-To: References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> Date: Sun, 3 Feb 2013 11:29:29 -0600 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 From: Joe Guy To: Eitan Adler Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 03 Feb 2013 17:29:37 -0000 On 2/2/13, Eitan Adler wrote: > On 1 February 2013 15:17, Lawrence K. Chen, P.Eng. wrote: >> >> >> ----- Original Message ----- >>> Hi, >>> >>> I've just installed the latest chromium-24.0.1312.57; and it appears >>> to >>> suffer from the same IPC memory leakage as the version just before >>> it. When >>> no more IPC shared memory can be allocated, chromium will only >>> display a >>> blank page. Loading pages full of javascript will hurry this >>> behaviour. > > I am seeing the same issue. After some discussion with a chromium dev > he pointed me to > https://code.google.com/p/chromium/issues/detail?id=143580 > I have not looked further, but someone here may be interested in doing so. > > > -- > Eitan Adler > _______________________________________________ > 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" > From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 11:06:22 2013 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 698CE842 for ; Mon, 4 Feb 2013 11:06:22 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF2BCC6 for ; Mon, 4 Feb 2013 11:06:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r14B6MDj028287 for ; Mon, 4 Feb 2013 11:06:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r14B6Luk028285 for chromium@FreeBSD.org; Mon, 4 Feb 2013 11:06:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Feb 2013 11:06:21 GMT Message-Id: <201302041106.r14B6Luk028285@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Subject: Current problem reports assigned to 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, 04 Feb 2013 11:06:22 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/175369 chromium www/chromium: Chromimum Desktop Integration doesn't op o ports/173583 chromium www/chromium reproducibly crashes when trying do downl o ports/165637 chromium www/chromium: 17.0.963.56 fails to find some ns plugin o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 5 problems total. From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 17:00:14 2013 Return-Path: Delivered-To: freebsd-chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3A188483; Mon, 4 Feb 2013 17:00:14 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 15CABA6F; Mon, 4 Feb 2013 17:00:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r14H0Dsh099180; Mon, 4 Feb 2013 17:00:13 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r14H0Ddw099176; Mon, 4 Feb 2013 17:00:13 GMT (envelope-from edwin) Date: Mon, 4 Feb 2013 17:00:13 GMT Message-Id: <201302041700.r14H0Ddw099176@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-chromium@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/175835: www/chromium no audio playing from Google Voice 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, 04 Feb 2013 17:00:14 -0000 Synopsis: www/chromium no audio playing from Google Voice Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-chromium Responsible-Changed-By: edwin Responsible-Changed-When: Mon Feb 4 17:00:13 UTC 2013 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=175835 From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 17:20:53 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6210CA33 for ; Mon, 4 Feb 2013 17:20:53 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by mx1.freebsd.org (Postfix) with ESMTP id 07DDEBE2 for ; Mon, 4 Feb 2013 17:20:52 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id h1so4287324oag.31 for ; Mon, 04 Feb 2013 09:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YY5RMZVY020IQ1R5utIWKaDrcSjzWrqiHVY8LUF/2LA=; b=lQl+Ahd8qROlMDv4Vsvyt7T0+s53qMMvqxKJdFY9zD0KTdA8t4uPsf18Q0ShJ77jR1 sffQtkNWyjmv8vNCFlEUUIQX68Y5+xvMb+a/DUtVz7JmnVgvkW0poJdr4HQ8pwrRLai4 uzQKzxKEDzpwOYLeP7ENMx9k0a6Kh2mpoMFB9mRZYVBe04H0Fj6jKVpkxmSF4nx5TR8c qfvRmZQMQfoOkoRLxOT5wEPfZT6ASFGl4a3g2bLe9Zef1EbIuKYkGX/8lmKuP4krBKGA 6nBxSwBCAIEEzP/DXlH9SZJbysKV24o4dH4kUtBsh6UGuwfuzC3luqxjgnUJPQRZB8jK SQ+g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YY5RMZVY020IQ1R5utIWKaDrcSjzWrqiHVY8LUF/2LA=; b=fNBy+vuUDgIWkIDTnbWONQ2Zc4H4W1SX063pygaUw5Egq0uE/yaASMkRJ05eyJCO4d 9ZlFoD1g3F6qBu9b8P3j9Cq/hyZrBKbanqF/hyLHOnaQihTDZch+7vkv6APJd2FU3Jhw Bmo8JF+l6ag3nu7U6+LGccSqF+nZnYy/nZRtc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=YY5RMZVY020IQ1R5utIWKaDrcSjzWrqiHVY8LUF/2LA=; b=AZ3MYagPfO+TxrIjOHZ/sN5AVKsq6HGho8Ajqv6WFKa3r+YeNhHvolpAxcfbrCsid1 6oQ5nSAY0mZI9vFhmJG6UlYIJQtT7mBeT2VpPNV64nQ4MXPQByEdNWu+pVOSTeh3qRYP kSiWMKwzxsUZ9W58krEB6LsJ4jSMGCGaNFQu29xOwo8KjVeQ3fLCQsN9MOSRI505hm33 aAvOIRj5SDOKMilv5Buod/+ukWLX1lrFE9/ISDz4vcJ3IV3Kc6Dd6usOJsxeBd0WavDO ln167m5nmxMhL6hcwp45EjxWLIGjKqJwYMNQqotPSTXN7h7JWtUO+2SLAbno6G9ZFa+8 p/NQ== MIME-Version: 1.0 X-Received: by 10.60.7.167 with SMTP id k7mr17708896oea.20.1359998452085; Mon, 04 Feb 2013 09:20:52 -0800 (PST) Sender: evanm@google.com Received: by 10.76.72.3 with HTTP; Mon, 4 Feb 2013 09:20:52 -0800 (PST) In-Reply-To: <20130202123101.59c2ee40@shibato> References: <20130202123101.59c2ee40@shibato> Date: Mon, 4 Feb 2013 09:20:52 -0800 X-Google-Sender-Auth: 442-9PvCc54sXwQbaX-GG7gNu7I Message-ID: Subject: Re: webGL in chrome From: Evan Martin To: "J.R. Oldroyd" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl2TdXS7S24Eh8ZzpXTI0Itfvyv841Y/bJE/HgWW7p54AB5AkRb73pOWhB3/b2RpXU0xs9N3XYhFPs1/1mJ/4kjrwLC3NlPt/LC/8fHbQWM6OwUgUT8AGzNxEPY4MoM245DynAhvQ7Bslto3W9i1o6Tytfp4YHmCPVFIdfcJjugh929D2qW1hDlnEvYQtOJZmBGMqFDMQmYiHzq1wxh/jMnPtNkUQ== 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, 04 Feb 2013 17:20:53 -0000 If it helps any, here's the code that produces that error, which is testing for a specific GL feature. const GLint kMinRenderbufferSize = 512; // GL says 1 pixel! GLint max_renderbuffer_size = 0; if (!QueryGLFeature( GL_MAX_RENDERBUFFER_SIZE, kMinRenderbufferSize, &max_renderbuffer_size)) { LOG(ERROR) << "ContextGroup::Initialize failed because maximum " << "renderbuffer size too small."; return false; } https://code.google.com/p/chromium/codesearch#chrome/src/gpu/command_buffer/service/context_group.cc&q=context_group.cc&sq= On Sat, Feb 2, 2013 at 9:31 AM, J.R. Oldroyd wrote: > Hi all, > > I am trying to enable webGL. > > Sys here is 9.1-REL, video is radeon. Chrome is chromium-24.0.1312.57. > > Chrome's chrome://gpu was reporting red "Unavailable. Hardware > acceleration disabled" for most of the items. The error log showed my > glx was < 1.3. glxinfo showed server was 1.2. > > Fixed that by adding WITH_NEW_XORG to /etc/make.conf and rebuilding > ports graphics/libdrm, graphics/dri, graphics/libGL, > x11-servers/xorg-server and x11-drivers/xf86-video-ati and now have > glx 1.4 for both client and server. In chrome://gpu all entries now > show green "Hardware acceleration enabled" except for Panel fitting. > > However, webGL pages still report that the browser does not support > webGL and there are repeated messages in the log: > > [81426:255882240:0201/221740:ERROR:context_group.cc(92)] : > ContextGroup::Initialize failed because maximum renderbuffer size too > small. > [81426:255882240:0201/221740:ERROR:gles2_cmd_decoder.cc(2012)] > : GpuScheduler::InitializeCommon failed because group failed to > initialize. > > In the chrome://flags settings, I have enabled "Override software > rendering list", "GPU compositing on all pages" and "Threaded > compositing". > > Is there something else that I need to recompile? Or some other flag > to set to increase this renderbuffer size? > > FWIW, all the graphics/mesa-demos programs run well. > > Thanks, > -jr > _______________________________________________ > 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" From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 18:56:05 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 21F38256 for ; Mon, 4 Feb 2013 18:56:05 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-ea0-f176.google.com (mail-ea0-f176.google.com [209.85.215.176]) by mx1.freebsd.org (Postfix) with ESMTP id B67BE659 for ; Mon, 4 Feb 2013 18:56:04 +0000 (UTC) Received: by mail-ea0-f176.google.com with SMTP id a13so3083200eaa.21 for ; Mon, 04 Feb 2013 10:55:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=aPh/razzctisCVJM37vIICkvy9gn4akNtx92n7Y119c=; b=dihkaO/WPC5JYHW62YFhAGlgAmcC4XRMkIXYTUbkn7AV3feNA82Q4nPkLopwkzmCTQ Vw8TBb0o4DQIDqTWj+06kl+oJWPFkjwlY4xCUE+MxFsiD/1kLnIcP3dRCDLfhUuNEUlv QerE+ekSKsBK/3MmpLqCOkPvkhQiON6hjLgVKH0dg0LaL9gUjiqREr2JNEt5oCTKM/ZO 7z+YEiBDkzoFaFrrr8FOaR3kzRLoK33hhuXFu6mkx2ciH8ufHRGmU0uv3lWCVF845zyf OhUZDIzipD4jrWOPJAmhOJ2afU9lxBnm/y0bn6dKRYsfuXWo0W96WF7UgtJtPdFxitkX hChQ== MIME-Version: 1.0 X-Received: by 10.14.219.5 with SMTP id l5mr75057916eep.7.1360004158653; Mon, 04 Feb 2013 10:55:58 -0800 (PST) Received: by 10.223.31.145 with HTTP; Mon, 4 Feb 2013 10:55:58 -0800 (PST) In-Reply-To: <20130203122913.6c0cf4e9@shibato> References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> Date: Mon, 4 Feb 2013 20:55:58 +0200 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 From: George Liaskos To: "J.R. Oldroyd" Content-Type: text/plain; charset=UTF-8 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, 04 Feb 2013 18:56:05 -0000 > I think the problem may be related to > files/patch-ui__surface__transport_dib_linux.cc which replaces the > immediate removal of the shm after attaching to it with removal in > the destructor iff we're the last who is attached to it. > > The comment states: > // On BSD we can't access the shared memory after is marked for > deletion. > but this is not true if kern.ipc.shm_allow_removed=1 which we are told > to set in the pkg-message. The problem is definitely in this patch, if kern.ipc.shm_allow_removed is set then the patch is not needed at all. The issue here is that the sysctl is not set by default and we must / should support the default configuration. I don't really know how to solve correctly this issue, TransportDIBs are created from a static function and the shm keys are cached. Simply removing the key in the destructor is not correct because there are other TransportDIB instances which use the same key. ... and even if you handle the removal gracefully, what happens when the process crashes? More leaks, that's why all other platforms allow the removal immediately. Maybe we are correct according to the Posix spec but now i understand why almost no one follows this specific behavior. [1] http://src.chromium.org/viewvc/chrome/trunk/src/ui/surface/transport_dib_linux.cc?revision=167669&content-type=text%2Fplain From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 22:08:19 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30D4F7EF for ; Mon, 4 Feb 2013 22:08:19 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-02-ewr.mailhop.org (mho-04-ewr.mailhop.org [204.13.248.74]) by mx1.freebsd.org (Postfix) with ESMTP id 01ABE34F for ; Mon, 4 Feb 2013 22:08:18 +0000 (UTC) Received: from pool-151-203-245-187.bos.east.verizon.net ([151.203.245.187] helo=homobox.opal.com) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U2UD3-000PBx-U5; Mon, 04 Feb 2013 22:08:18 +0000 Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:4:221:63ff:fe5a:c9a7]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r14M8EsA086865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 4 Feb 2013 17:08:14 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 151.203.245.187 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+8Sf0Xa1oFb/4k32vQKxhz Date: Mon, 4 Feb 2013 17:08:02 -0500 From: "J.R. Oldroyd" To: George Liaskos Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 Message-ID: <20130204170802.3ed0ac23@shibato> In-Reply-To: References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/D50Q57cyMqMrZiPMK3ZD4P8"; protocol="application/pgp-signature" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [IPv6:2001:470:8cb8:4::1]); Mon, 04 Feb 2013 17:08:14 -0500 (EST) X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, OPAL_URI_COUNT_5_9, RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com 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, 04 Feb 2013 22:08:19 -0000 --Sig_/D50Q57cyMqMrZiPMK3ZD4P8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 4 Feb 2013 20:55:58 +0200 George Liaskos wrote: > > > I think the problem may be related to > > files/patch-ui__surface__transport_dib_linux.cc which replaces the > > immediate removal of the shm after attaching to it with removal in > > the destructor iff we're the last who is attached to it. > > > > The comment states: > > // On BSD we can't access the shared memory after is marked for > > deletion. > > but this is not true if kern.ipc.shm_allow_removed=3D1 which we are told > > to set in the pkg-message. >=20 > The problem is definitely in this patch, if kern.ipc.shm_allow_removed > is set then the patch is not needed at all. > The issue here is that the sysctl is not set by default and we must / > should support the default configuration. >=20 > I don't really know how to solve correctly this issue, TransportDIBs > are created from a static function and the shm keys are cached. > Simply removing the key in the destructor is not correct because there > are other TransportDIB instances which use the same key. >=20 > ... and even if you handle the removal gracefully, what happens when > the process crashes? More leaks, that's why all other platforms allow > the removal immediately. >=20 > Maybe we are correct according to the Posix spec but now i understand > why almost no one follows this specific behavior. >=20 >=20 > [1] http://src.chromium.org/viewvc/chrome/trunk/src/ui/surface/transport_= dib_linux.cc?revision=3D167669&content-type=3Dtext%2Fplain Hey George, I saw you were the submitter of this patch, so thanks for chiming in. I can say that I've run without the patch for about 36-48 hours now and the problem has not recurred. So those wanting a simple fix can simply remove the patch, recompile chrome, set kern.ipc.shm_allow_removed=3D1 and run. Since the patch breaks things, I think it needs to be replaced. A simple fix would be to remove the patch and add a wrapper sh script that checks if the sysctl is set and prints a message if not. As for a proper fix, I haven't really studied that code in detail. Some possible thoughts. I am not sure what is using this shm region... separate processes or separate threads? Could the shm perhaps be replaced by something else, such as a malloc'd region accessed through a global variable? If not, is the removal code in the right place in the destructor; should it perhaps be in the TransportDIB::Detach method instead, or somewhere else? Do we know why it is not being executed - is this due to the removal code not being reached or is it due to something crashing? If something is crashing (and we can't fix that problem), can we trap that event and remove the shm there? -jr --Sig_/D50Q57cyMqMrZiPMK3ZD4P8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEQMU0ACgkQls33urr0k4n64wCfa4jL/8deXRrIWRNJZJRFKRgS aw0AoKeR7jrpk6p0+3ez7Yrg2r8AXGXw =ZxoY -----END PGP SIGNATURE----- --Sig_/D50Q57cyMqMrZiPMK3ZD4P8-- From owner-freebsd-chromium@FreeBSD.ORG Mon Feb 4 22:31:12 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5AB0177 for ; Mon, 4 Feb 2013 22:31:12 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by mx1.freebsd.org (Postfix) with ESMTP id 1B862687 for ; Mon, 4 Feb 2013 22:31:11 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id l10so7175676oag.16 for ; Mon, 04 Feb 2013 14:31:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=By+CeDhqEKehA0Wxs6GbT2xzGHD9Id5u0YuFzzJi4tw=; b=L1BxXk1IFj4GiXrmUi2p5post35U1C0XHVfsiub1ouEScAN3lMFeR0y8A3mBDK2jcq p7IFqnIVDqt3W4bHH6zJMxGIIxa+nEg7GtFPIt8/YHxyYQMpnHjZjX7Na0H4hbcxfbLV Iyo/+TvDumDAlEjVWBSePD4WsZFMQgLiKbkNzocRzzwE5Kgvu41vQgKll7NB/E94MzSO k8ZUlH0DyOh5J6gZnIS7w3n75fMG8IZbElppdu1i4t3JAX8qRve0PjLlRKwmr5Orkwco ZmYlywMJ1nX2rr+6Upa2ESQFFCuIWMoNDwF7lK+VLnKcZlxkcY/vBZa/rlo31TP+5L6R JNNA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=By+CeDhqEKehA0Wxs6GbT2xzGHD9Id5u0YuFzzJi4tw=; b=iMjxEMX+ohstvcC0p48aF4esTKLQJDwwpYiJOTbdWHwALvDYih1fxVD7t9FBrWgYx2 f3Xf63ooxiCzRhOEp2hE4LmwciM9SNo+8dwKYpGwIiSTqbfDIMEMQ7yPUucmyYnpHcKS oAaSTji2ETPEG3NUCLWNa4ijXb8/HW0Jyludk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=By+CeDhqEKehA0Wxs6GbT2xzGHD9Id5u0YuFzzJi4tw=; b=U0WLgjPiZ8ra75nnL3Sj+rM74tlipy3E0ZSWJuZXZie6GH+b/bBZVDq4BFprxw8T5z SF4LBQL+nmagt871F7GUVKQoWDkknZUJ+ER25UKvujHDJsxo1vFFHl/ZCchlcaSJNzgA qnoDZHejMixpnInYELBZj2QMD3PaZskVqxPxnqlAR9lq8FcjURR1xK+F25Tz4reiZewC r/LCsLZ/avL8wLeNrjmxmNcwJWsYc6DDmfTfgGVvD3DrWjYGELqUVvpQgwVZZ31vNVM2 wUHSi12J27buGJkvfhk7JOjvs26D9Tvh/zIz5kdPCAiK8hrWf8bJbs9niQAl58YwrCW+ o8qw== MIME-Version: 1.0 X-Received: by 10.60.7.167 with SMTP id k7mr18449581oea.20.1360017065047; Mon, 04 Feb 2013 14:31:05 -0800 (PST) Sender: evanm@google.com Received: by 10.76.72.3 with HTTP; Mon, 4 Feb 2013 14:31:04 -0800 (PST) In-Reply-To: <20130204170802.3ed0ac23@shibato> References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> Date: Mon, 4 Feb 2013 14:31:04 -0800 X-Google-Sender-Auth: 8-M9YpXWYn1sLHpsgo7kJZHFaTQ Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 From: Evan Martin To: "J.R. Oldroyd" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkHXUtysr+ZniuiL6+tmWXugMJkG8Zbjcl5FTIvTZNJHqaqOTOXUkCPcx2qRMX7BbUCiyhh9AXAEuhMkgqu+5vVKWvkU93f89k710MAHCJSPX8a8miMVXJ7TWzZxNWOP9x0zd8SP3bbTe9vqZXsK3QgC5AD+pfDubkNKbsXO/TdE8Gzc1fxoXWB36jMSkK+86qz+t7K+aa3jYZAs1pvo+f7ivuYlw== 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, 04 Feb 2013 22:31:12 -0000 I am the author of some of the related code, here's a brief explanation. One process ("per tab") runs WebKit, which has no connection to X so that a WebKit exploit won't give an attacker direct access to your mouse/keyboard. It does all of the drawing of web page pixels into a buffer. This buffer is then passed to the parent browser process, which has a connection to X, and that process passes the buffer along to the X server. So there are three separate processes interacting with these pixels -- WebKit, the browser, and X. Using shared memory instead of mallocs allows us to pass these pixels between processes without making copies (which are large enough to be slow -- imagine a large video writing out a screen's worth of pixels at 24fps). It's hard to pin down exactly where to free these buffers because the whole reason they exist is to allow multiple processes to access them asynchronously. Also, any of these processes can die and you don't want them leaking memory after they die. A more ideal API would allow you to ref-count this memory, so when all the involved processes are gone it would just free itself. The kernel toggle effectively allows this sort of ref-counting. Unfortunately, part of the reason this area is so complicated is that the X APIs for shared memory require the SYSV shmat() interface, rather than the more convenient BSD-derived mmap() interface (which is what the rest of Chrome uses when it needs shared memory for other purposes). On Mon, Feb 4, 2013 at 2:08 PM, J.R. Oldroyd wrote: > On Mon, 4 Feb 2013 20:55:58 +0200 George Liaskos > wrote: >> >> > I think the problem may be related to >> > files/patch-ui__surface__transport_dib_linux.cc which replaces the >> > immediate removal of the shm after attaching to it with removal in >> > the destructor iff we're the last who is attached to it. >> > >> > The comment states: >> > // On BSD we can't access the shared memory after is marked for >> > deletion. >> > but this is not true if kern.ipc.shm_allow_removed=1 which we are told >> > to set in the pkg-message. >> >> The problem is definitely in this patch, if kern.ipc.shm_allow_removed >> is set then the patch is not needed at all. >> The issue here is that the sysctl is not set by default and we must / >> should support the default configuration. >> >> I don't really know how to solve correctly this issue, TransportDIBs >> are created from a static function and the shm keys are cached. >> Simply removing the key in the destructor is not correct because there >> are other TransportDIB instances which use the same key. >> >> ... and even if you handle the removal gracefully, what happens when >> the process crashes? More leaks, that's why all other platforms allow >> the removal immediately. >> >> Maybe we are correct according to the Posix spec but now i understand >> why almost no one follows this specific behavior. >> >> >> [1] http://src.chromium.org/viewvc/chrome/trunk/src/ui/surface/transport_dib_linux.cc?revision=167669&content-type=text%2Fplain > > Hey George, > > I saw you were the submitter of this patch, so thanks for chiming in. > > I can say that I've run without the patch for about 36-48 hours now > and the problem has not recurred. So those wanting a simple fix can > simply remove the patch, recompile chrome, set > kern.ipc.shm_allow_removed=1 > and run. > > Since the patch breaks things, I think it needs to be replaced. A > simple fix would be to remove the patch and add a wrapper sh script > that checks if the sysctl is set and prints a message if not. > > As for a proper fix, I haven't really studied that code in detail. > Some possible thoughts. I am not sure what is using this shm > region... separate processes or separate threads? Could the shm > perhaps be replaced by something else, such as a malloc'd region > accessed through a global variable? If not, is the removal code > in the right place in the destructor; should it perhaps be in the > TransportDIB::Detach method instead, or somewhere else? Do we know > why it is not being executed - is this due to the removal code not > being reached or is it due to something crashing? If something is > crashing (and we can't fix that problem), can we trap that event and > remove the shm there? > > -jr From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 00:21:07 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5E771E3A for ; Tue, 5 Feb 2013 00:21:07 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by mx1.freebsd.org (Postfix) with ESMTP id 254EEA9F for ; Tue, 5 Feb 2013 00:21:06 +0000 (UTC) Received: by mail-qa0-f51.google.com with SMTP id cr7so1565816qab.17 for ; Mon, 04 Feb 2013 16:21:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=4NHM+sxObc6E6RkdNZzGK1krbKLsXd+1aDNl5Y7l8Gc=; b=Aslc7pxcna2jIkbt4pZcJjSkHLrAkMxXrnT6KUHCRZ+pMTriT65q61bFyuwdVAKjaA T4bBEzTlIX/c2nu7/WpjyBdg2Pi3YQEIM1SGLavI566Z7gfbiMJ3VYe6uOoF7RuovXvI VONWw5xlZtkVshHhA8HL5PRWBnnEKn9rZYzKPXnqOozlsMRcX/wbt5IjXs2D4VTvqi2b RVyXqzI6Dd66cb2+VExZVSRQOROxDloZyDwOqeACaK7J04WdXL4a6p6Xz17Kbne64Ar7 yHp+ockKbTUobHzHqfYmzIBaDpUmBNiwcndOLX9+CFLANsljlteT+1AXRC7YUesP2t1D QzYQ== MIME-Version: 1.0 X-Received: by 10.224.100.130 with SMTP id y2mr18947621qan.40.1360023275135; Mon, 04 Feb 2013 16:14:35 -0800 (PST) Received: by 10.49.74.10 with HTTP; Mon, 4 Feb 2013 16:14:34 -0800 (PST) X-Originating-IP: [203.99.129.1] In-Reply-To: References: Date: Tue, 5 Feb 2013 13:14:34 +1300 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 From: Jonathan Chen To: freebsd-chromium@freebsd.org X-Gm-Message-State: ALoCoQkjX91YJKcB552zyRfrnCNyAXZyD36IV/gHWU1KGOMXn4GTDM6AqMHlwWkVtA/DY2DZ/SrJ Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 05 Feb 2013 00:21:07 -0000 On 1 February 2013 10:56, Jonathan Chen wrote: > Hi, > > I've just installed the latest chromium-24.0.1312.57; and it appears to > suffer from the same IPC memory leakage as the version just before it. When > no more IPC shared memory can be allocated, chromium will only display a > blank page. Loading pages full of javascript will hurry this behaviour. > I've tracked the leakage to the patch-file: patch-ui__surface__transport_dib_linux.cc. Removing this patch file appears to have resolved the IPC shared-mem leakage. I'll file a PR for this. Cheers. -- Jonathan Chen From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 00:31:26 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F39E2F11 for ; Tue, 5 Feb 2013 00:31:25 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by mx1.freebsd.org (Postfix) with ESMTP id 92588B08 for ; Tue, 5 Feb 2013 00:31:25 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id g10so1549280qah.18 for ; Mon, 04 Feb 2013 16:31:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=pUK8Ar1f2j4SPkQOsVNaNmxDQ9L/lJDiwmxrUpl67+w=; b=NfrGMNZpyPUu6Y/IacB5X+Di0Vhffv21VO58TeFkM19KbUL7jrNLrN23g8Fpw4wvcy fs2oWAd2xgbE2MI5cyzzvLeYM206YTg0FjvoRzbA/37gfBGpYcjFwnFdxLkP6pK2lI+j 4QNtuux63pBypH6KFVY3RuAqTfgCWGzK3XI1kZHGReDkeWlS3ds1sZxyMqY/PDMJk4bJ dipsmiQAO/57aTMa8oNzANEZV40V/6w/BVOZCcKKHq/5peOlVDn9ptgQxIr5omcXV57r n/7/VEWKqj3XnR6k8X83B7ueZXmB4+xZe7GRG5Phu33zaVwAg60NSzzmFZnDJJhQwNnS HEDQ== MIME-Version: 1.0 X-Received: by 10.224.101.74 with SMTP id b10mr18989677qao.0.1360024278473; Mon, 04 Feb 2013 16:31:18 -0800 (PST) Received: by 10.49.74.10 with HTTP; Mon, 4 Feb 2013 16:31:18 -0800 (PST) X-Originating-IP: [203.99.129.1] In-Reply-To: References: Date: Tue, 5 Feb 2013 13:31:18 +1300 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 From: Jonathan Chen To: freebsd-chromium@freebsd.org X-Gm-Message-State: ALoCoQkBcVdKp/cg3yUD/4weY15+AiyZSn0OVq4wYOYbkRkehpRoM9xrqE3FXAanLEQaVtn5jXSF Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 05 Feb 2013 00:31:26 -0000 On 5 February 2013 13:14, Jonathan Chen wrote: > > I've tracked the leakage to the patch-file: > patch-ui__surface__transport_dib_linux.cc. Removing this patch file appears > to have resolved the IPC shared-mem leakage. I'll file a PR for this. > > Oops. I see that other people have found the same fix as I have. Anyway, the PR has been filed: http://www.freebsd.org/cgi/query-pr.cgi?pr=175850 -- Jonathan Chen From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 02:27:52 2013 Return-Path: Delivered-To: freebsd-chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C0072F16; Tue, 5 Feb 2013 02:27:52 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8D402F14; Tue, 5 Feb 2013 02:27:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r152Rqwl014183; Tue, 5 Feb 2013 02:27:52 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r152Rqpj014179; Tue, 5 Feb 2013 02:27:52 GMT (envelope-from edwin) Date: Tue, 5 Feb 2013 02:27:52 GMT Message-Id: <201302050227.r152Rqpj014179@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-chromium@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/175850: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 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: Tue, 05 Feb 2013 02:27:52 -0000 Synopsis: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-chromium Responsible-Changed-By: edwin Responsible-Changed-When: Tue Feb 5 02:27:52 UTC 2013 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=175850 From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 03:09:26 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BC59E1EC for ; Tue, 5 Feb 2013 03:09:26 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by mx1.freebsd.org (Postfix) with ESMTP id 478881B6 for ; Tue, 5 Feb 2013 03:09:26 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id q12so7273075lbc.11 for ; Mon, 04 Feb 2013 19:09:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=jtKiXS2DntpPMsxDFUnd74bYFusVPByhsdyn4vEw5lM=; b=ZjZNkJpBoRP4SVoM2523GRjUpdMsrxtQs51rUD/zwGMUFxkbGUNlSzl40kigtPpd1G RFMbdgi5ZQQwMvgQQne+L1A53jfIGY+/kIEO1GUU67rpyxAmvMxm1RPc9S+wCy8rq4Sc x09BaBpL4YCTzaQg0brGyF3bKTXYqoWf0ymeM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=jtKiXS2DntpPMsxDFUnd74bYFusVPByhsdyn4vEw5lM=; b=MbpxI22X2YtVa6meAB+vKSanqlU+B4+lOcgClmU6Dp2rdWbDLd9ww5gXcTHlfw7h8z BvBmFxT8Savqh+NHGUDfOJyqE6zoUQ62cuG/4QtDfnEhEt/7bAHAd3sIDjuDv6JXqezP rlA7WXtJk7xVdBPCRgv/jCdXFMpx8Sl7yRjOf14d/p5is+arLOulgQzWDDyoP8uxwuAF iDxDEXRlpRPACNNS0DxybRXyhdLYnGEVBusPPEbR2ZzGTZbsA/tDJWQ9u0vnSggKCJ+b vnXaeGZlhscjenZiP3qBKmGzMPyyqDrHILEwWsvagkRTsMuze1guynoGRE7A05l2Vrwb oivQ== X-Received: by 10.152.147.103 with SMTP id tj7mr21488056lab.54.1360033765160; Mon, 04 Feb 2013 19:09:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.91.164 with HTTP; Mon, 4 Feb 2013 19:08:55 -0800 (PST) In-Reply-To: <20130204170802.3ed0ac23@shibato> References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> From: Eitan Adler Date: Mon, 4 Feb 2013 22:08:55 -0500 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 To: "J.R. Oldroyd" Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnI5nq3S8mIsarwU0GdP/PWT9HXgyK4Rcr47fQp+yK8isV67Ygdw3jzXyWWHUKT/vQSRwrP 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: Tue, 05 Feb 2013 03:09:26 -0000 On 4 February 2013 17:08, J.R. Oldroyd wrote: > I can say that I've run without the patch for about 36-48 hours now > and the problem has not recurred. So those wanting a simple fix can > simply remove the patch, recompile chrome, set > kern.ipc.shm_allow_removed=1 > and run. I have this set and it does *not* fix the problem for me. -- Eitan Adler From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 04:34:51 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 DA22C47D for ; Tue, 5 Feb 2013 04:34:51 +0000 (UTC) (envelope-from dnikolaev@mega-net.ru) Received: from mail.mega-net.ru (mail.mega-net.ru [91.217.137.1]) by mx1.freebsd.org (Postfix) with SMTP id ED37568F for ; Tue, 5 Feb 2013 04:34:50 +0000 (UTC) Received: (qmail 83161 invoked from network); 5 Feb 2013 08:34:48 +0400 Received: from unknown [172.16.10.39] (HELO virus.mega-net.ru) by mail.mega-net.ru with ESMTP; 5 Feb 2013 08:34:48 +0400 Message-ID: <51108BE7.8000804@mega-net.ru> Date: Tue, 05 Feb 2013 08:34:47 +0400 From: "Dmitry S. Nikolaev" Organization: OOO Meganet-2003 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130114 Thunderbird/17.0.2 MIME-Version: 1.0 To: Eitan Adler Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dnikolaev@mega-net.ru List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 04:34:51 -0000 Hi all. I have the same problem with chrome. Eitan Adler, you need to read J.R. Oldroyd message. You must set sysctl, than remove patch files/patch-ui__surface__transport_dib_linux.cc, than recompile chrome. I will try this fix today, hope it will work. --- With best regards, Dmitry S. Nikolaev On 05.02.2013 07:08, Eitan Adler wrote: > On 4 February 2013 17:08, J.R. Oldroyd wrote: >> I can say that I've run without the patch for about 36-48 hours now >> and the problem has not recurred. So those wanting a simple fix can >> simply remove the patch, recompile chrome, set >> kern.ipc.shm_allow_removed=1 >> and run. > I have this set and it does *not* fix the problem for me. > From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 04:39:19 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 197E649E for ; Tue, 5 Feb 2013 04:39:19 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by mx1.freebsd.org (Postfix) with ESMTP id 6865069C for ; Tue, 5 Feb 2013 04:39:17 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id go11so7135420lbb.8 for ; Mon, 04 Feb 2013 20:39:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=LJBWZl0nKRq3tdLvgKqAIqHL81F51ycSEA1f5LdCZ20=; b=uVyxUCbEAusozQBxu01PuzTQ/E+1UZpVtAFrDDr7MDdTWdmhDjk66RB1GaxD0cj/aT k3Nvh5DvUhJQetW3Uh1iIYZ5sxzNUPnc9F5FozWA0QYiIBex9jqpI3NtaNx3cNo2/b4t Zk3XCgU5gMkr+W2EbkYvO/nkxHDp2qAma2PJQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=LJBWZl0nKRq3tdLvgKqAIqHL81F51ycSEA1f5LdCZ20=; b=Fe/BG0q1R6x31ZKhf1elo001d8jh8MgB7ebgbteMR7kp2cKOyghiX78HoHnID+lmTQ BiYUDoMuZYWooyNGBcL/YaG/TQjKDR/QyjEqDA4rl4TKdQhzXCPHgxIPyKqIPEVFp5pc vaV8nNsFW7JYQzB2tSh+abwPqs7awip+br+bMRZ6LWFBjFjqR4XHc5HudN7gHUoGcj5A AGMjRT4b0qzpIHt39q5f2QSN8XaTV28/Fj2hqPbeAyPGE6ER8dQ8W2fnf+lmyrP4jo92 jLSlrW6GLPFwnNthXZJXheKvA6SlPlmHeHmARGSpoyFnd4fivoCIwp5OQxPQjpJ7RuLv 2JSA== X-Received: by 10.152.108.195 with SMTP id hm3mr21551540lab.17.1360039156893; Mon, 04 Feb 2013 20:39:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.91.164 with HTTP; Mon, 4 Feb 2013 20:38:46 -0800 (PST) In-Reply-To: <51108BE7.8000804@mega-net.ru> References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> <51108BE7.8000804@mega-net.ru> From: Eitan Adler Date: Mon, 4 Feb 2013 23:38:46 -0500 Message-ID: Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 To: dnikolaev@mega-net.ru Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmIk2rPeUr+xXR3gCle87GkhEJPdsRrfK9xIhb+s8OdArVYHlbvKlVIPabsj4wq0EkOFz+8 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: Tue, 05 Feb 2013 04:39:19 -0000 On 4 February 2013 23:34, Dmitry S. Nikolaev wrote: > Hi all. > > I have the same problem with chrome. > > Eitan Adler, you need to read J.R. Oldroyd message. > You must set sysctl, than remove patch > files/patch-ui__surface__transport_dib_linux.cc, than recompile chrome. Ack. I misread. I read as *either* remove patch or set sysctl. I shall fix. -- Eitan Adler From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 05:30:01 2013 Return-Path: Delivered-To: freebsd-chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B3EC59C9 for ; Tue, 5 Feb 2013 05:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A68497E7 for ; Tue, 5 Feb 2013 05:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r155U1cT047656 for ; Tue, 5 Feb 2013 05:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r155U1Tk047655; Tue, 5 Feb 2013 05:30:01 GMT (envelope-from gnats) Date: Tue, 5 Feb 2013 05:30:01 GMT Message-Id: <201302050530.r155U1Tk047655@freefall.freebsd.org> To: freebsd-chromium@FreeBSD.org Cc: From: Jonathan Chen Subject: Re: ports/175850: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Jonathan Chen List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 05:30:01 -0000 The following reply was made to PR ports/175850; it has been noted by GNATS. From: Jonathan Chen To: bug-followup@FreeBSD.org, jonc@chen.org.nz Cc: Subject: Re: ports/175850: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 Date: Tue, 5 Feb 2013 18:28:47 +1300 --047d7bea3518dfe96a04d4f37b03 Content-Type: text/plain; charset=ISO-8859-1 Can be closed, as this was done in r311648 -- Jonathan Chen --047d7bea3518dfe96a04d4f37b03 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Can be closed, as this was done in=A0r311648
--
Jon= athan Chen <jonc@c= hen.org.nz>
--047d7bea3518dfe96a04d4f37b03-- From owner-freebsd-chromium@FreeBSD.ORG Tue Feb 5 11:10:55 2013 Return-Path: Delivered-To: freebsd-chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0E7F8A62; Tue, 5 Feb 2013 11:10:55 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id DC8A9E91; Tue, 5 Feb 2013 11:10:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r15BAsEG022068; Tue, 5 Feb 2013 11:10:54 GMT (envelope-from rene@freefall.freebsd.org) Received: (from rene@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r15BArI7022064; Tue, 5 Feb 2013 11:10:53 GMT (envelope-from rene) Date: Tue, 5 Feb 2013 11:10:53 GMT Message-Id: <201302051110.r15BArI7022064@freefall.freebsd.org> To: jonc@chen.org.nz, rene@FreeBSD.org, freebsd-chromium@FreeBSD.org From: rene@FreeBSD.org Subject: Re: ports/175850: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 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: Tue, 05 Feb 2013 11:10:55 -0000 Synopsis: Fix IPC shared memory leakage on www/chromium 24.0.1312.57 State-Changed-From-To: open->closed State-Changed-By: rene State-Changed-When: Tue Feb 5 11:10:18 UTC 2013 State-Changed-Why: Closed on submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=175850 From owner-freebsd-chromium@FreeBSD.ORG Fri Feb 8 09:36:04 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6F204DE3 for ; Fri, 8 Feb 2013 09:36:04 +0000 (UTC) (envelope-from h2+lists2011@fsfe.org) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.freebsd.org (Postfix) with ESMTP id 0BABF814 for ; Fri, 8 Feb 2013 09:36:01 +0000 (UTC) X-Envelope-From: h2+lists2011@fsfe.org X-Envelope-To: Received: from [192.168.3.80] (brln-4dbade15.pool.mediaWays.net [77.186.222.21]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id r189ZxSH011577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 8 Feb 2013 10:36:00 +0100 Message-ID: <5114C6FE.10200@fsfe.org> Date: Fri, 08 Feb 2013 10:35:58 +0100 From: Hannes MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Re: ports/175835: www/chromium no audio playing from Google Voice References: <201302041700.r14H0Ddw099176@freefall.freebsd.org> In-Reply-To: <201302041700.r14H0Ddw099176@freefall.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 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: Fri, 08 Feb 2013 09:36:04 -0000 On 04.02.2013 18:00, edwin@FreeBSD.org wrote: > Synopsis: www/chromium no audio playing from Google Voice > > Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-chromium > Responsible-Changed-By: edwin > Responsible-Changed-When: Mon Feb 4 17:00:13 UTC 2013 > Responsible-Changed-Why: > Over to maintainer (via the GNATS Auto Assign Tool) > > http://www.freebsd.org/cgi/query-pr.cgi?pr=175835 > _______________________________________________ > 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" > I have no audio on html5 as well. Best, Hannes From owner-freebsd-chromium@FreeBSD.ORG Fri Feb 8 10:00:58 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8CC0BA08 for ; Fri, 8 Feb 2013 10:00:58 +0000 (UTC) (envelope-from dnikolaev@mega-net.ru) Received: from mail.mega-net.ru (mail.mega-net.ru [91.217.137.1]) by mx1.freebsd.org (Postfix) with SMTP id BFE1B941 for ; Fri, 8 Feb 2013 10:00:57 +0000 (UTC) Received: (qmail 4363 invoked from network); 8 Feb 2013 14:00:49 +0400 Received: from unknown [172.16.10.39] (HELO virus.mega-net.ru) by mail.mega-net.ru with ESMTP; 8 Feb 2013 14:00:49 +0400 Message-ID: <5114CCD1.5050906@mega-net.ru> Date: Fri, 08 Feb 2013 14:00:49 +0400 From: "Dmitry S. Nikolaev" Organization: OOO Meganet-2003 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130206 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Re: IPC memory leakage on latest chromium-24.0.1312.57 References: <1563077977.10385807.1359749865202.JavaMail.root@k-state.edu> <20130203122913.6c0cf4e9@shibato> <20130204170802.3ed0ac23@shibato> <51108BE7.8000804@mega-net.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dnikolaev@mega-net.ru List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 10:00:58 -0000 Hi all. After last portsnap and portupgrade chrome work fine all day long, no blank pages and etc. - bug has gone. I set kern.ipc.shm_allow_removed=1 and compime chrome with all pacthes including patch-ui__surface__transport_dib_linux.cc. I`am running on FreeBSD 8.3-STABLE. With best regards, Dmitry S. Nikolaev On 05.02.2013 08:38, Eitan Adler wrote: > On 4 February 2013 23:34, Dmitry S. Nikolaev wrote: >> Hi all. >> >> I have the same problem with chrome. >> >> Eitan Adler, you need to read J.R. Oldroyd message. >> You must set sysctl, than remove patch >> files/patch-ui__surface__transport_dib_linux.cc, than recompile chrome. > Ack. I misread. I read as *either* remove patch or set sysctl. I shall fix. > From owner-freebsd-chromium@FreeBSD.ORG Sat Feb 9 07:24:59 2013 Return-Path: Delivered-To: freebsd-chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F38F5B5D; Sat, 9 Feb 2013 07:24:58 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B3DB6C33; Sat, 9 Feb 2013 07:24:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r197Owde092363; Sat, 9 Feb 2013 07:24:58 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r197Oww2092359; Sat, 9 Feb 2013 07:24:58 GMT (envelope-from linimon) Date: Sat, 9 Feb 2013 07:24:58 GMT Message-Id: <201302090724.r197Oww2092359@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-chromium@FreeBSD.org, chromium@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: ports/175835: www/chromium no audio playing from Google Voice 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: Sat, 09 Feb 2013 07:24:59 -0000 Synopsis: www/chromium no audio playing from Google Voice Responsible-Changed-From-To: freebsd-chromium->chromium Responsible-Changed-By: linimon Responsible-Changed-When: Sat Feb 9 07:24:47 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=175835 From owner-freebsd-chromium@FreeBSD.ORG Sat Feb 9 07:25:17 2013 Return-Path: Delivered-To: chromium@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ABB95B75; Sat, 9 Feb 2013 07:25:17 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD5CC36; Sat, 9 Feb 2013 07:25:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r197PHEV092403; Sat, 9 Feb 2013 07:25:17 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r197PHud092399; Sat, 9 Feb 2013 07:25:17 GMT (envelope-from linimon) Date: Sat, 9 Feb 2013 07:25:17 GMT Message-Id: <201302090725.r197PHud092399@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, chromium@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: ports/175972: www/chromium does not build with pulseaudio 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: Sat, 09 Feb 2013 07:25:17 -0000 Old Synopsis: chromium does not build with pulseaudio New Synopsis: www/chromium does not build with pulseaudio Responsible-Changed-From-To: freebsd-ports-bugs->chromium Responsible-Changed-By: linimon Responsible-Changed-When: Sat Feb 9 07:24:23 UTC 2013 Responsible-Changed-Why: Fix synopsis and assign. http://www.freebsd.org/cgi/query-pr.cgi?pr=175972