1044209 - Animated download progress bar in OS X Dock uses too much CPU, horrible UX

Status: RESOLVED WORKSFORME

(Core :: Widget: Cocoa, defect)

Description

[Daniel Ritz]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140716183446

Steps to reproduce:

Download a big file


Actual results:

The progress bar in the Dock causes high CPU usage (7% or so on 2009 MacBook Pro, 10.9.4).

The animation is bad because for a few reasons:
- CPU usage -> reduced battery run time
- After the download is finished, the CPU usage seems to stay at the same level until the Dock is restarted
  (need to confirm that one)
- UX is bad:
  - When the Dock is always visible, the animation drags the user's attention for no good reason. 
    Also it's sluggish.
  - When the Dock is in auto-hide mode, the CPU does not change at all, it just drains the battery


Expected results:

Remove the animation. A simple non-animated progress bar which updates only
every 1 or 2 seconds is enough, does not drag the users attention and is easier
on the battery.

Or give the user the possibility to disable the Dock progress bar.

Comment 1

[Vlad Bacia-Mociran [:VladB]]

I didn't managed to reproduce this issue on the latest release(43.0.4) nor the latest Nightly(46.0a1).

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160111030207

Can you please try to reproduce this on the latest release(43.0.4) and latest Nightly(46.0a1) and provide the results?
When doing this, you could create a new clean Firefox profile, or maybe test in safe mode, as some of this issues may be caused by third party installed addons or custom settings
(https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems).

Thank you,
Vlad

Comment 2

[Vlad Bacia-Mociran [:VladB]]

Hi,

Considering the fact that the reporter did not provide more informations on my request, I will mark this issue as Resolved - WFM.
If you can still reproduce this, feel free to reopen it and provide the requested information.

Thanks