Closed Bug 1146105 Opened 10 years ago Closed 8 years ago

high CPU usage with html5 on FreeBSD 10.1

Categories

(Core :: Audio/Video: Playback, defect)

Product:
Core
Component:
Audio/Video: Playback
Version:
31 Branch
Platform:
x86_64
FreeBSD
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mzs_47, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33 Build ID: 20150311144957 Steps to reproduce: I played video from youtube with html5 player and audio from soundcloud. I don't have flash installed. The machine is a two year old Core i7. [..] % uname -a FreeBSD freebsd64_10 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 [..] [..] pkg info firefox-esr firefox-esr-31.5.0,1 Name : firefox-esr Version : 31.5.0,1 Installed on : Sat Mar 14 19:22:57 IST 2015 Origin : www/firefox-esr Architecture : freebsd:10:x86:64 Prefix : /usr/local Categories : www ipv6 Licenses : Maintainer : gecko@FreeBSD.org WWW : http://www.mozilla.com/firefox Comment : Web browser based on the browser portion of Mozilla Options : [..] Actual results: Output from top command THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 66 20 0 704M 350M uwait 7 1:00 113.28% firefox Expected results: Midori(based on chromium) consumes around 15%(360p) and 24%(720p) for youtube. 100% is just too much.
See Also: → 1146104
See Also: → 970308
Component: Untriaged → Video/Audio
Product: Firefox → Core
We don't support HW accelerated h264 decoding on linux.
Component: Audio/Video → Audio/Video: Playback
(try Firefox 43 or later)
Feedback timeout.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Sorry guys, I did not check this earlier. Yes the CPU utilization is around ~32 each for Xorg and Seamonkey, could not try with firefox-esr as it was not loading properly. Thanks for updating ports and fixing this.
You need to log in before you can comment on or make changes to this bug.