Open cbuschardt opened 8 years ago
I just tested with a nearly 900MB tags file and it's working fine so maybe it depends on more than just the plugin. My config is Linux Min 17.3 64-bit with 16GB of RAM (no swap).
I have a 58M tag file. How long does it take to be able to find the definitions? I keep getting 'symbol not found'. Have been able to use this well on a smaller project.
I also have this issue with a 1.15 gb .tags file. Not sure how to get more information on the cause of the crash. Atom 1.8.0.
This seems to be a duplicate of #147 .
I also have the same issue with a 456M .tags file. But it's not systematic. I'm using atom 1.11 and the latest version of this plugin.
I am facing the same issue with .tags files as small as 15Mb in size on Atom 1.15.0. Anyone knows if there is a way to increase the Atom memory limit? I have a 16Gb ram on this machine and still it crashes the window only (not the entire atom session)
I'm on Atom 1.32.2 on MacOS and having this issue just recently. I have this in my project:
-rw-r--r-- 1 lacoste staff 1.6G Nov 20 17:20 .tags
-rw-r--r-- 1 lacoste staff 857M Nov 20 17:40 .tags_swap
And when all hell breaks loose, I get upto 10 or more ctags processes using massive cpu. I'm gonna remove try to remove the .tags_swap
and see how it goes. I also cleaned out a bunch of junk from /tmp
and /logs
though I wouldn't imagine that should break anything.
Any other ideas how to fix this please???
Should I install atom-ctags package? I removed it not that long ago when I installed https://atom.io/packages/atom-codesearch which was not very straight foward to install, but provides a super fast full code search in my large projects. The only other change was that I recently tried out vscode and found it was VERY slow when I first opened my project but then sped up after a few minutes.
I tried removing the .tags file, but it is recreated the instance, I start a project wide search.
What would be a solution for this?
I enabled ctags for a medium sized project.
The editor full on crashes the moment the project loads. I suspect the problem is that internally this plugin is loading the entire .tags file into a buffer. Typically editors like vim support tags by binary searching on the text log file. The .tags file in question is approximately 1G. This is a 64-bit system with >8GB of RAM [plus swap].