169
ForkServer in Firefox 141: No More Restarts and Better Performance on Linux (ostechnix.com)
submitted 1 year ago by to c/linux@lemmy.ml
24 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (2 children)

Kind of neat... Don't know if really useful at all, but cool anyway

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 42 points 1 year ago* (1 child)
    • No More Forced Restarts: This is a huge relief for many!. Firefox on Linux no longer requires a forced restart after your package manager applies an update. This means smoother, uninterrupted browsing, even during system updates.
    • Reduced Memory Usage: ForkServer leads to a significant reduction in memory consumption for content processes. The base resident memory for a content process is now around 50% lower. This helps Firefox run more efficiently, especially if you have many tabs open.
    • Faster Process Startup: You'll notice that content process startup times are reduced by approximately 35%. This translates to snappier new tab openings and overall improved responsiveness.

    Sounds actually too good to be true to me.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 18 points 1 year ago (1 child)

    Reduced Memory Usage:

    This is the one that really matters. Both Chrome and FF are brutal on memory use.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 1 year ago (1 child)

    That’s because each tab is sandboxed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 1 year ago (2 children)

    And cached. Browsers just use the RAM for what it exists for.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    I use Auto Tab Discard, have all except 10 tabs unloaded and FF has 5.5 GB reserved, just in case.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    I have currently 13 tabs open and I don’t see the issue. RAM is there to be used. I actually expect my programs to extensively cache stuff and use the RAM.

    (The other Firefox processes for the individual tabs are cut from the screenshot.)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 1 year ago (1 child)

    I for one am extremely happy about the no force restart. It's quite minor in the grand scheme of things, but it is so annoying.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 year ago (1 child)

    True, its annoying, bit this does not take away the need for a restart of the process, obviously, just you can do it at a more convenient time.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 year ago

    Absolutely, it's only about convenience. I often miss the fact that firefox is in the list of all the packages that are getting updated and realize it only when I open a new tab and I get the error message, and that's annoying. Very much a first world problem for sure!

  • permalink
  • fedilink
  • source
  • parent