How to interpret core dump analysis result of ASP.NET Core application

Posted on by faz_business


We collected a core dump of our productive ASP.NET Core application using dotnet-dump collect -p <PID>.

Loading it into Visual Studio and running diagnostic analysis revealed some interesting stuff. However, two of the analysis results I’m not sure how to investigate further:

AA0013 Multiple exceptions were found on the heap

enter image description here

Clicking on one of the message shows some exception details:

enter image description here

The exception details do not contain stack traces, so I have no idea, where these exceptions are coming from.

Question: how can I troubleshoot this further? Why don’t I see any stack traces? Do I need to collect the core dump in a different way in order to get more details?

AA0003 Finalizer Queue may be blocked and cause high memory usage

enter image description here

Here I don’t see any useful details.

Question: how can I troubleshoot the root cause of this further?

Leave a Reply

Your email address will not be published. Required fields are marked *