-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
server-d process stuck in endless loop #336
Comments
It may be a problem with sublime text, i'll try to reproduce the freeze again and check sublime's log And i'll try with vscode as well |
I think it might not be stuck in an endless loop, but rather takes a very long time to process the source code - do you have any complex things such as very nested code or very long code? You would need to find out the file in which this loop started happening to better resolve it. You may not immediately notice it if you don't keep an eye on the serve-d status all the time. I'll add a rough optimization step that will filter out all |
parsing code is sometimes synchronous, so if it is taking a very long time, it would also hang up all LSP communication. In case of highlighting related things, parsing code is synchronous. |
I don't think it's slow, i left it for few minutes and still no response, main thread definitely is frozen and stuck on libdparse code |
anyway I optimized some code here to avoid such deep AST visits, try out serve-d master |
It froze again with your commit.. i suspect problem might be in workspace-d In this while loop: serve-d/workspace-d/source/workspaced/com/dcdext.d Lines 2188 to 2272 in a5929bb
That's at least where the debugger says it stopped at
Stuck appending some tokens then dunno where it goes |
I disabled syntax check with: I'll try to debug this further an other day, i am to finish this project i am working on for this week |
I found the part of my code that trigger the freeze, i'll try to reduce the code so i can share it (can't share the whole thing since it's private) |
I'm not sure what causes it exactly, but in my project, after a while, serve-d becomes stuck and eat CPU
After i managed to attach a debugger and here are 2 call stacks from 2 runs:
A different one after a retry:
The text was updated successfully, but these errors were encountered: