From owner-freebsd-chromium@freebsd.org Sun Jan 20 17:54:34 2019 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47D60149C52A for ; Sun, 20 Jan 2019 17:54:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.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 D799071B85 for ; Sun, 20 Jan 2019 17:54:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9837A149C528; Sun, 20 Jan 2019 17:54:33 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86BF8149C526 for ; Sun, 20 Jan 2019 17:54:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25DC871B7C for ; Sun, 20 Jan 2019 17:54:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 673271D071 for ; Sun, 20 Jan 2019 17:54:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0KHsWIH099591 for ; Sun, 20 Jan 2019 17:54:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0KHsWDU099590 for chromium@FreeBSD.org; Sun, 20 Jan 2019 17:54:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 234672] www/chromium: c++: error: unable to execute command: Segmentation fault (core dumped) Date: Sun, 20 Jan 2019 17:54:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fbsd@www.zefox.net X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2019 17:54:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234672 --- Comment #12 from Bob Prohaska --- Attempts to work through the crashes by cleaning up and restarting buildworld have so far proved ineffective. Clang still stops with signal 11's or internal higher-numbered (e.g., 254) errors fairly regularly. Oddly enough, chromium (the browser) seems to work alright, if slowly, and no errors apart from clang are evident. The only complaint other than from clang occurs when starting chromium: [83827:1218383872:0120/075747.927080:ERROR:gpu_process_transport_factory.cc= (1016)] Lost UI shared context. [84111:1339003392:0120/075753.574384:ERROR:command_buffer_proxy_impl.cc(113= )] ContextResult::kFatalFailure: Shared memory handle is not valid Still, chromium does not crash. In any case, this does not seem to be a chromium issue so this particular bug report might as well be closed. Thanks for everyone's attention, bob prohaska --=20 You are receiving this mail because: You are the assignee for the bug.=