1395
32GB Ram and Linux
(quitaxd.online)
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 01 Nov 2024
1395 points (99.4% liked)
linuxmemes
21180 readers
789 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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!
founded 1 year ago
MODERATORS
Can't relate, just upgraded my laptop from 32GB to 64GB since VScode would keep closing due to OOM. What? Oh, no, it's not vscode's fault.....I keep like 5 Firefox windows with 30+ tabs open, like a fucking maniac..... Close them? What do you mean "close" them?
I think there's still something wrong with your setup.... You should be able to have as many Firefox windows and tabs as you'd like without using too much RAM, since they should de "suspended".
I regularly have hundreds of tabs running fine, on 32GB of RAM.
Most likely it's a vscode extension that's leaking memory, and this problem will still happen after your upgrade, just take longer.