Atom often becomes no response


#1

Atom often becomes no response with the Atom Helper thread take High CPU usage.

When this problem happen, i can’t do any thing on atom. The only thing i can do is to kill the atom thread and restart it.

My colleagues also meet this problem. And we find that when switch file between two deep directory and big file, this problem will more easily come out.
For exapme:
-src
–B
—C
----D
-----E
------F
–H
—I
----J
-----K
------L
if i open L and i want to open F, atom will easily becomes no response.

And i have try following ways to resolve this problem, but they are not helpful.

  1. –save mode.
  2. mv ~/.atom/packages ~/.atom/packages_backup
  3. rm -rf compile-cache/
  4. rm -rf storage
  5. reinstall atom
  6. use atom 1.3.3

Atom version: 1.3.2
OS: OS X 10.10.4
Language: Node.js


#2

Have you followed the suggestions in the Debugging document? Also, could you give the following information?

  • What OS and version are you running?
  • Can you reproduce the issue after completely exiting Atom and restarting using atom --safe?
  • Can you try updating to the latest version of Atom?
  • Are your files on a network drive?

#3

I have updated my issue.


#4

This sounds like “two files with the same name but different paths” problem. Try updating to the latest version of Atom, v1.4.0, which has a fix for this.


#5

OK, i will try 1.4.0. Thx