Goto-definition can time out despite all device-contexts for the current device being finished (as reported in-client, at least)
Once one request times out, subsequent requests may give 'no response' instantly, before the server recovers and communication is re-established.
Likely an error either in device context reporting (the device isn't ready even though the analysis says it is) or in the request state-waits (they are waiting even though they should not be)