Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

I have a message to Mozilla. Can you please fix the buffering problem with Flash for Firefox 33?

  • 2 răspunsuri
  • 8 au această problemă
  • 3 vizualizări
  • Ultimul răspuns de sabbath99

more options

Hello Mozilla. Ever since I upgraded to 32, I had this buffering problem on Flash (especially YouTube videos) where the gray timing bar would stop moving and the video would start buffering. This wasn't fixed for Firefox 32.0.1. Can you please fix all of this?

Hello Mozilla. Ever since I upgraded to 32, I had this buffering problem on Flash (especially YouTube videos) where the gray timing bar would stop moving and the video would start buffering. This wasn't fixed for Firefox 32.0.1. Can you please fix all of this?

Toate răspunsurile (2)

more options

Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.

You can try to disable hardware acceleration in Firefox.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.

You can check for problems with current Shockwave Flash plugin versions and try this:

See also:

more options

cor-el, I downgraded back to Firefox 31 and this problem doesn't happen there. I think you should get Mozilla to fix this problem for Firefox 33. This is the problem I was having with Firefox 32.