-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High memory usage in Atom 1.18 beta #308
Comments
Same here. 😢 macOS 10.12.5 |
I have the same problem on Windows 7. |
same here |
It leaves my system out of memory with a certain project folder too. |
Also confirmed on my system. Fresh Atom install with only pigments running. Node and Electron are both up-to-date with the Arch/AUR repos. |
Same here on 0.39.1 and Atom 1.18.0-beta0. When Pigments is enabled it will boost an Atom Helper Process to CPU loads constantly higher than 100% and high RAM usage after opening a single file, no matter what type. I'm on a Macbook / MacOS 10.12.3. |
In the latest beta version, the problem seems to have stopped occurring. macOS 10.12.5 |
Not sure what caused it, but I'm glad it's solved. |
I'm on the latest beta build [1.18.0-beta2] and still experiencing the massive memory issues on Win10. |
Is there any update on the progress of this? 1.18 is now the stable release of Atom and this still is not resolved, rendering Pigments entirely unusable. |
+1 |
I like the concept of Pigments, but in its' current state it makes ATOM unstable (and in my case, causes it to freeze outright). |
Closing in favour of the master post. |
Originally reported here: atom/atom#14436
In Atom
1.18
(currently beta), having a few files open and then enabling this package seems to use a lot of RAM (some GBs).Console shows:
Might be related to adding snapshots atom/atom#13916, but not sure.
The text was updated successfully, but these errors were encountered: