Telling GC Lag from a Memory Leak in .NET — A Practical Procedure for Observing, Comparing, and Proving Memory Growth (archived 2026-09-01)
A procedure for determining whether growing memory in a .NET application is simply waiting on garbage collection or a genuine memory leak, using dotnet-counters, dotnet-gcdump, and dotnet-dump. Archived version of https://comcomponent.com/en/blog/2026/06/09/000-dotnet-gc-or-memory-leak/, as published on 2026-09-01. The live article is maintained and may change after this date. First published 2026-06-09.
Authors
- Go Komura (ORCID: https://orcid.org/0009-0008-8895-8390)
Institutions
- Fujikura (United States) (US)
Publication Details
- Journal
- Zenodo (CERN European Organization for Nuclear Research)
- Published
- 2026-09-01
- DOI
- https://doi.org/10.5281/zenodo.21614660
- Primary Topic
- Digital and Cyber Forensics
- Type
- article
- Field-Weighted Citation Impact
- 0.00