Date: Mon, 10 Aug 2015 17:58:05 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 201543] www/chromium: chrome processes stuck at 100% cpu Message-ID: <bug-201543-28929-kz5uwstws5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201543-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-201543-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=201543 --- Comment #16 from pete@nomadlogic.org --- I am running 10.2-RC2 via bhyve and I am currently unable to trigger this bug: [pwright@bsd0 ~]$ uname -ar FreeBSD bsd0.trp-srd.com 10.2-RC2 FreeBSD 10.2-RC2 #0 r286137: Fri Jul 31 17:54:39 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 [pwright@bsd0 ~]$ pkg info|grep chromium chromium-44.0.2403.107 Google web browser based on WebKit I suspect the fix that we are trying to get into 10.1 is working as expected in 10.2. -- 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-201543-28929-kz5uwstws5>