Date: Fri, 25 Dec 2015 16:20:54 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 203732] www/firefox: High CPU usage when playing HTML5 video Message-ID: <bug-203732-21738-7pQ7gik32X@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203732-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-203732-21738@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=203732 Arto Pekkanen <aksyom@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aksyom@gmail.com --- Comment #3 from Arto Pekkanen <aksyom@gmail.com> --- (In reply to Jan Beich from comment #1) I am another user of www/firefox who can verify that the stock alsa-plugins without BUFSZ_P2 causes www/firefox to use more than 100% CPU when playing videos. Anyway, the total effect of not having this bug fixed is that now FreeBSD users do not have a properly working, modern, full-featured browser. The reason for my claim is that the other full-featured browser would be www/chromium, but it is also buggy and unstable, since tabs often crash. There's also a bounty for fixing www/chromium, which I am trying to help fix as a non-professional, but nothing has been done to fix it thus far (see: https://github.com/gliaskos/freebsd-chromium/issues/40). As a sidenote: I am trying to get a core dump from crashing tabs in chromium, but have not been successful yet (because I am not a professional software developer). Because of the total effect this bug has on the few desktop users of FreeBSD, I would suggest creating a clone of alsa-plugins, let's call it alsa-plugins-gecko, in which the BUFSZ_P2 is forced on by default, and having www/firefox link against alsa-plugins-gecko until a proper solution is found. Creating a BUFZS_P2 clone of alsa-plugins would have no negative side effects, since only gecko ports would link against it. Later, when the actual issue has been resolved and when it can be proven that www/firefox works well with the stock alsa-plugins, this temporary workaround can be reverted. If we leave this issue as it is, me and other users of www/firefox are forced to do all kinds of extra work to get firefox working. PS. My solution was to simply compile and install alsa-plugins with BUFSZ_P2 option, which causes negative side effects in other apps. I will try compiling www/firefox with PULSEAUDIO and see how well that works. But I would prefer not having to depend on PULSEAUDIO, I consider it a cancer to be avoided. -- 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-203732-21738-7pQ7gik32X>