From owner-freebsd-chromium@freebsd.org Sun Jul 3 00:23:20 2016 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A7FAB81728 for ; Sun, 3 Jul 2016 00:23:20 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7B4A129B3 for ; Sun, 3 Jul 2016 00:23:20 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7A6A3B81726; Sun, 3 Jul 2016 00:23:20 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A084B81725 for ; Sun, 3 Jul 2016 00:23:20 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55A5929B2 for ; Sun, 3 Jul 2016 00:23:19 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1467505398288244.40473045015187; Sat, 2 Jul 2016 17:23:18 -0700 (PDT) Date: Sat, 02 Jul 2016 17:23:18 -0700 From: Matthew Macy To: "chromium" Message-ID: <155ae2351dc.d435e15355364.689950361019774764@nextbsd.org> Subject: chrome spends all its time calling open MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2016 00:23:20 -0000 While looking at other issues I tried running truss on chrome at startup and I discovered a certain rather dysfunctional behavior: lanecrash# grep "close(" chrome.log | wc 1317903 7905445 68502169 planecrash# wc chrome.log 1466068 8798135 78854285 chrome.log It repeatedly calls close on 1 up to ~128000. System calls aren't expensive per se, but if almost 95% of your system calls are close you're doing something quite wrong. -M