Re: [Bug 212812] www/chromium: tabs "hang" 10% of the time
Grzegorz Junka writes: > On 20/07/2018 19:28, bugzilla-nore...@freebsd.org wrote: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 >> >> --- Comment #81 from Jan Beich --- >> 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 ___ freebsd-chromium@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "freebsd-chromium-unsubscr...@freebsd.org"
Re: [Bug 212812] www/chromium: tabs "hang" 10% of the time
On 20/07/2018 19:28, bugzilla-nore...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 --- Comment #81 from Jan Beich --- 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-chromium@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "freebsd-chromium-unsubscr...@freebsd.org"
Re: [Bug 212812] www/chromium: tabs "hang" 10% of the time
On Mon, 2016-09-19 at 10:28 +, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812 > > bk...@cs.ucl.ac.uk changed: > It's not simple to fix because good hardware is required to do the debugging. Ideally > 64G of ram. Then I could have everything in tmpfs, +20Gb binary +20Gb that binary under debugger +whatever debugger might need more. Or > 32G just for debugging purpose, having project on ordinary FS. May be someone could give me an access to such an equipment? Also, I would love to have more distcc hosts to do what I'm about to finish now: GYP->GN migration, that would decrease the waiting time for me. And it would be much simpler to do component debugging with that GN build tool. Having 3 hosts now, compilation time is about 6 hours for me. I would very much appreciate any help regarding the computation power. signature.asc Description: This is a digitally signed message part
