resource-leak-audit

To find IDisposable misuse and resource leaks in C# .NET code, apply a two-phase audit methodology with forward and backward searches to locate disposal-site issues. This scan validates findings against disposal patterns across changed files or a full codebase.

Common .NET resource leak patterns include CancellationTokenSource lifecycle issues, buffer pool mismanagement, missing event unsubscriptions, and static leaks. A pattern-driven discovery audit surfaces these actionable findings for risk assessment and remediation.

To audit a pull request for CancellationTokenSource lifecycle issues, run a PR-mode audit to scan changed C# files. The workflow follows forward and backward analyses to locate CTS leaks and validates findings against disposal patterns.

This resource leak audit works on both a full codebase and changed PR files. You can run the PR-mode audit to scan only changed C# files or apply the two-phase methodology across the entire project to locate IDisposable misuse.

The .NET resource leak audit validates findings by checking disposal-site patterns using forward and backward searches. This two-phase methodology ensures located IDisposable and CancellationTokenSource leaks are actionable before triage and risk assessment.

The best way to triage and fix .NET memory management leaks is to use a structured triage and risk assessment workflow that provides clear ownership and remediation guidance for the identified IDisposable and CTS lifecycle issues.