vscode-extension-debugger

Debugging memory leaks in VS Code extensions involves using heap snapshot analysis through the Extension Host debugger to identify unreleased objects, then implementing the DisposableStore pattern to ensure proper resource cleanup and event listener disposal.

Race conditions occur when async operations complete out of order or interleave unexpectedly. Fix them by structuring async workflows sequentially, using proper error handling for promise rejections, and ensuring disposable lifecycle management prevents stale callbacks.

WebView communication failures stem from missing message handlers, timing issues, or improper serialization. Diagnose using DevTools logging, verify message routing between extension and WebView, and implement comprehensive error handling for bidirectional messages.

Systematic debugging follows structured triage: reproduce the issue, collect logs and heap snapshots, identify the root cause pattern (dispose handlers, async errors, event listeners), implement a targeted fix, and verify with regression testing.

Yes, the Extension Host debugger and DevTools reveal activation failures by tracking unhandled promise rejections, logging extension lifecycle events, and inspecting the activation context to pinpoint where initialization breaks.

Runtime crashes result from unhandled errors, resource exhaustion, or inter-extension conflicts. Trace crashes by enabling Extension Host verbose logging, analyzing stack traces, capturing heap snapshots at failure, and testing isolation from other extensions.