A Roslyn-based C# analyzer that detects explicit and implicit heap allocations like boxing, closures, and delegate creations.
Roslyn Clr Heap Allocation Analyzer is a Roslyn-based diagnostic analyzer for C# that detects both explicit and implicit heap allocations in source code. It helps developers identify performance bottlenecks caused by unnecessary memory allocations, such as boxing operations, closure allocations, and implicit delegate creations. The tool provides real-time feedback during development to optimize memory usage and reduce garbage collection overhead.
C# developers working on performance-critical applications who need to minimize heap allocations and optimize memory usage, particularly those using Visual Studio and the Roslyn compiler platform.
Developers choose this analyzer because it provides deep insight into hidden allocation patterns that traditional profiling might miss, integrates seamlessly with the Roslyn compiler and Visual Studio, and helps catch performance issues early in the development cycle before they impact production applications.
Roslyn based C# heap allocation diagnostic analyzer that can detect explicit and many implicit allocations like boxing, display classes a.k.a closures, implicit delegate creations, etc.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Detects both explicit allocations like 'new' objects and implicit ones such as boxing, closures, and delegate creations, as illustrated in the README example image.
Integrates with Visual Studio to provide inline diagnostics with visual indicators, helping developers catch allocation issues immediately during coding.
Available as a NuGet package, allowing seamless integration into CI/CD processes for automated performance checks in builds.
Leverages the Roslyn compiler for precise source code analysis, ensuring reliable detection of allocation patterns directly from the code.
The project is no longer maintained and archived, with key analyzers merged into dotnet/roslyn-analyzers, meaning no bug fixes, updates, or official support.
As an archived tool, it may not work properly with newer versions of Visual Studio or .NET frameworks, leading to potential integration failures.
Only targets C# code via Roslyn, making it unsuitable for other programming languages or non-Roslyn compilation environments.