100% CPU when opening a project or 'Settings > Packages'

[joecritch]

Hey, I've got no other packages activated inside of Atom, and after installing nuclide-installer package, I'm getting a 100% CPU. This is also happening when I try to view the Packages list inside of Atom, so I can't uninstall using the Prefs screen.

A brief issue, as I'm unfamiliar with the reporting process, but please let me know what information you require.

[bolinfest]

Are you on Windows, Mac, or Linux? Anything else about your system that might be special?

[joecritch]

.@bolinfest Mac, OS X Yosemite. My atom settings are symlinked, in the style of https://github.com/holman/dotfiles. Interestingly, the CPU still caps when I run atom with $ atom --safe. If you can point me to where I need to go, perhaps I can do some CPU profiling?

[Sterbic]

Same issue here on OS X 10.10.3 and Atom 0.211.0.

I installed nuclide through apm and now Atom Helper and npm max out their thread each time I start Atom. Loading the packages view in the settings tab take a few minutes.

After the first restart I had only 6 nuclide-* packages installed, after the second restart I see 9 packages so Atom Helper might be doing useful work. I still don't see some packages like nuclide-quick-open.

[bolinfest]

The nuclide-installer package goes through and runs apm install for each package in https://github.com/facebooknuclideapm/nuclide-installer/blob/master/lib/config.json. We're getting some reports that this is very, very slow. I'm also checking with GitHub to see if there's anything on their end that could be contributing to this.

[bolinfest]

You could experiment with installing each package through Atom's GUI to see if the behavior is any different. I need to dig into the code in settings-view to see if anything extra special happens there.

[Sterbic]

I am trying to uninstall everything through Atom's GUI but it's extremely slow and unresponsive. I will try a fresh install through the GUI and from source to check if there is any difference.

[bolinfest]

If you backup your ~/.atom/packages directory, that's the easiest way to remove all of your packages.

[Sterbic]

Even uninstalling a single package after disabling it takes several minutes and Atom Helper goes 100%. Shouldn't this be as fast as rm -r pkg_dir?

Building from source with ./scripts/dev/setup does solve the issue.

START INSTALL: 2015-06-24 01:17:17.482524
...
FINISH INSTALL: 2015-06-24 01:19:34.594759
PackageManager.install() took 137 seconds.

Now it takes less than 10 seconds to start Atom and load all packages, including 13 nuclide-* packages.

[Sterbic]

When installed from source, uninstalling through the GUI is almost instant as expected.

This is probably an issue with Atom and not directly nuclide: only the first uninstalled package is removed from the current search of installed packages, the other packages stay listed until I enter a different search term although they are not present in ~/.atom/packages any more.

[Sterbic]

I tried to install nuclide-installer through Atom's GUI and monitor the progress through
ls ~/.atom/packages/. It took about 40 minutes to complete, but the 100% cpu issue is still there.

This is probably a wild guess, is there any chance Atom treats differently symlinked and normal packages?

[mauriciord]

Same problem for me. Installing with ./scripts/dev/setup is perfect now, but i want the apm install nuclide-installer.
Did you tried sudo apm install nuclide-installer ?

[Sterbic]

I will give it a try, but I doubt it will make any difference. EDIT: no difference

[grabbou]

Just to add few more bits, I've tried installing both from Atom and from apm. Neither of them completed successfully as the Atom UI was just frozen. Afraid of the high CPU temperature for a few minutes, I've decided to build from source. The installation has finished w/o any problems, and all the components were there, but the whole UI was full of lags and the CPU usage was still as high as during the installation process. Decided to remove all the packages by using apm as the editor was completely unusable.

Atom 1.0, OS X Yosemite (10.10.3), Macbook Pro Early 2015

[klvnptr]

Same here. "Atom Helper" is running on 100% CPU on OS X 10.10.3.

[zacharytamas]

Same here. Atom is basically unusable right now. Major lag: I can finish a whole line of code before it actually appears on screen. I'm having to remove the packages one by one with apm just to restore it well enough to actually work today. OS X 10.10.3

[kaizhang]

Same here. OS X 10.10.3.

[samueloph]

I have a dirty workaround for this bug:
It looks like removing atom and all its config. files resolves the problem [of course, making a new clean installation later].

rm -r .atom/
rm -r .config/Atom
rm .atom
rm -r /root/.atom/

You can check the proper atom's bug report here:
atom/settings-view#555.

[mauriciord]

I removed atom and its config several times, and i made a new clean installation later.
Didn’t work for me.

Now i will try do the same with the new Atom 1.0.

EDIT: Same thing with the new Atom 1.0

[chibipirate]

Try apm uninstall * for any nuclide package you see. That seemed to do the trick for me. Keep in mind that I have yet to reinstall Nuclide.

[samueloph]

@chibipirate Could you confirm if reinstalling Nuclide didn't make atom crash again? I'm starting to think this problem is related to Nuclide, considering the number of people that are participating in the settings-view's bug report.

I reinstalled nuclide here and atom started to crash again.

[rpedroni]

Same here on OS X 10.10.3. I really do believe this is nuclide related since this has only happened after installation. For me, opening the settings panel starts the havoc

Edit: definitely nuclide related. Deleting all nuclide packages from ~/.atom/packages fixes the cpu use

[cesarandreu]

+1

After installing Nuclide, opening my settings shoots up CPU usage.

[admmasters]

