Memory leak worsened (v135.0)
Has anyone else noticed that the memory leak issues have gotten way worse since last update? I work on a potato. Most of the memory is in the windows paging file, on a m… (আরও পড়ুন)
Has anyone else noticed that the memory leak issues have gotten way worse since last update?
I work on a potato. Most of the memory is in the windows paging file, on a mechanical hard drive. So freeing up used memory takes longer than it would on a machine with a metric tonne of quad-channel RAM. The past 6 months, Firefox has started having memory leak issues, where it just uses more & more memory until the paging file hits its hard limit and windows kills firefox.
But since last update (135.0 x64), the memory leak issue has worsened significantly.
If I open firefox, and then tab between all current tabs, I get maybe 5 GB of memory usage. So even if all tabs are marked as "active" and loaded into memory, this still isn't enough to cause issues.
But after 30 minutes, that memory usage has ballooned up to >20 GB, at which point windows decides that it needs to free up memory, and kills the process. Which is annoying, because then the browser reverts to the last saved state, meaning many tabs can be lost or reset to several clicks back.
I've tried shaving off extensions, with zero change. I've tried increasing paging file size, but that's just kicking the bucket down the road.
Anyone have a solution to this?