-
Notifications
You must be signed in to change notification settings - Fork 4
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
SublimeText locking up #11
Comments
Hi @jeffdeville, right now I'm in a "almost non-internet" country. But if you use prints you could see in the terminal, or write your own logger in Python you should be able to log to a file. I will try to check this problem any way. Cheers |
Thanks for checking in, @edelvalle. No rush. I do have some new info. The problem is that elixir_sense itself seems to be crashing. If I kill that process, sublime comes back. (Now maybe the processes are linked, and I'm still wrong). Nevertheless, killing the process lets me look at the console. Which... I didn't dig through yesterday because I had a release. But now that I know how to collect more info, I'll hopefully be able to help at least diagnose the cause more completely. |
|
I think the "Broken pipe" is where I killed elixir_sense. |
Yes, right now it works in blocking mode. |
any update on this issue? Its very annoying. I'm getting lockups every 10 - 30 minutes. |
I'm getting hard lockups in sublime. If there's a rhyme or reason for what is triggering them, I haven't managed to identify it yet. I'll just be typing, and then beach ball. I suppose the most likely case is a crash on linting, because I've had it crash when I switch to my browser, and can't get back to sublime.
I've cloned master into my plugins directory, but haven't played with sublime plugins much. Is there a way to write the log output to a file instead of the console (that I can't see)? If so, any best practices for helping debug? (I realize I haven't given much to go on)
The text was updated successfully, but these errors were encountered: