Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Learn More

Firefox locking up on opening. Have refreshed, no help

  • 6 odpovedí
  • 1 má tento problém
  • 4 zobrazenia
  • Posledná odpoveď od davewhitearcata

more options

A few seconds after opening Firefox it locks up. Eventually a Shockwave Flash error message comes up. Clicking either the continue or close plug inbuttons does not help. After a few minutes Firefox will operate normally until I reopen it. I have refreshed, updated Shockwave to no avail. I have the latest version of Firefox and am running Win 10.

A few seconds after opening Firefox it locks up. Eventually a Shockwave Flash error message comes up. Clicking either the continue or close plug inbuttons does not help. After a few minutes Firefox will operate normally until I reopen it. I have refreshed, updated Shockwave to no avail. I have the latest version of Firefox and am running Win 10.

Vybrané riešenie

You can check for problems with current Shockwave Flash plugin versions and hardware acceleration in Firefox and try this:

See also:

Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (6)

more options

What are you using as the homepage?

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac=Options)
key, and then starting Firefox. Is the problem still there?

more options

The problem seems to go away.

more options

The problem does go away in safe mode. Changing homepage did not cure the problem, If I wait a couple of minutes it starts operating normally. Annoying

more options

Vybrané riešenie

You can check for problems with current Shockwave Flash plugin versions and hardware acceleration in Firefox and try this:

See also:

Upravil(a) cor-el dňa

more options

I updated Adobe Flash again (updated earlier today) and this seemed to cure the problem. Maybe there was a Flash issue that was corrected?

more options

It seems I was premature in declaring the problem solved. This morning it has returned. Is anyone else having this problem?