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

plugin-container triggers upon clear recent history

  • 3 Antworten
  • 29 haben dieses Problem
  • 10 Aufrufe
  • Letzte Antwort von RobHunt

more options

I've disabled plugin-container from triggering using the about:config and dom.ipc... settings. Worked fine in 3.6, but with 4.0, I noticed plugin-container processes popping up when I cleared recent history (cookies, cache, active-logins). A BUNCH of plugin-container processes, which then proceed to peg the CPU (for whatever goddamned reason). I have to restart Firefox to get them to clear.

This is repeatable: • visit http://boston.com/ • check processes via TaskMgr; only 1 firefox.exe running (as expected) • clear recent history: selecting cookies, cache & active logins • check processes and BAM, multiple plugin-container processes

I've disabled plugin-container from triggering using the about:config and dom.ipc... settings. Worked fine in 3.6, but with 4.0, I noticed plugin-container processes popping up when I cleared recent history (cookies, cache, active-logins). A BUNCH of plugin-container processes, which then proceed to peg the CPU (for whatever goddamned reason). I have to restart Firefox to get them to clear. This is repeatable: • visit http://boston.com/ • check processes via TaskMgr; only 1 firefox.exe running (as expected) • clear recent history: selecting cookies, cache & active logins • check processes and BAM, multiple plugin-container processes

Alle Antworten (3)

more options

Update: Simply starting Firefox, blank page and not visiting any sites and clearing recent history triggers two plugin-container processes.

more options

Clicking "Clear Recent History" in Firefox 4.0 triggers several instances of "plugin-container.exe" which can be seen in Task Manager. The memory usage is about 100MB. It sometimes takes 20-30 seconds for the CRH box to disappear as the computer whirs away in obvious distress.

System info: WinXP Home Edition, SP3, 32-bit

Firefox 4.0

Firefox add-ons: NoScript, AdBlock Plus, CookieCuller

Geändert am von firefox123

more options

UPDATE: It seems that pages containing Flash animations trigger plugin-container processes when EITHER recent history AND/OR Firefox (process) is closed. In the latter case, plugin-container processes activate, go postal (CPU-wise) and then (eventually) disappear, delaying the rundown and exit of Firefox. Very annoying.