If you look in about:memory, you can try to diagnose a bit where the memory is going. This may or may not result in anything that will be useful for you. I ap

If you look in about:memory, you can try to diagnose a bit where the memory is going. This may or may not result in anything that will be useful for you. I appreciate that it is frustrating when your browser is misbehaving, but your generic complaint "my browser leaks like a sieve!" cannot possibly garner anything other than generic suggestions. Memory issues can be caused by buggy websites, websites that use some feature that Firefox implements poorly, addons, plugins, buggy graphics drivers, and so on. Issues that come up after days of heavy browsing can be particular hard to diagnose. > although I had the impression that both sorts of fixes were generally backported to the ESR branch ESR mostly just receives security updates, plus the occasional crash fix.