This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

When browser closes, many "plugin-container.exe" processes are started

  • 2 பதிலளிப்புகள்
  • 48 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by qdlmbmlxwh

When Firefox start, there's only one "plugin-container.exe" process. Instead at closing, many plugin-container.exe appear gradually taking up memory. So closing is quite slow. Is it normal?

When Firefox start, there's only one "plugin-container.exe" process. Instead at closing, many plugin-container.exe appear gradually taking up memory. So closing is quite slow. Is it normal?

u2t4c6s8n மூலமாக திருத்தப்பட்டது

தீர்வு தேர்ந்தெடுக்கப்பட்டது

That may be caused by using Delete browsing, search and download history on Firefox to clear the cookies. Firefox 4 tries to clear the Flash cookies (LSO) as well and starts the plugin-container processes to accomplish that.

Read this answer in context 👍 4

All Replies (2)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

That may be caused by using Delete browsing, search and download history on Firefox to clear the cookies. Firefox 4 tries to clear the Flash cookies (LSO) as well and starts the plugin-container processes to accomplish that.

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.