Date: Fri, 10 Aug 2018 16:58:22 +0200 From: Jan Beich <jbeich@FreeBSD.org> To: Grzegorz Junka <list1@gjunka.com> Cc: freebsd-chromium@freebsd.org Subject: Re: [Bug 212812] www/chromium: tabs "hang" 10% of the time Message-ID: <pnyq-1d69-wny@FreeBSD.org> References: <bug-212812-28929@https.bugs.freebsd.org/bugzilla/> <bug-212812-28929-C4t7jY6KIS@https.bugs.freebsd.org/bugzilla/> <1532547c-74a1-bb50-8e88-b43e13af7b90@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Grzegorz Junka <list1@gjunka.com> writes: > On 20/07/2018 19:28, bugzilla-noreply@freebsd.org wrote: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 >> >> --- Comment #81 from Jan Beich <jbeich@FreeBSD.org> --- >> Can someone check if the patch in bug 181741 has any effect? Maybe some hangs >> (e.g., cache on high latency storage but not GPU driver bugs) are due to IPC. >> >> Just a wild guess. >> > Do you know in which version of Chrome it ended up? FreeBSD 12.0 or try -CURRENT. Only kernel matters, you can postpone upgrading base/userland and ports/packages as long as the kernel config contains COMPAT_FREEBSD10 and/or COMPAT_FREEBSD11. Background: An innocuous change in Firefox 63 made tabs hang on *every* page, so a Mozilla engineer that maintaines IPC code got curious and tracked it down to a kernel bug. As Firefox IPC is based on old Chromium IPC I made a guess that Chromium may suffer from a similar issue but whether it's related to the notorious hanging tabs is unknown. https://bugzilla.mozilla.org/show_bug.cgi?id=1475970#c7 https://bugzilla.mozilla.org/show_bug.cgi?id=1476130
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?pnyq-1d69-wny>