Date: Sat, 03 Mar 2018 12:56:24 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 212812] www/chromium: tabs "hang" 10% of the time Message-ID: <bug-212812-28929-1nfbbBcQ1O@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212812-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-212812-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=3D212812 --- Comment #51 from Thomas Zander <riggs@FreeBSD.org> --- (In reply to Rob Belics from comment #49) The messages about GetIdleWakeupsPerSecond() not being implemented should n= ot be a problem (fingers crossed, though). Chromium continuously samples metri= cs of its processes. This one metric just can't be sampled on FreeBSD then. Bu= t it should not make tabs crash. For additional info on the topic, see https://bugs.chromium.org/p/chromium/issues/detail?id=3D120488 However, I just observed a tab crashing and the dreaded "Aw, snap!" being displayed, I noticed this one: [43273:506440448:0303/134803.387965:ERROR:socket_stream.cc(210)] Closing st= ream with result -101 --=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-212812-28929-1nfbbBcQ1O>