Date: Sun, 20 Jan 2019 17:54:32 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 234672] www/chromium: c++: error: unable to execute command: Segmentation fault (core dumped) Message-ID: <bug-234672-28929-limObTM6iE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234672-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-234672-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234672 --- Comment #12 from Bob Prohaska <fbsd@www.zefox.net> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234672-28929-limObTM6iE>