<p dir="auto">I've been writing a custom debug adapter for vscode and have been running into the following issue:</p>
<p dir="auto">When deploying your extension in server mode ( at least I haven't tested on extension host mode ), and the you drop stop the client abruptly, for any reason, whilst the front-end is still awaiting a request that affects the variables debug view, then even after the client has stopped, whatever values were in the view remain there and become locked. Starting a new debug session does not clear them, you have to open a new window with the project in order for them to clear.</p>
<p dir="auto">These screenshots illustrate :</p>
<blockquote>
<p dir="auto">While debugging on the client, at the same time I have the adapter project being debugger on server mode, and paused while there is still a scopesRequest or variablesRequest response unfulfilled.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/11462418/13276706/90a40976-da98-11e5-94ec-646f19645ef0.gif"><img src="https://cloud.githubusercontent.com/assets/11462418/13276706/90a40976-da98-11e5-94ec-646f19645ef0.gif" width="600" data-animated-image="" style="max-width: 100%;"></a></p>
<p dir="auto">I've stopped the server without completing the request. The client's variables view remains locked with whatever was last in it.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/11462418/13276707/924df264-da98-11e5-810d-954ccbb5765e.gif"><img src="https://cloud.githubusercontent.com/assets/11462418/13276707/924df264-da98-11e5-810d-954ccbb5765e.gif" width="600" data-animated-image="" style="max-width: 100%;"></a></p>
</blockquote>
<p dir="auto">It's happened both in the January and insider's build.</p>
<p dir="auto">Whenever there is a long running debug adapter request and a spinner appears in the UI, this spinner does not disappear when the session is terminated (in fact the full variables viewlet does not disappear in this case). Since starting a new debug session does not work in this situation, only a window reload helps.</p>