Closed jrieken closed 7 years ago
Hi,
Thanks for reporting the bug! Now the change callbacks are using vscode.window.activeTextEditor (and some null checks) to avoid this issue, however I can't think of a case where this could happen.
Hopefully this will fix the problem for you, but it is still interesting!
I see this error a lot in production and when developing extensions it makes the debugger always break there...