Same. Only happening with Nuclide. Unusable for 5 or minutes after starting the app.

[gothy]

AtomHelper per opened window consumes 100% CPU even after closing the "Settings" tab. Waiting for more than 5minutes now...
MacOS X Yosemite.

Removing all nuclide packages helps.

[sglyon]

Seeing this also -- posting so I'm notified of new comments

[despairblue]

@spencerlyon2 there is a subscribe button on the right 😉

[AndreaCatalucci]

+1, atom1.2.4 on el capitan

[nowaits]

+1, atom1.3.0beta6 on El Capitan

[ck3mp3r]

Hi, having the same issue (El Capitan, Atom 1.2.4), had to manually remove all nuclide packages from my ~/.atom/packages directory.
Just as a note, emptying the recycle bin after showed over 250k files being deleted... npm goodness? Yes, my recycle bin was empty before I binned the nuclide packages...

What version are you using internally if it's not behaving this way?

[cbrwizard]

+1, editor becomes unusable on my mac after installing nuclide - 104% CPU

[jadedevin13]

+1

[adrice727]

+1

[lbennett-stacki]

+1 atom1.2.4 on El Capitan

@bolinfest has highlighted the need to integrate a batch package download and install api in the official atom repo, has anyone followed this up with an issue on the atom repo? Lastly, has anyone started on a pr?

[lukeed]

Would it make sense to have nuclide just be a fork of Atom, instead of a layer on top of it?

Still allow apm to run on nuclide, just restructure whatever needs restructuring internally, including the NPM module de-duping.

Shrug -- early morning fog rants...

[plrthink]

same problem here

[mauriciord]

I stopped using Nuclide because of this, I'm just using JSX React Snippets
for Atom and other individually, not the created by Facebook.
Working for me this way.
I hope it helps, thanks.

Atenciosamente,
Maurício R. Duarte.

2015-12-07 8:43 GMT-02:00 Perry Poon [email protected]:

same problem here

—
Reply to this email directly or view it on GitHub
#84 (comment).

[lbennett-stacki]

@lukeed - I know what you're getting at, forking Atom would mean that those interested in the nuclide behemoth of a package can focus purely on redesigning and redeveloping its infrastructure to perfectly suit nuclides needs. Personally however, I believe nuclide could benefit from the wider Atom community if it stayed as purely an abstraction package for Atom. Additionally, Atom could benefit from nuclide as the nuclide community helps Atom become more suitable and stable for larger package suites.

Maybe something that should be looked into is the fact that actually the nuclide package in whole is a bit too much and seems to target a very specific use case/user story. In my opinion, I would love to see the 'nuclide installer' as the root Atom package, from there it is an abstracted settings and package management panel purely for the nuclide packages. You could reply "Well... you can just directly download the packages you want and only them" but this is a problem of accessibility and usability and I believe that could be of benefit. This is just my opinion, of course there is potential for this to be a very stupid opinion.

[ssorallen]

In my opinion, I would love to see the 'nuclide installer' as the root Atom package, from there it is an abstracted settings and package management panel purely for the nuclide packages.

@LukeeeeBennett, stay tuned. We have been exploring that direction to address the many valid critiques of the current approach that make Nuclide difficult to install and update. More updates when we've got something to show.

[adamsoffer]

+1

[Dids]

I can verify that manually installing Nuclide from source doesn't cause any of these issues.

[eendeego]

Manually installing from source works for me too~~, but now I've got either one or two tree views. 😝~~

[lukeed]

How are you installing from source? The readme no longer contains those instructions. And after finding them in the readme's history, running scripts/dev/setup didn't do anything except npm install

[mauriciord]

Clone the source $ git clone https://github.com/facebook/nuclide.git

$ cd nuclide

Install dependencies $ npm install # Link the 'nuclide' package to Atom's

package directory $ apm link

Atenciosamente,
Maurício R. Duarte.

2015-12-29 21:26 GMT-02:00 Luke Edwards [email protected]:

How are you installing from source? The readme no longer contains those
instructions. And after finding them in the readme's history, running
scripts/dev/setup didn't do anything except npm install

—
Reply to this email directly or view it on GitHub
#84 (comment).

[lukeed]

@mauriciord gotcha, thanks!

[mostafaeweda]

This should have been fixed with the UP release, http://nuclide.io/blog/2016/01/13/Nuclide-v0.111.0-The-Unified-Package/

[dmythro]

Finally! Checked, works as expected, all good.

[mauriciord]

Finally working ! Thanks

[v3ss0n]

There is 100% IO usage when settings is Open and Nuclided is installed. It spawns about 4-5 watchman processes that takes 100% I/O . Latest nuclide.

[mostafaeweda]

@v3ss0n are you using the latest Atom? We are currently fine at Atom 1.6.2.
However, there is a known issue (pending fix) with Atom >= 1.7 that causes such CPU spike.

[v3ss0n]

i am with atom 1.7 +

[mostafaeweda]

the fix will be out in ~ 2 days

[eworkflow]

My Atom started crashing on its startup. After booting it in the safe mode (atom --safe) I attempted to uninstall all the Nuclide packages but most of them resulted in the Atom uninstalling errors. When deleting the related directories manually, I noticed that some of the "Nuclide-*" directories have obscene sizes such as ~80MB. I fear that the "hacking" packages got hacked themselves unless there is another explanation for this. In any case, only after a manual delete of these directories, I was able to orderly delete Nuclide packages in Atom.