4 ms·

Not claiming, that your experience isn't true, but: Firefox hasn't crashed for me in years! And I am a real tab hoarder. 400 tabs and more are not so uncommon f

Not claiming, that your experience isn't true, but: Firefox hasn't crashed for me in years! And I am a real tab hoarder. 400 tabs and more are not so uncommon for me. Then again I don't allow arbitrary websites to run all sorts of shit scripts. It might or might not be your hardware, or it might be the websites you visit.

jeltz 5y ago
Another tab hoarder and for me the only times Firefox has crashed is when I have upgraded Firefox but not yet restarted it.
sockaddr 5y ago
Yeah, I think there are measures I could take to help the situation but it's a little low on my priority queue at the moment. The crashes are rare and not really a big issue for me.
mhitza 5y ago
Not the OP, but I consider it a soft crash every time I update Firefox in my OS, and it won't allow me to spawn new tabs until I restart Firefox. Annoying behavior they've included a couple years back.
- sfink 5y ago
  If I understand what you're reporting correctly, then that's something your OS "included a couple of years back". If you install Firefox from Mozilla's site, it won't have these update problems. What's happening is that your package manager is swapping Firefox's bits out from under it while it's running. Firefox's built-in update system doesn't do that. Which is not to say that I think you shouldn't be using a packaged version of Firefox. Personally I'm running Nightly so I don't have the option anyway. Generally speaking, I vastly prefer sticking to my package manager's stuff. I just wish the package managers would fix their Firefox updates. (I don't know what the right fix would be, and I imagine it could be hard.)
  - mhitza 5y ago
    Then someone at Redhat was probably bribed by some Googler, cause it only happens with Firefox updates /s Joke aside, Firefox is aware that it's been updated and the new tab states that I have to restart my browser. I'm not familiar with the inner workings of Firefox, I just expect it to have everything it needs to function, in working memory. I've been using Fedora for close to 14 years now, Firefox always installed from system packages, and the updates always replaced the existing files on disk without it affecting my application experience. No other desktop app I use has this behavior after updates while they where running. A big fuss? No, got used to it already. But I still consider it a soft crash state that I encounter with Firefox.
    - kaba0 5y ago
      You just probably use the web browser much more often to catch it after an update. And afaik, the reason for this is that they can only maintain a known good state this way, as well as making freshly patched security patches available as soon as possible.
    - grey_earthling 5y ago
      Strictly, Fedora doesn't support doing updates while the system is running (or at least they don't recommend it). An alternative that might be smoother in this regard: use a flatpak version of Firefox instead. (Firefox is in Fedora's flatpak repo, and on Flathub.) GNOME Software updates flatpak apps in the background, and you just get the new version the next time you open the app.
      - mhitza 5y ago
        Not sure from which perspective your comment comes from. dnf update or dnfdragora updates (if you prefer a GUI) are all done while the system is running. Sure, distribution upgrades nowadays are just like Windows update requiring a system reboot and a black screen with a useless progress bar to stare at (that's also a pretty annoying relatively recent addition). GNOME is not my cup of tea. And until flatpak delivers tangible finegrained software sandboxing (at least Android level sandboxing), I'm not really interested in using it for software that's already packaged in the dnf repositories. I use Fedora because it has newer software, pretty stable in my experience, and my knowledge is transferable to RedHat/Enterprise Linux. But I stopped buying into most of Redhat's desktop innovations a while ago.
Datagenerator 5y ago
Don't forget to disable all prefetching, landing pages visiting previous sites, studies and pings on each start and shutdown to improve privacy.

jeltz 5y ago

Another tab hoarder and for me the only times Firefox has crashed is when I have upgraded Firefox but not yet restarted it.

sockaddr 5y ago

Yeah, I think there are measures I could take to help the situation but it's a little low on my priority queue at the moment. The crashes are rare and not really a big issue for me.

mhitza 5y ago

Not the OP, but I consider it a soft crash every time I update Firefox in my OS, and it won't allow me to spawn new tabs until I restart Firefox. Annoying behavior they've included a couple years back.

sfink 5y ago
If I understand what you're reporting correctly, then that's something your OS "included a couple of years back". If you install Firefox from Mozilla's site, it won't have these update problems. What's happening is that your package manager is swapping Firefox's bits out from under it while it's running. Firefox's built-in update system doesn't do that. Which is not to say that I think you shouldn't be using a packaged version of Firefox. Personally I'm running Nightly so I don't have the option anyway. Generally speaking, I vastly prefer sticking to my package manager's stuff. I just wish the package managers would fix their Firefox updates. (I don't know what the right fix would be, and I imagine it could be hard.)
- mhitza 5y ago
  Then someone at Redhat was probably bribed by some Googler, cause it only happens with Firefox updates /s Joke aside, Firefox is aware that it's been updated and the new tab states that I have to restart my browser. I'm not familiar with the inner workings of Firefox, I just expect it to have everything it needs to function, in working memory. I've been using Fedora for close to 14 years now, Firefox always installed from system packages, and the updates always replaced the existing files on disk without it affecting my application experience. No other desktop app I use has this behavior after updates while they where running. A big fuss? No, got used to it already. But I still consider it a soft crash state that I encounter with Firefox.
  - kaba0 5y ago
    You just probably use the web browser much more often to catch it after an update. And afaik, the reason for this is that they can only maintain a known good state this way, as well as making freshly patched security patches available as soon as possible.
  - grey_earthling 5y ago
    Strictly, Fedora doesn't support doing updates while the system is running (or at least they don't recommend it). An alternative that might be smoother in this regard: use a flatpak version of Firefox instead. (Firefox is in Fedora's flatpak repo, and on Flathub.) GNOME Software updates flatpak apps in the background, and you just get the new version the next time you open the app.
    - mhitza 5y ago
      Not sure from which perspective your comment comes from. dnf update or dnfdragora updates (if you prefer a GUI) are all done while the system is running. Sure, distribution upgrades nowadays are just like Windows update requiring a system reboot and a black screen with a useless progress bar to stare at (that's also a pretty annoying relatively recent addition). GNOME is not my cup of tea. And until flatpak delivers tangible finegrained software sandboxing (at least Android level sandboxing), I'm not really interested in using it for software that's already packaged in the dnf repositories. I use Fedora because it has newer software, pretty stable in my experience, and my knowledge is transferable to RedHat/Enterprise Linux. But I stopped buying into most of Redhat's desktop innovations a while ago.

Datagenerator 5y ago

Don't forget to disable all prefetching, landing pages visiting previous sites, studies and pings on each start and shutdown to improve privacy.