Beehaw Support

2794 readers

1 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

Penguincoder@beehaw.org

remington@beehaw.org

[Solved] Beehaw crashing after few minutes (beehaw.org)

submitted 1 year ago* (last edited 1 year ago) by s3rvant@beehaw.org to c/support@beehaw.org

8 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] s3rvant@beehaw.org 2 points 1 year ago (1 children)

Thank you; I've added my notes:

https://github.com/LemmyNet/lemmy-ui/issues/1385#issuecomment-1600820290

[–] ffmike@beehaw.org 1 points 1 year ago (1 children)

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.

[–] s3rvant@beehaw.org 0 points 1 year ago (1 children)

Yep. Version 114.0.2 is available now and after updating the issue is gone.

[–] ffmike@beehaw.org 2 points 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!