You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
When a big complex folder is added as an project folder (such as your home directory, please do not tell me that I shouldn't add home as a project folder, because atom atomatically add it when I am editing files in home.), and start to do something (the fuzzy-finder package is enabled but not using its function such as via ctrl-t), run top or other system monitor, you'll see always one core is being used 100%, and let the fan runs, battery is used quickly.
I am sure it's fuzzy-finder's problem because after open atom as safe mode, the problems still there. And after disabling fuzzy-finder, the cpu usage become normal.
It's strange why it cause this even the function is not being used.
Steps to Reproduce
Added a big and complex project folder such as your home.
Open atom with fuzzy finder enabled, but don't use it, just leave enabled.
Open top or other system monitor and see a BEAUTIFUL CPU usage as one core nearly fully loaded, and also the fully-loaded core may be change to other core!
Expected behavior: A normal cpu usage which is always under 10%.
Actual behavior: Always one core was loaded nearly 100%.
Prerequisites
Description
When a big complex folder is added as an project folder (such as your home directory, please do not tell me that I shouldn't add home as a project folder, because atom atomatically add it when I am editing files in home.), and start to do something (the fuzzy-finder package is enabled but not using its function such as via ctrl-t), run top or other system monitor, you'll see always one core is being used 100%, and let the fan runs, battery is used quickly.
I am sure it's fuzzy-finder's problem because after open atom as safe mode, the problems still there. And after disabling fuzzy-finder, the cpu usage become normal.
It's strange why it cause this even the function is not being used.
Steps to Reproduce
Expected behavior: A normal cpu usage which is always under 10%.
Actual behavior: Always one core was loaded nearly 100%.
Reproduces how often: Nearly every time I did so.
Versions
Output of
$ atom --version
:Output of
$ apm --version
:Output of
$ uname -a
:Additional Information
Pictures of enabling fuzzy finder:
Pictures after disabling it:
The text was updated successfully, but these errors were encountered: