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
x/tools/gopls: cache panic inheriting destroyed handle #41415
Comments
I'm very open to suggestions on how to improve the error message, but this is fundamentally very tricky stuff :-/ Did this happen as you exited an editor? My best guess is that we tried to deal with a |
Any metadata describing the handle would be a start. Given how few distinct handles we have, perhaps this could be threaded through. From our analysis, we think this was in the s.packages loop of |
Change https://golang.org/cl/255357 mentions this issue: |
gopls uses a lot of keys that are just strings, which print without any type information. Include the type of the key explicitly. Updates golang/go#41415. Change-Id: I01cfc685184e7b44c1f562b6536f173da5ae4830 Reviewed-on: https://go-review.googlesource.com/c/tools/+/255357 Trust: Heschi Kreinick <heschi@google.com> Reviewed-by: Robert Findley <rfindley@google.com>
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Based on the fact that we haven't seen this in a month (as far as I know), I think I'm ok with leaving it closed. |
Agree. I haven't noticed this since (though I have spent less time looking for panics lately). Since we don't have anything actionable here, let's leave it closed until it reoccurs. |
FWIW, I just saw this again:
Same symptoms as last time. Unfortunately nvim deleted the logs, since they were in the nvim tmpdir... |
Also from DidClose. I still suspect this has to do with editor shutdown but still would need a log to investigate. |
I believe this was fixed by CL 367675. |
Just got a concerning panic from the generational cache:
panic: inheriting destroyed handle "bf90d6e270fcf98967555c6a0aba69594d7e60ab389281fa22a86d7efcbcbe3e" into generation v12/1291
This is running in daemon mode. I'm sure this is less likely to occur in standalone mode.
Logs were not revealing, but I have them if we think they'd be useful.
Perhaps a reasonable action would be to improve the error message above to make this easier to diagnose.
cc @heschik @stamblerre
The text was updated successfully, but these errors were encountered: