ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Firefox locking up on opening. Have refreshed, no help

  • 6 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 4 ნახვა
  • ბოლოს გამოეხმაურა davewhitearcata

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.

გადაწყვეტა შერჩეულია

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

See also:

პასუხის ნახვა სრულად 👍 0

ყველა პასუხი (6)

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?

The problem seems to go away.

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

შერჩეული გადაწყვეტა

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

See also:

ჩასწორების თარიღი: , ავტორი: cor-el

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

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