the memory leak introduced by 115 has been fixed
A1Rayne
joined 2 years ago
nextbern is that you :P
116 when?
very nice but for me 115 has been a disaster, progressively using abnormally high amounts of RAM.
I'm just about done with this browser as a daily driver. will keep it as a backup. its always the same with firefox a few versions it runs great then comes another update that breaks the hell out of it.
i am quoting them from this reddit post:
https://www.reddit.com/r/Dashlane/comments/14jh4kv/dashlane_getting_slow_on_firefox/
The fix for the browser latency issues has been added to our latest version releases for Chrome and Edge - v6.2325. However, we are still waiting on Mozilla's review, which is why Firefox is still on version 6.2321. Here is the bug we filed with Mozilla https://bugzilla.mozilla.org/show_bug.cgi?id=1838448 Will update once we get more info.
and pin tabs that remain pinned after the browser is closed
edit: culprit found: dashlane extension for firefox causing latency and high use of resources.. dashlane claims they are waiting on mozilla to review their patch submitted 3 weeks ago:
thanks ill just use vivaldi for the time being. this new version is using 10k + ram with 3 tabs open. unusable.
pitty though firefox was working so well since 112 and great since 114. this patch butchered the performance.
i have a feeling there is something horribly wrong with 115.
firefox has been lagging and using too much ram. 114 was the best patch in history but now its back to the same old struggling firefox. or worse.
hmm i was sure this patch would contain native translation for desktop.. rather underwhelming