Freezes on build 3065
Opened this issue · 23 comments
Whenever I type something that would trigger the code complete suggestions, the editor freezes. Can't do anything else but to force kill it.
I can confirm this. It seems to me that attempting to use any T3S feature causes an immediate freeze of the editor.
Same here. Anyone know if a previous build works?
With 3059 it works, the freeze is introduced with the new sublime build.
Hi,
Is there any fix yet for Sublime build 3065, concerning this issue?
Cheers,
i'll try to take a look but i don't have much time these days to work on the plugin
I totally understand - time is always a problem - but, unfortunately, in the meantime the plugin is almost impossible to use.
@liviuignat No autocomplete or edit on mobile.
We have the same problem here. I hope you can fix this soon :)
same problem here, running it on fedora 21 FYI
Btw, same problem with the latest 3066 build
Last update from my side - seems that the current dev branch is working, at least for now.
Hi, I too looked into this problem, and I noted that sublime freezes while communicating with tss. I am using Debian Jessie is anyone wonder.
If I kill the node process, sublime continue as nothing has happens. It does not seem to be a problem to start the tss node process it is only the process communication that errors (freeze).
Maybe the fact that sublime 3065 compiles using python 3.3.3 could be a hint ? Hope this can help fixing it.
I have this same problem.
+1
I have the same problem:
- Mac OS X 10.9.5
- Sublime Text 3 build 3065
I could temporarily solve it by switching to the dev
branch.
The problem remains if I am using linux for version 3066 (dev), so this may be fixed for Mac but still not fixed on linux.
It would be nice to know if the python version included contains some kind of network error (it freezes while talking to tss)
@mathieumg After some initial git learning problems I ended up cloning your changes, and that stopped the freezing problem in my sublime 3066, thanks.
I will try to use this for some time to see if other errors occur, but for now it looks good.
Thanks for your nice improvements !
@mathieumg Sorry ... of cause not, instead thanks to @Phaiax, but it is at very nice rewrite of the plugin, I hope to see this in this main repos soon. But thanks for pointing in the right direction :-)