Status

()

Firefox
General
--
critical
RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: doktor solfernus, Unassigned)

Tracking

3.5 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4

on page with plugins then I have to shut it down in running processes; then Error log pops up: plugin-container.exe encountered some problem and needs to be closed

Reproducible: Always

Steps to Reproduce:
1.visit page http://fotbal.sport.cz/fotbal/ostatni/171299-italove-odjizdeji-jako-prestarli-psanci.html
2.if you have the same problem then you are now not able to do anything
3.shut down the browser


Expected Results:  
no errors
Do you get this on all pages with flash or only on this one ?
Please try http://support.mozilla.com/en-US/kb/Safe+Mode

Which flash Version do you have installed ?
(Reporter)

Comment 2

8 years ago
I have flash v.10.0.45.2. I encountered this problem on various pages, this one was just example...

Thanks

Comment 3

7 years ago
FIREFOX v3.6.13 locked up solid on me (symptoms, getting slower, then a continual cycling "wait" circle with "Firefox is not responding").

Using PROCESS EXPLORER v11.33 by Sysinternals I have successfully killed (using the Right-Click "Kill Process" and not "Kill Process Tree" option) the PLUGIN CONTAINER (which caused the Plugin Container to reload) of Firefox 3.6.13 and am currently posting this reply.  I also killed the Sun Java hook in play with Firefox too.

Net result.  Unfreezing of Firefox and am posting from a previously solid lockup state without restarting Firefox itself (it is still laggy to a degree).

Quick solution, kill the PLUGIN CONTAINER (be nice if the Plugin Container "killed itself" when the "Firefox is not responding message lasts for over 45 seconds), let it restart, and Firefox should be good to go again.

After all, the Plugin Container is *supposed to be* a disposable sacrificial lamb in preventing crashes.  Let it die or kill it when Firefox is stunned and Firefox will live again once the Plugin Container restarts.

Note that I am also currently using "Downthemall!" to download a few hundred image files when the Plugin Container decided to go "Drama Queen" and lock up Firefox solid.  Killed the Plugin Container (as listed above), "Downthemall!" is still continuing the downloads with zero problems.

Kill that Plugin Container when it decides to give Firefox the death grip of failure, and you'll be back in the perky (though laggy) land of the living and the Plugin Container itself will restart and happy times are yours to enjoy.

Updated

7 years ago
Version: unspecified → 3.5 Branch
Reporter, Firefox 4.0.1 has been released, and it features significant improvements over previous releases. Can you please update to Firefox 4.0.1 or later, and retest your bug? Please also create a fresh profile (
http://support.mozilla.com/kb/Managing+profiles), update your plugins (Flash, Java, Quicktime, Reader, etc) and update your graphics driver and Operating system to the latest versions available. 

If you still continue to see this issue, please comment. If you do not, please close this bug as RESOLVED > WORKSFORME

filter: prefirefox4uncobugs
(Reporter)

Updated

7 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.