Closed Bug 859254 Opened 11 years ago Closed 11 years ago

Firefox 20 plays Flash content slower than older versions

Categories

(Core Graveyard :: Plug-ins, defect)

20 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: macster_smart, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

I went to this website called http://chaturbate.com/ and find out that all Firefox versions starting with version 17, 18 ,19 and now 20 play the Flash content slower than version 16.0.2. 


Actual results:

Basically every adult webcam is rendered by Flash, the Flash content can be resized. Started with version 17 up to version 20 all webcams rendered by Flash are rendering much slower than in Firefox version 16.0.2.
This is a bug that initially started with version 17 and just perpetuates through all other versions till version 20.
I have an 10 years old computer CPU Athnlon XP 2600+ 2.08 GHz single core only SSE 1 support MMX and 3DNow! and a GPU Radeon 9600 128 MB DX 9 card, system RAM 1.25 GB, Win XP SP3 clean install with no other updates other than a DirectX 2008 redistributable update.


Expected results:

It should have worked like version 16.0.2 because now I can't update my Firefox browser since is working so slow in that particular webpage.
Try with a new profile, please: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Don't import anything, disable plugins (not Flash of course).
Flags: needinfo?(macster_smart)
All others plugins are already disable since that's how I use Firefox for many years now, only Flash plugin is active. 
I don't see how using a new profile would help since I installed every new version 17, 18 , 19 and 20 the I had to uninstall them and switch back to version 16.0.2 which doesn't have the above mentioned bug.
When I uninstalled every version I checked to remove all customizations cookies bookmarks etc.
And when I updated to a new version I used the update feature and I even downloaded full versions from Mozilla website just to discover the same result.
Flags: needinfo?(macster_smart)
Please try with a new profile like Loic mentions.  Profile data is separate from the application executable.
Component: Untriaged → Plug-ins
Product: Firefox → Core
Don't you get it that when I installed a new version I did it by uninstalling the old one and removing all profile data by checking this option "Remove my Firefox personal data and customizations"
Do you think you are talking to a newbie or something ?
And I've just uninstalled Firefox 20 like I did with versions 19, 18 and 17 that have this bug and switched back to version 16.0.2 which works very well for me. I'm not gonna install version 20 again just to try it with a new profile since the profile was already new when I installed it, this is just stupid.
Maybe I will install version 21 when it comes out just to check again if this bug was fixed, if not I will uninstall it and switch back again to version 16.0.2.
(In reply to macster_smart from comment #5)
> And I've just uninstalled Firefox 20 like I did with versions 19, 18 and 17
> that have this bug and switched back to version 16.0.2 which works very well
> for me. I'm not gonna install version 20 again just to try it with a new
> profile since the profile was already new when I installed it, this is just
> stupid.
> Maybe I will install version 21 when it comes out just to check again if
> this bug was fixed, if not I will uninstall it and switch back again to
> version 16.0.2.

So use the tool mozregression to find a possible regression range since Firefox 17: 
http://harthur.github.io/mozregression/

FF17 nightlies started in July 2012: mozregression --good=2012-07-01
Flags: needinfo?(macster_smart)
Well I'm not quite comfortable in playing around with alpha and beta builds but I can say that version 17 as a whole was way slower than version 16 not just in the Flash area. I've just checked the Release notes bug list here:
http://www.mozilla.org/en-US/firefox/17.0/releasenotes/buglist.html
and there are some bugs related to Flash that might have had modified the way Firefox handles Flash content that might have caused this bug to occur:
- Repainting issue of Flash content when scrolling with Flash Player
https://bugzilla.mozilla.org/show_bug.cgi?id=762948
- Flash Plugin related Assertion failure: false
https://bugzilla.mozilla.org/show_bug.cgi?id=779849
Flash 11.3 crashes
https://bugzilla.mozilla.org/show_bug.cgi?id=772717
Report CPU usage for hung Flash processes
https://bugzilla.mozilla.org/show_bug.cgi?id=781124
Flash crashes 
https://bugzilla.mozilla.org/show_bug.cgi?id=773419
PluginDestructionGuard from Flash 
https://bugzilla.mozilla.org/show_bug.cgi?id=767882

How about the implementation of these features in version 17 that might have caused the slowliness ?
First revision of the Social API and support for Facebook Messenger
Sandbox attribute for iframes implemented, enabling increased security
Flags: needinfo?(macster_smart)
(In reply to macster_smart from comment #7).
> Well I'm not quite comfortable in playing around with alpha and beta builds

Finding out which specific bug started this started would certainly help here - mozregression just starts some old versions for you and asks you if the problem exists in them. It does this without affecting your existing installation and doesn't require any special knowledge.
But mozregression still uses alpha and beta Firefox versions for the test so is still alpha and beta software. 
Forget about it as I said I have an 10 years old computer and I found that version 16.0.2 works best for me so I'm gonna use this versions as long as it works. 
I've heard that some users still use Internet Explorer 6 even these days LOL so if it works for them that ancient browser this not so old version of Firefox sure will work for the years to come. :)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.