Narrated, with original music and captions. The whole loop on the Storefront demo, recorded in VS Code: Track Memory, the leak suspects, the retention graph, the fix typed in, then a second run. Fast-forwarded stretches are marked on screen.

Screen recording: fixing a C# memory leak in VS Code with the SharpLsp memory profiler, from leak suspects to the retention graph and a verified fix

Name: Screen recording: fixing a C# memory leak in VS Code with the SharpLsp memory profiler, from leak suspects to the retention graph and a verified fix
Uploaded: 2026-10-19T00:06:17+11:00
Duration: 1 min 32 s
Description: Narrated, with original music and captions. The whole loop on the Storefront demo, recorded in VS Code: Track Memory, the leak suspects, the retention graph, the fix typed in, then a second run. Fast-forwarded stretches are marked on screen.

Read the guide: How to Fix a Memory Leak in C# and .NET

Transcript

This is Storefront, a C# app whose memory keeps climbing. Track Memory on its process, right from VS Code.

SharpLsp snapshots the heap every ten seconds, and the heap keeps growing.

Leak suspects rank by consistent growth. CustomerSession climbs in every snapshot. Click it, and you jump to its code.

So, what's keeping those sessions alive?

The reference graph walks up to the root: a static dictionary that remembers every order, and never forgets one.

The fix: keep the last thousand orders, and evict the oldest as each new one arrives.

Rebuild, run it again, and track memory once more.

This time the heap holds steady, and no suspect climbs past Low. The leak is found, fixed, and proven, without leaving your editor.