-
Notifications
You must be signed in to change notification settings - Fork 35
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
Atom crashing #183
Comments
I am not sure if this is related, but my Atom project window crashes when ctags successfully builds a reference to my WordPress project files. The (.tags) file produced is between 15Mb to 75Mb depending on the exclude paths I configure in the settings (I need to increase the timeout settings to be make sure ctags completes). Initially when I Rebuild the ctags symbols, the session runs fine and I am able to goto delcarations, however, when I restart Atom, the project window crashes and I have to close (only) this window, delete the .tags file, and reopen my project to get it to work again. |
Same issue here, large ctags file causes Atom to crash on opening. |
I'm seeing this problem too. I had a flail around disabling various plugins and eventually worked out that it was Disabling the plugin fixed it. Annoyingly, I forgot to backup the My
And a crash report: Atom Helper_2017-07-17-114552_three-headed-monkey.crash.txt |
i should mention my ctags file was fairly large was well, 100+MB |
Version 1.23.3 of atom still crashed with ctags .tags file not fitting to atom-ctags crashed with this format, which vim can handle quite well
atom-ctags did not crash with
i.e.
This is the extended format according to http://ctags.sourceforge.net/FORMAT. atom-ctags seems not to consider the pattern, It is no good, that atom crashes, though. It would also be great if the pattern could be considered. |
Crashed when generating a 32 MB file. |
This has worked fine for me up until recently but now it crashes on the same codebase I have been using it on. My Atom and plugin should be fully up to date. Not sure exactly what the issue is. Disappointed to have to stop using it but no choice currently.
The text was updated successfully, but these errors were encountered: