<story><title>Atom text editor 1.4 released</title><url>https://github.com/atom/atom/releases/tag/v1.4.0</url></story><parent_chain><item><author>leejoramo</author><text>I continue to want to like Atom, and I try it out several times a year. Just updated, and see that it still has big performance problems on my system. I currently have BBEdit and SublimeText open for real work, and these are apps the have been running for days.&lt;p&gt;Here 100% would represent full usage of a CPU core:&lt;p&gt;BBEdit:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    15 files open (various types&amp;#x2F;sizes)
    76MB RAM 
    &amp;lt; 2% CPU
    1 process
    25MB app disk space
&lt;/code&gt;&lt;/pre&gt;
SublimeText:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    10 files open (various types&amp;#x2F;sizes)
    169 RAM
    &amp;lt; 2% CPU
    1 process
    27MB app disk space
&lt;/code&gt;&lt;/pre&gt;
Atom&lt;p&gt;&lt;pre&gt;&lt;code&gt;    1 small Markdown file open 
    &amp;gt; 1.2GB RAM !!!!!!
    &amp;gt; 85% CPU 
    7 processes
    205MB app disk space
&lt;/code&gt;&lt;/pre&gt;
Just sitting in the background I am seeing Atom&amp;#x27;s CPU and RAM usages fluctuate wildly. The numbers above are the LOWEST I observed.&lt;p&gt;I will spend a little time looking into why this is happening. I certainly could be related to some add-on package that I have installed, but I don&amp;#x27;t every recall seeing BBEdit or SublimeText behave so poorly with all of the customizations I have thrown at them.&lt;p&gt;Update: added disk space for base app. Even with a 500GB SSD, Atom would make me think about its value vs space usage.&lt;p&gt;Update 2: the system specs. 2011 MacBook Pro 13-inch, 2.3GHz i5, 500GB SSD, 16GB RAM, OS X 10.11.2&lt;p&gt;Update 3: performed a clean reinstall of Atom, removed all third party packages, removed preference files, disabled Markdown preview. Atom is still using over 80% cpu and greater than 1GB RAM with one short markdown file open</text></item></parent_chain><comment><author>leejoramo</author><text>SOLUTION to high CPU!&lt;p&gt;Well, I kept digging and ultimately found a very long running issue thread[1] that mentioned having a &lt;i&gt;.git&lt;/i&gt; directory in your home directory can cause high CPU.&lt;p&gt;Removing the three year old and accidentally created ~&amp;#x2F;.git directory and restarting Atom fixed the problem.&lt;p&gt;So now I will give Atom a deep new look.&lt;p&gt;Still, I am a bit perplexed, this is an issue that has been reported for nearly two years, and has not been fixed. I am not sure about the technical nature of the problem, but I think Atom, is trying to digest my entire 340GB home directory. Assuming that this is desired behavior, there should be at least a warning at launch about the issue. I am sure that MANY people have accidental ~&amp;#x2F;.git folders, and have a bad experience with Atom. At the vary least, it should not have taken me a couple hours of digging to find a solution buried in a GitHub issue.&lt;p&gt;While this fixes the issue on my MacBook, I am not sure about the Mac Mini, which I don&amp;#x27;t think will have a .git directory, but I will check later tonight.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;atom&amp;#x2F;atom&amp;#x2F;issues&amp;#x2F;3426#issuecomment-119780457&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;atom&amp;#x2F;atom&amp;#x2F;issues&amp;#x2F;3426#issuecomment-119780...&lt;/a&gt;</text></comment>
<story><title>Atom text editor 1.4 released</title><url>https://github.com/atom/atom/releases/tag/v1.4.0</url></story><parent_chain><item><author>leejoramo</author><text>I continue to want to like Atom, and I try it out several times a year. Just updated, and see that it still has big performance problems on my system. I currently have BBEdit and SublimeText open for real work, and these are apps the have been running for days.&lt;p&gt;Here 100% would represent full usage of a CPU core:&lt;p&gt;BBEdit:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    15 files open (various types&amp;#x2F;sizes)
    76MB RAM 
    &amp;lt; 2% CPU
    1 process
    25MB app disk space
&lt;/code&gt;&lt;/pre&gt;
SublimeText:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    10 files open (various types&amp;#x2F;sizes)
    169 RAM
    &amp;lt; 2% CPU
    1 process
    27MB app disk space
&lt;/code&gt;&lt;/pre&gt;
Atom&lt;p&gt;&lt;pre&gt;&lt;code&gt;    1 small Markdown file open 
    &amp;gt; 1.2GB RAM !!!!!!
    &amp;gt; 85% CPU 
    7 processes
    205MB app disk space
&lt;/code&gt;&lt;/pre&gt;
Just sitting in the background I am seeing Atom&amp;#x27;s CPU and RAM usages fluctuate wildly. The numbers above are the LOWEST I observed.&lt;p&gt;I will spend a little time looking into why this is happening. I certainly could be related to some add-on package that I have installed, but I don&amp;#x27;t every recall seeing BBEdit or SublimeText behave so poorly with all of the customizations I have thrown at them.&lt;p&gt;Update: added disk space for base app. Even with a 500GB SSD, Atom would make me think about its value vs space usage.&lt;p&gt;Update 2: the system specs. 2011 MacBook Pro 13-inch, 2.3GHz i5, 500GB SSD, 16GB RAM, OS X 10.11.2&lt;p&gt;Update 3: performed a clean reinstall of Atom, removed all third party packages, removed preference files, disabled Markdown preview. Atom is still using over 80% cpu and greater than 1GB RAM with one short markdown file open</text></item></parent_chain><comment><author>stymaar</author><text>Of course Atom is not the lightest editor out there but your figures are really strange: I&amp;#x27;m using atom for one year now with dozens of installed plugin, currently working with more than 10 files opened at the same time with an up-time of 17days and I&amp;#x27;ve never seen anything like you&lt;i&gt;.&lt;p&gt;&lt;/i&gt;except one notorious bug when trying to open minified javascript files of hundred kB.&lt;p&gt;That&amp;#x27;s weird to have such a difference performance-wise between users, because it&amp;#x27;s based on chromium which does not suffer plateform specific performance drops I think.&lt;p&gt;Do you have issues with Google Chrome also ?</text></comment>