Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Suggestion: use GLAD for memory diagnostics.
See original GitHub issueAs Maoni Stephens just announced, the GLAD is available as open source and it’s looks like it’s going to support .net core. Sadly there’s no nuget package, but I’ve created issue for it.
Long story short, the GLAD is a subset of perfiew tool API that uses ETW and provides info about GCs, allocations and much more.
This should simplify the MemoryDiagnoser’s code and should enable more diagnosers in future (in fact, anything that can be analysed by perfView, disk IO and JIT events as example).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My understanding is that other than a slightly higher level C# object model, the main thing that the GLAD API gives you is more info about GC pauses. If you just use the Trace Event parser you have to do the calculations yourself, as I did in my post Visualising the .NET Garbage Collector
So I agree with @goldshtn, I’m not sure what this buys us over what we already have, but I probably need to look at GLAD a bit more to see where it differs from TraceEvents CLR parser?
AFAIK most of this stuff is natively available in TraceEvent’s CLR parser.