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

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Version 115 uses too much memory

  • 2 réponses
  • 1 a ce problème
  • 2 vues
  • Dernière réponse par vgleiber

vgleiber
vgleiber
more options

Memory usage jumps significantly on new tabs. And no, it didn't happen on the previous version.

Sometimes this memory is later released but not always.

Memory usage jumps significantly on new tabs. And no, it didn't happen on the previous version. Sometimes this memory is later released but not always.

Solution choisie

Thanks for the prompt reply, Terry.

No, it didn't solve the problem. All of it might be relevant if the previous version under the same conditions didn't work perfectly.

But there is good news - I've found the problem. It was the Dashlane extension which didn't automatically update itself to its new version. After I forced it to look for updates everything is OK.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (2)

Terry
Terry
more options

Does it happen with all new tabs or only with some sites? The article linked below may help. You could try entering about:memory in the address bar. That page has a button for minimising memory usage.

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources

vgleiber
vgleiber Auteur de la question
more options

Solution choisie

Thanks for the prompt reply, Terry.

No, it didn't solve the problem. All of it might be relevant if the previous version under the same conditions didn't work perfectly.

But there is good news - I've found the problem. It was the Dashlane extension which didn't automatically update itself to its new version. After I forced it to look for updates everything is OK.