When leaving home page up in Firefox tab after ~5 minutes the tab will crash. This started last night and initially thought a fluke however is continuing this morning. I’ve tried CTRL+F5 to clear cache in case some code change but that did not resolve the issue. Also checked console for error messages though did not see any. So far have not had an individual post page crash; only the home page. Any other steps I can take to help troubleshoot?
Edit: Seems to have been an issue with Firefox 114.0.1. Version 114.0.2 is available now and after updating the issue is gone.
- !ozoned@lemmy.world ( @ozoned@beehaw.org ) English4•1 year ago
Yup. Firefox’s Isolated Web Container process just chomps up all the memory of your system. It’s either a memory leak in Firefox or a memory leak in Lemmy. If you downgrade Firefo it seems better, but Lemmy seems to take quite a bit of time to load. At least in my brief testing.
Sadly I don’t know how to custom build Firefox, nor have the time, to run it through Valgrind to find the leak. I tried with my standard firefox and it just never launched.
I’d recommend posting to the Github to see if Lemmy devs pay attention.
EDIT: I actually posted this earlier: https://beehaw.org/post/678781
- ffmike ( @ffmike@beehaw.org ) English3•1 year ago
Seeing the same here. Firefox 114.0.2. Also seeing slow load times in general.
Update: appears to be working fine in Chrome. I can load the same post in both browsers, and it comes up quickly in Chrome and spins in Firefox. So that’s probably pointing at a browser change.
- ffmike ( @ffmike@beehaw.org ) English3•1 year ago
Thank you; I’ve added my notes:
https://github.com/LemmyNet/lemmy-ui/issues/1385#issuecomment-1600820290
- ffmike ( @ffmike@beehaw.org ) English3•1 year ago
This may be fixed in Firefox already. I’ve been running a Beehaw tab in Firefox Nightly (116.0a1) for a few hours now, and memory appears to be stable.
Yep. Version 114.0.2 is available now and after updating the issue is gone.
- ffmike ( @ffmike@beehaw.org ) English2•1 year ago
Well…I’m definitely having the issue in 114.0.2 on a Mac. Might be some combo of the addons I have loaded, but given that it seems to be definitely fixed for me in 116 I’m not going to try to track that down further.
Glad you got yours solved though!