8 ms·

How is that possible, I get FF crashes literally every time I load a moderately intensive website (eg. Google Keep). I still use FF because I can't abide Chrome

How is that possible, I get FF crashes literally every time I load a moderately intensive website (eg. Google Keep). I still use FF because I can't abide Chrome. My PC is admittedly a bit older (only 6 gigs RAM) but still.

techwizrd 5y ago
I routinely have hundreds of tabs open in Firefox at any given time without crashes on macOS and Linux. The tabs include everything from documentation, Jupyter notebooks, papers, Jira, Reddit, HN, Github, Gitlab, GMail, Google Keep, Todoist, etc. I can't even recall the last time Firefox crashed for me.
- sundarurfriend 5y ago
  Agreed. I've got 99 problems with Firefox, but a crash ain't one.
- brokenmachine 5y ago
  Many hundreds of tabs here in FF on Windows and pretty rock solid.
loufe 5y ago
I don't know if I've experienced a crash in Firefox in years. I would really suggest taking a look at the crash logs and maybe do a checkup on your machine's health.
jandrese 5y ago
6GB is ample memory if you're not loading tons of tabs. I run Firefox on Raspberry Pi model 1s and while you have to limit yourself to a tab or two and have plenty of patience it does still work. What doesn't work is trying to compile the browser on the Pi. The build process has some really gigantic source files that cause the compiler to choke.
marcosdumay 5y ago
Hum... Firefox breaking on some Google site is surprising, but not extremely so.
bmicraft 5y ago
You should really check if you have bad memory. I've found firefox to be very sensitive to such an issue
kaba0 5y ago
Maybe corrupted firefox profile? Try running it with a new empty one.
sundarurfriend 5y ago
I've only got 4 gigs of RAM, and don't think I've seen Firefox crash in years. And I run Jupyter notebooks, browser games, image processing, all sorts of intensive things on it.
peter_l_downs 5y ago
Fwiw i left Keep a few years ago because they totally fucked the web client. Wouldn’t work for me on either ff or chrome. Had a few thousand notes. Not sure if it’s any better now but that may be a Keep specific thing
gcp 5y ago
Paste a few links from about:crashes here. If you click on them, you might find the associated bug (if it exists). Firefox should literally never crash. If it does, that's a serious bug (but especially on Windows, not necessarily in Firefox itself).
BikeHelmet 5y ago
Just throwing it out there - most software and OS's adapt to fit hardware constraints. I was running 32GB of RAM, and regularly hit 20-24GB of use in my web browser. When I switched to 128GB of RAM and reloaded my session, my web browser expanded its use to 40-44GB and performed a lot better. While Firefox may be working with 6GB, it may work a lot better with 16GB, for example. The crashes could be some addon or other profile feature interfering with Firefox's stability. I had a profile that I migrated from FF 1.x, and I finally had to put that one to rest...

techwizrd 5y ago

I routinely have hundreds of tabs open in Firefox at any given time without crashes on macOS and Linux. The tabs include everything from documentation, Jupyter notebooks, papers, Jira, Reddit, HN, Github, Gitlab, GMail, Google Keep, Todoist, etc. I can't even recall the last time Firefox crashed for me.

sundarurfriend 5y ago
Agreed. I've got 99 problems with Firefox, but a crash ain't one.
brokenmachine 5y ago
Many hundreds of tabs here in FF on Windows and pretty rock solid.

loufe 5y ago

I don't know if I've experienced a crash in Firefox in years. I would really suggest taking a look at the crash logs and maybe do a checkup on your machine's health.

jandrese 5y ago

6GB is ample memory if you're not loading tons of tabs. I run Firefox on Raspberry Pi model 1s and while you have to limit yourself to a tab or two and have plenty of patience it does still work. What doesn't work is trying to compile the browser on the Pi. The build process has some really gigantic source files that cause the compiler to choke.

marcosdumay 5y ago

Hum... Firefox breaking on some Google site is surprising, but not extremely so.

bmicraft 5y ago

You should really check if you have bad memory. I've found firefox to be very sensitive to such an issue

kaba0 5y ago

Maybe corrupted firefox profile? Try running it with a new empty one.

sundarurfriend 5y ago

I've only got 4 gigs of RAM, and don't think I've seen Firefox crash in years. And I run Jupyter notebooks, browser games, image processing, all sorts of intensive things on it.

peter_l_downs 5y ago

Fwiw i left Keep a few years ago because they totally fucked the web client. Wouldn’t work for me on either ff or chrome. Had a few thousand notes. Not sure if it’s any better now but that may be a Keep specific thing

gcp 5y ago

Paste a few links from about:crashes here. If you click on them, you might find the associated bug (if it exists). Firefox should literally never crash. If it does, that's a serious bug (but especially on Windows, not necessarily in Firefox itself).

BikeHelmet 5y ago

Just throwing it out there - most software and OS's adapt to fit hardware constraints. I was running 32GB of RAM, and regularly hit 20-24GB of use in my web browser. When I switched to 128GB of RAM and reloaded my session, my web browser expanded its use to 40-44GB and performed a lot better. While Firefox may be working with 6GB, it may work a lot better with 16GB, for example. The crashes could be some addon or other profile feature interfering with Firefox's stability. I had a profile that I migrated from FF 1.x, and I finally had to put that one to rest...