Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

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

  • 2 svar
  • 48 har detta problem
  • 1 visning
  • Senaste svar av 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?

Ändrad av u2t4c6s8n

Vald 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 svaret i sitt sammanhang 👍 4

Alla svar (2)

more options

Vald 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.