3
#VsCode/#Codium is making my mac unstable because of how much resources it's using (it recently used 47 GB ram, out of 16) so I've been trying out ... (mastodon.art)
submitted 1 year ago by to c/programming@fedia.io
5 comments fedilink hide all child comments
 

#VsCode/#Codium is making my mac unstable because of how much resources it's using (it recently used 47 GB ram, out of 16) so I've been trying out alternatives. The Kate editor seems nice
#coding #programming

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 year ago (4 children)
  1. Just because it has 47 GB mapped doesn't mean it's trying to use all that... I have used VSCode on a machine with 8 GB of RAM and it actually behaved better than Firefox, and I can't remember having any serious issues. Of course if it's your experience that it ruins your machine, then that's what's up, I'm just saying it might be an extension or something.
  2. You might look into Helix Editor if you're up for a learning curve. I started learning it pretty recently and it is now my favorite editor for smaller / no-extension-needed projects.
  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 1 year ago (3 children)

    @PhilipTheBucket the whole os locks up and i have to force power off so it’s a genuine issue

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

    Whoa... that's definitely not supposed to happen. My first random guess would be that some of your RAM's gone bad; if you're not using some Firefox derivative for web browsing, then VSCode might just be the only thing that's stressing the memory enough to cause the crash. But that's not an expected result just from stressing the system's resources (at least certainly not to that modest extent).

    If it were me I might run a memory tester and see what it said. I have no real idea if that's the issue or not, but that's a thing I would try.

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

    @PhilipTheBucket Ig it won’t hurt, but I don’t have issues with anything else, including compiling large programs on all cores and playing resource intensive games

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    Hm, yeah, maybe not that then. In that case I have no idea, I just know I've used VSCode on a lot more resource-constrained machines than that and can't remember ever having it cause a whole system crash.

    (Actually, not completely true -- once I set up a NixOS machine with 8GB of RAM and forgot to make any swap for it for some stupid reason, and that one definitely got completely hosed if I tried to open up e.g. Codium and Firefox at the same time. But not for any machine that was set up right 🙂.)

  • permalink
  • fedilink
  • source
  • parent