Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Atom Editor Not Responding #9185

Closed
erinjerri opened this issue Oct 17, 2015 · 14 comments
Closed

Atom Editor Not Responding #9185

erinjerri opened this issue Oct 17, 2015 · 14 comments

Comments

@erinjerri
Copy link

I checked my Utilities and it is taking up so much energy, I haven't been able to code in it for a while and keep having this error pop-up.

image

@erinjerri
Copy link
Author

I don't have that issue with input lag, it just won't load. =(

On Sat, Oct 17, 2015 at 3:05 AM, Paweł Ciechomski notifications@github.com
wrote:

When editor is responding have you something like "input lag" when typing?
Because I have similar issue on Linux - Editor takes much more resources
than earlier, I can't type because editor has big input lag and switching
between tabs takes more than 10 seconds. Maybe mine issue is related to
yours.


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

Erin Jerri
http://www.erinjerri.com

@methodbox
Copy link

You should read over #3426 to see if your issue is related.

@nathansobo
Copy link
Contributor

Can you try running atom --safe and seeing if this still happens?

@markgarrigan
Copy link

This happens to me about every 10 minutes maybe more after the first time it happens. I have no packages installed and nothing custom. It's a fresh install of atom. Atom 1.3.2. OS X 10.11.2

@kexoth
Copy link

kexoth commented Mar 31, 2016

I'm having the same issue, tried the advice in /issues/9185, to delete the uneccessary files from ~/.atom/storage but it appears again & again ..

@lee-dohm
Copy link
Contributor

@erinjerri Are you still having this Issue? Did atom --safe help?

@lee-dohm
Copy link
Contributor

For others, can you replicate the issue using atom --safe?

@kexoth
Copy link

kexoth commented Mar 31, 2016

Right now I'm using Atom with --safe flag & it's fine, but still, this shouldn't happen 😞

@lee-dohm
Copy link
Contributor

If the problem doesn't reproduce with atom --safe that means the issue is with a community package you have installed. Some people have had good luck with using the package-cop package to track these problems down.

We all agree that this shouldn't happen and we're looking into ways to mitigate these kinds of problems with runaway packages. Until that time though, there are ways to track down the root cause and get the information to the package maintainers so they can fix the issue.

@sompylasar
Copy link

Looks related: #10378

@alexniver
Copy link

#7581 this helps me work out. delete .atom/storage works for me

@Ben3eeE
Copy link
Contributor

Ben3eeE commented Dec 21, 2016

Thank you for reaching out!

Because this doesn't reproduce in Safe Mode, it would seem that what you're reporting isn't being caused by Atom itself but by a community package you have installed. It may be that there is still a bug in Atom. If so, we'll need the maintainer of the package that is causing the problem to help track that down.

What we need you to do is to figure out what community package is causing the problem. Some people have reported that using the package-cop package has been helpful, you may want to try it. Once you've determined what package is causing the problem, The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme so you can file this issue there.

@Ben3eeE Ben3eeE closed this as completed Dec 21, 2016
@karankashyap
Copy link

atom --clear-window-state works!
From #12983 (comment)

@lock
Copy link

lock bot commented Apr 2, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked and limited conversation to collaborators Apr 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants