Use variable count to automatically detect expensive scopes

[isidorn]

Currently debugging a program with a large number of local variables simply crashes the debugger. Does the new inspector protocl let us just query for the number of variables in a scope without getting all of them. If that is possible we could automatically mark some scopes as expensive so vscode would not automatically expend them.

Here is an example repository made by @weinand

many locals.zip

[roblourens]

I don't know of a way to do that. But we should test whether the issues are with the adapter requesting the props from Node, or only from the adapter sending the response to the client.

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!