4 ms·

To summarize my above findings. For me the biggest problem here is the high CPU usage when the app should be idling. That KILLS battery life. I would not accep

To summarize my above findings. For me the biggest problem here is the high CPU usage when the app should be idling. That KILLS battery life. I would not accept this behavior from high end video software, I certainly will not accept it from a text editor. Following that the high RAM use can lead to swapping which will impact performance and battery live. As I said above after a clean install, and with just one short markdown file open, Atom is now using over 2GB RAM and Climbing. Fortunately, I have 16GB RAM on this system, otherwise I would already be swapping. BBEdit and SublimeText never tax the CPU unless I am working with extremely large files, or doing search & replace on a huge number of files. I often will have 50 to 100 files open for days in these editors. I like the evolving ecosystem of Atom, it now looks to be about on par with Sublime, and I can see that it will soon over take Sublime on that front. But it really need to get the resource utilization under control. To be fair to Atom, I also tried installing it on a Mac Mini with an almost clean Mac OS X 10.11 installation. I had similar problems.

stymaar 11y ago
> BBEdit and SublimeText never tax the CPU unless I am working with extremely large files […] it really need to get the resource utilization under control Neither does Atom for most users. It's not just n problem of «resource utilization», you're clearly facing a bug … Maybe you should consider submitting an issue (https://github.com/atom/atom/issues https://github.com/atom/atom/issues)
- leejoramo 11y ago
  I see a number of current CPU related issues for Atom. I will look into using the performance diagnostic tools and see if I can contribute any new insights. Again, I am see the issues on admittedly rather heavily customized workhorse MacBook (lots of Unix level tweets), AND on my stock Mac Mini. So I don't think this is a case isolated to just me.
  - leejoramo 11y ago
    As noted in this thread, I solved my problem, and filed an issue: https://github.com/atom/atom/issues/10421 https://github.com/atom/atom/issues/10421
fuzzywalrus 11y ago
Atom Helper sometimes gets a mind of its own and runs rampant on the CPU, sometimes eating 100% of a single core even an i7 2015 MacBook Pro. Quiting Atom doesn't seem to stop Atom helper. It takes firing up the Activity Monitor and quitting them. It's ugly but it works.
seanp2k2 11y ago
I've had this happen too. For me, disabling a continuously-fading cursor plugin stopped most of my troubles with high CPU. Still kind of ridiculous that to animate the color on a few dozen pixels constantly took so much CPU in 2015, but I'm guessing it was forcing redraws or something. Note that this was on an rMBP with integrated graphics if that matters.
- leejoramo 11y ago
  I looked for the "continuously-fading cursor plugin" but found nothing. Is this built-in or an add-on?

stymaar 11y ago

> BBEdit and SublimeText never tax the CPU unless I am working with extremely large files […] it really need to get the resource utilization under control Neither does Atom for most users. It's not just n problem of «resource utilization», you're clearly facing a bug … Maybe you should consider submitting an issue (https://github.com/atom/atom/issues https://github.com/atom/atom/issues)

leejoramo 11y ago
I see a number of current CPU related issues for Atom. I will look into using the performance diagnostic tools and see if I can contribute any new insights. Again, I am see the issues on admittedly rather heavily customized workhorse MacBook (lots of Unix level tweets), AND on my stock Mac Mini. So I don't think this is a case isolated to just me.
- leejoramo 11y ago
  As noted in this thread, I solved my problem, and filed an issue: https://github.com/atom/atom/issues/10421 https://github.com/atom/atom/issues/10421

fuzzywalrus 11y ago

Atom Helper sometimes gets a mind of its own and runs rampant on the CPU, sometimes eating 100% of a single core even an i7 2015 MacBook Pro. Quiting Atom doesn't seem to stop Atom helper. It takes firing up the Activity Monitor and quitting them. It's ugly but it works.

seanp2k2 11y ago

I've had this happen too. For me, disabling a continuously-fading cursor plugin stopped most of my troubles with high CPU. Still kind of ridiculous that to animate the color on a few dozen pixels constantly took so much CPU in 2015, but I'm guessing it was forcing redraws or something. Note that this was on an rMBP with integrated graphics if that matters.

leejoramo 11y ago
I looked for the "continuously-fading cursor plugin" but found nothing. Is this built-in or an add-on?