What problem does it solve? Investigating memory leaks in VS Code requires manually repeating UI workflows, capturing heap snapshots, and verifying that the scenario actually ran — a slow, error-prone process. This Skill automates launching Code OSS, driving repeatable scenarios, sampling renderer memory, and producing verifiable evidence so leaks can be diagnosed and fixed. ## Core Features & Use Cases - Checked-in automation runners: Run multi-turn Chat memory smoke tests or chat-session-switching scenarios that launch Code OSS via Playwright over CDP, send prompts, sample heap, and write summary.json plus screenshots. - Targeted heap snapshot capture: Take labeled .heapsnapshot files at warmed-up baseline and later iterations instead of snapshotting every sample, keeping runs fast and comparable. - Verification before analysis: Inspect summary.json, chat turn counts, and screenshots to confirm the scenario actually executed before handing snapshots to heap-snapshot-analysis. - Fix-and-verify loop: Root-cause leaks with git blame and lifecycle tracing, patch product code, rerun the identical scenario, and compare like-for-like memory trends. - Use Case: A user suspects the Chat view leaks memory across turns. Run the chat-memory-smoke runner with 8 iterations and two snapshot labels, compare the snapshots, identify a growing service map, fix the disposal logic, and rerun to confirm flat memory. ## Quick Start Ask the agent to run the bundled Chat memory smoke runner with a few iterations and no heap snapshots to verify the scenario works end to end.
