Closed Bug 383923 Opened 19 years ago Closed 18 years ago

Certain Flash scripts makes FX unresponsive

Categories

(Firefox :: Extension Compatibility, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: broset, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20061201 Firefox/2.0.0.4 (Ubuntu-feisty) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20061201 Firefox/2.0.0.4 (Ubuntu-feisty) Surfing to this website (http://www.nos.nl/nosstudiosport/voorpagina/index.html) makes fx unresponsive for 5 to 10 seconds. This Adobe Flash message pops up: "A script in this movie is causing Adobe Flash Player 9 to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?" Clicking 'yes' makes everything run smooth again, clicking 'no' leads fx to crash, and a forced quit is neccesary. On version 2.0.0.3 this did never occurred. Now always. Reproducible: Always Steps to Reproduce: 1.install fx 2.0.0.4 2.install adobe flash 9 for linux 3.surf to http://www.nos.nl/nosstudiosport/voorpagina/index.html Actual Results: Unresponsive fx for 5 to 10 seconds, the this adobe flash message pops up "A script in this movie is causing Adobe Flash Player 9 to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?" Expected Results: Excecute the Flash script and being able to view the site's Flash contents.
Summary: Certain Flash scripts make FX unresponsive → Certain Flash scripts makes FX unresponsive
Ok, if anyone is interested: I think the clue is that I've got a shared Firefox directory for both Win XP and Linux, the flash plugins may be conflicting. Because surfing to that very website on machines without a shared Fx directory to problem doesn't occur.
Ok, nobody is interested, but what the hell: reinstall of ubuntu solved the prob..
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.