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
crash in python when exiting vim #495
Comments
LLVM doesn't like when there's an error on writing to stdout or stderr while exiting and aborts. This typically happens when one of those streams is prematurely closed or the disk it's writing to is full. |
We redirect ycmd std output and error descriptors to point to log files. We delete these during some part of shutdown (can't remember the details). So there might be a race condition here between the log files getting deleted and libclang writing stuff to stderr. What I'm curious about is why is libclang writing anything to stderr... |
@mellery451 Do you still get crashes with latest ycmd? |
@micbou - I do not see the crash on exit anymore. I'm not sure exactly when this got resolved, but it seems like sometime in June/July perhaps? |
Then I think this can be closed. We can reopen it if it happens again. 👍 |
We changed the way the server shuts down in July so it could be that. |
I'm getting a python crash upon exiting vim pretty consistently - I'd say about 90% of the time I exit vim I see a crash like this. I'm pasting the OSX crash info, although I realize it's not super helpful. One other tidbit, it seems like there is an element of time involved here. If I just open vim and edit one file, it doesn't happen. I have to leave it open for some (X) amount of time, where X is > 5 minutes maybe ? I'm not sure if some background operation is timing out that leads to this eventual crash on exit, but I think time is somehow involved here - with admittedly very thin evidence to support this claim.
If there is anything else I can do to help repro, please let me know. Thanks.
The text was updated successfully, but these errors were encountered: