Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

how do I stop multiple plugin containers opening? ...

  • 2 件の返信
  • 4 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: brassmonkey

more options

Last night Firefox seemed really sluggish. When I looked at 'Task Manager' I had multiple plugin containers open [11 in total] - taking up too much memory.

It appeared that the plugins open when I'm clearing recent history.

I'm running Firefox 10.0.o2. Which is up to date. All plugins are up to date.

I've tried disabling add-ons ... with no effect. I thought 'Shockwave Flash' was the problem, but it's now happening when I have this disabled too.

Last night Firefox seemed really sluggish. When I looked at 'Task Manager' I had multiple plugin containers open [11 in total] - taking up too much memory. It appeared that the plugins open when I'm clearing recent history. I'm running Firefox 10.0.o2. Which is up to date. All plugins are up to date. I've tried disabling add-ons ... with no effect. I thought 'Shockwave Flash' was the problem, but it's now happening when I have this disabled too.

この投稿は brassmonkey により に変更されました

すべての返信 (2)

more options

This is a known bug*. It will happen whenever you clear history or cookies, hopefully the developers will fix it in the not too distant future. In the meantime you may just have to put up with a problem when history is cleared.

*Bug 633427 it has been slow progress but they have got as far as trialling a patch to fix the problem

more options

Good to know there's going to be a fix for this issue sometime soon.

Thanks for the info ... much apprecitated.