this post was submitted on 01 Nov 2024
1414 points (99.2% liked)

linuxmemes

21393 readers
1348 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 2 points 3 weeks ago (2 children)

    Does it kill Firefox if it tries to go over the limit? I think I tried this once and if there is a memory leak it just closes itself (which is batter than hogging the whole system, bit still)

    [–] [email protected] 5 points 3 weeks ago* (last edited 2 weeks ago) (1 children)

    No, it just limits the amount of RAM that Firefox (or whatever other application you launch with these parameters) will see.

    A few Firefox tabs may crash occasionally as a side effect. And obviously if Firefox eats up all of the 8GB it's allocated it may crash itself though usually it doesn't and tabs will crash before the browser crashes.

    [–] [email protected] 2 points 3 weeks ago

    Thanks I understand now, I'll have to try it again

    [–] [email protected] 3 points 3 weeks ago (1 children)

    I think Firefox only sees 8 GB and limits itself ideally. So if it goes over it just unloads unused tabs and such.

    [–] [email protected] 2 points 3 weeks ago

    I can confirm this, the first time I tried it out I accidentally set it to 1 GB, Firefox could only see that amount of memory. Though limiting Firefox to only 1GB its a very bad idea and it can cause it to crash it's not because it's trying to go over though it's just because it ran out of memory.

    8GB is what I would consider the safe minimum for web browsing. If you said it lower you'll have performance losses. Setting it higher though will only chew up valuable System RAM by inactive tabs.