Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Plugin-container bug report

  • 1 resposta
  • 6 têm este problema
  • 3 visualizações
  • Última resposta de cor-el

more options

I'm having a problem that started in ver 9 and continues through 10.0.2. I use two plugins, Flash and RealPlayer. I also view pdf's outside of Firefox in Acrobat (not Reader). Each time i close a session of Firefox, the plugin-containers do not get killed. Also, Firefox will also start Acrobat with no open window when it closes. If I run a bunch of Firefox sessions without rebooting or manually killing the plugin-container sessions, they start to accumulate. I have had 10 - 20 running after a few days. And Acrobat is always running even though there is nothing showing. That doesn't seem reasonable.

I'm having a problem that started in ver 9 and continues through 10.0.2. I use two plugins, Flash and RealPlayer. I also view pdf's outside of Firefox in Acrobat (not Reader). Each time i close a session of Firefox, the plugin-containers do not get killed. Also, Firefox will also start Acrobat with no open window when it closes. If I run a bunch of Firefox sessions without rebooting or manually killing the plugin-container sessions, they start to accumulate. I have had 10 - 20 running after a few days. And Acrobat is always running even though there is nothing showing. That doesn't seem reasonable.

Alterado por Jutt em

Todas as respostas (1)

more options

That can be caused by clearing the cookies via "Clear Recent History".

  • Firefox/Tools > Options > Privacy > Firefox will: "Use custom settings for history" > [X] Clear history when Firefox closes > Settings
  • Firefox > History > Clear Recent History
  • Tools > Clear Recent History

If you use "Clear Recent History" to clear the cookies then Firefox also tries to clear the cookies from plugins like Flash (LSO) and starts a plugin-container process for each plugin and that can add extra time and can cause an unresponsive script error to appear.