Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Learn More

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

Error count in Firefox developer toolbar is high after upgrade to Quantum.

  • 2 respostas
  • 2 têm este problema
  • 5 visualizações
  • Última resposta por DGSJM

DGSJM
DGSJM
more options

After upgrade to Quantum (57), Firefox shows an error count of hundreds (or thousands) in the bottom-right corner of developer toolbar. This happens regardless of the site I'm visiting and even just opening the developer console generates a handful more errors. But I don't see any specifics about the errors listed in the console.

The constant presence of an error count makes development more difficult. Critical errors are more difficult to notice.

What's going on? Am I missing something? Thanks

After upgrade to Quantum (57), Firefox shows an error count of hundreds (or thousands) in the bottom-right corner of developer toolbar. This happens regardless of the site I'm visiting and even just opening the developer console generates a handful more errors. But I don't see any specifics about the errors listed in the console. The constant presence of an error count makes development more difficult. Critical errors are more difficult to notice. What's going on? Am I missing something? Thanks
Capturas de ecrã anexadas

Modificado por DGSJM a

Todas as respostas (2)

user1929
user1929
more options

I can see this happening in my copy of Firefox as well. It looks like this is a known bug in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1228034 ), which happens whenever multi-process support is enabled. Multiproecess support was likely automatically enabled for you when you upgraded, which is why you're just seeing this bug now.

If you want, you can disable multi-process by opening about:config, clicking "I'll be careful", typing "browser.tabs.remote.autostart" in the searchbox, and double-clicking to change the value that appears to "false". However, this will make Firefox noticeably slower, and also a bit less secure, so I wouldn't recommend doing it. May I suggest using the console in the developer toolbox (Tools menu > Web Developer > Web console) instead?

DGSJM
DGSJM Proprietário da pergunta
more options

I tried changing the "autostart" value in "about:config". For me, the property that fixed the problem was "browser.tabs.remote.autostart.2". However, I certainly would prefer Firefox to be as fast and secure as it can be. Disabling multi-process support doesn't sound ideal, though it does stop the error count from going haywire.

Also, I do use the console in the developer toolbox. But I like how the toolbar alerts me to errors even if the console is not open. That way, I don't have to browse with the console always open.

Thanks for your quick reply and suggestions!