30
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Apr 2024
30 points (87.5% liked)
Firefox
20373 readers
177 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
Possibly one of them or another. You could try disabling a few at a time till you isolate the culprit (or eliminate them all as suspects).
Possibly? The issue is it takes upwards a week for the memory issues to reach the point of becoming noticable....
Just remembered, FF has the built in memory manager, did you ever check the usage in there?
I did find that, is there a way to just leave it on and keep tracking? it seems like the reports only run at the time you decide to check them.
It'd be nice if there was a way for it to be on at the time of the crash. I found out in my previous attempts that the crash report does not actually seem to generate for this crash.
You don't need to wait till it crashes. Check the memory usage daily, see if the usage of anything is ballooning. If it takes a week to leak enough to eat all your RAM you'll see it happening in plenty of time.