Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i 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.

Læs mere

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

  • 2 svar
  • 48 har dette problem
  • 18 visninger
  • Seneste svar af qdlmbmlxwh

more options

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?

Ændret af u2t4c6s8n den

Valgt løsning

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.

Læs dette svar i sammenhæng 👍 4

Alle svar (2)

more options

Valgt løsning

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.

more options

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.