We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

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

  • 2 odgovora
  • 48 ima to težavo
  • 18 ogledov
  • Zadnji odgovor od 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?

Spremenil u2t4c6s8n

Izbrana rešitev

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.

Preberite ta odgovor v kontekstu 👍 4

Vsi odgovori (2)

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

Izbrana rešitev

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.