Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 2 Antworten
  • 48 haben dieses Problem
  • 18 Aufrufe
  • Letzte Antwort von qdlmbmlxwh

u2t4c6s8n
u2t4c6s8n
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?

Geändert am von u2t4c6s8n

Ausgewählte Lösung

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.

Diese Antwort im Kontext lesen 👍 4

Alle Antworten (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Ausgewählte Lösung

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.

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