Why does plugin-container.exe start running ten or more instenses of itself (or why does firefox whichever) every single time i try to clear my history?
I try to clear my history on cache and the computer freezes. ten or more instenses of plugin-container.exe shows up in the process.... after this 50% of the time i have kill the entire FireFox program from the task manager and the other 50% of the time it slows way, way down and will do nothing until a message from firefox telling me "a script is not responding" and i can choose to stop the script or continue. if i stop the script eventually i can close firefox and all the instances of plugin-container will also shut down but my history and cache still are not cleared.
所有回覆 (8)
The plugin-container processes are started to clear the Flash local objects (Flash cookies ,LSO).
If you want to avoid that then clear the cookies manually in the Cookie Manager, also accessible via the favicon on the location bar -> More Information -> View Cookies and clear the search bar if necessary.
Thankyou for your help. I am still getting the script error... this is the script that stops responding, do you happen to know what it is?
chrome://browse/content/sanitize.js:136
the message is coming from firefox and it stops every timei try to clear the cache and history all at once
Again, thank you for your help
Hey Cor-rel, this contradicts your post at http://support.mozilla.com/en-US/questions/820740?s=plugin-container.exe&as=s. BTW, having same problem. BTW having same probs, even with all add-ons disabled. And...this even happens when I launch Firefox, not just closing it.
@ginassweeps
Please use Ask a Question and start your own thread. Post your "Troubleshooting Information" where requested, as the Owner of this thread did.
@the-edmeister
As nice as it is that you want ginasweeps to start her own thread it seems a little ridiculous that you would require it when 1) she had the same da** question. 2) My question was NEVER properly answered and 3) she was pointing out that Cor-rel directly contradicted what he said in prior postings.
in fact if you look at the threads there are multiple threads that have restated the same question in a different way. and all of the responses are varied and ambiguous.
Also Cor-rel only tried to treat the symptom not correct the problem.
if the problem is just bad programming that needs to be addressed in an update but it hasn't been worked out yet; then, if Mozilla wants to obtain the people that have been loyal supporters, they should say "here is how we recommend dealing with the symptoms of the problem. the cause is not yet known but we are working on it."
More answers less bureaucratic bs
由 stryde2101 於 修改
Sorry, I don't see a contradiction in cor-el's two responses, as ginassweeps noted. The thread that was cited was lacking in troubleshooting information in comparison to what you posted, so that answer was succinct - in my opinion. She can do as I recommended or not, that is her choice.
As far as bs goes, I have had my fill for today. I'm outta here for the evening.
You guys can keep up the criticism of the volunteers who are trying to help you, but someday there may not be anyone left here to help you guys. Between the crappy software used here and all the negative / disparaging comments thrown around here, few experienced Firefox users want to "armor-up" and venture into this realm to help other less experienced Firefox users.
@the-edmeister
you are correct in saying that i was unappreciative to you volunteers. It was a childish response and I hope you will accept my apology.
Regarding the use of Volunteers
http://www.technobuffalo.com/internet/how-does-the-mozilla-foundation-make-money/
http://thenextweb.com/2009/11/20/mozilla-money-start-exploring-options/
In 2007 the president of Mozilla was paid a salary of half a million... see http://en.wikipedia.org/wiki/Mitchell_Baker
My point? Mozilla is a non-profit but its creators and management are paid well, they do a lot of good work and have a comparatively tiny amount of employees.
Perhaps they should hire one or two tech guys and programers that can browse this forum and address any unanswered or incomplete question. because, believe it or not, those of us who choose to use Firefox are indeed the very thing that is generating their operating capitol. Just because they are non-profit does not mean that they do not have customers. Without the users the income would dry up, in affect making us user the customers. A company (be it non-profit or otherwise) can not ask its customers to use a faulty product and then not provide adequate support for that product and expect to remain successful.
What i am saying is that i am sorry you are a volunteer, it doesn't really sound worth it to me if you consider one of the people asking you to work for free and take all this guff for free made half a million back in 2007 and i am sure there have been at least cost of living raises since that time.
i have supported and recommended Firefox to everyone i know. i hate ie4 and don't really like chrome but at least there is some accountability because their support is not provided by (to the best of my knowledge) volunteers that can log off when they do not like the way things are going. so unfortunately if mozilla can not provide better solutions i will be making a switch
in any event, Thank you for what you have done. I think you are being taken advantage of and applaud you if you continue to volunteer here. Also please know that my annoyance was not intentionally direct at you but was meant for Mozilla and the fact that this problem continues to exist without any official redress or acknowledgement.
again, i sincerely hope you accept my apology
I am using Firefox 4.0.1 (win32, en-US) on Windows XP Professional SP3 (i386, ENU). I am able to solve this problem by renaming the "XUL.mfl" and "startupCache.4.little" files (after closing Firefox first of course). Search for the files in your system (C) drive, making sure to search for hidden files and folders, then rename the files to different names. After renaming the files, try relaunching Firefox and using the "Clear Recent History" function (with "Cookies" selected) for a few times, and hopefully the problem should be solved.