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!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Version 115 uses too much memory

  • 2 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan 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.

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

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

more options

Keazen oplossing

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.