Closed Bug 1170568 Opened 9 years ago Closed 9 years ago

Animated personas do not work after restarting Firefox

Categories

(Firefox :: Untriaged, defect)

38 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 819190

People

(Reporter: u540525, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150525141253

Steps to reproduce:

1) Install the animated persona from this link: https://addons.mozilla.org/firefox/addon/derpy-hooves-animated/
2) Restart Firefox
3) The background is no longer animated

This was tested on a new Firefox profile and the problem happens 100% of the time. Tested on two computers (Windows 8.1).


Actual results:

The background image is no longer animated. The only way to solve this is by disabling and re-enabling it, or by using the workaround by sean50350 listed on this page: https://support.mozilla.org/questions/965834


Expected results:

I expect the personas to remain animated after reopening Firefox. The workaround listed on the Mozilla support page works for a while, but every now and then the settings get reset and I have to apply them again.
Because these type of personas hase been disabled in Firefox due to bad performance for the user.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
So what you're basically saying is that instead of adding something like a message to inform users that these kind of personas can have a negative performance impact, somebody ended up crippling a feature in a way that makes it work for once and not after re-opening a browser? Why are animated personas still a thing when it's disabled anyway?

I read through the bug reports that are related to this which I found through the link that you mentioned and checked my own system. I'm definitely not speaking for everyone when I say this, but in my case I don't care whether I waste a few hundred megabytes of RAM and some CPU cycles. The firefox.exe process uses 1% of my i7-3770k when its doing nothing and uses around 500MB of memory.

Instead of breaking a feature in order to improve performance it would have been preferable for those who have different priorities to be able to remain using said features. A simple warning about performance is more than enough...
You need to log in before you can comment on or make changes to this bug.