Discussion Forum for .NET Memory Profiler

Hi, The internal .NET Memory Profiler API, the NmpCore task, and the NmpDataCollector are available as NuGet packages (SciTech.MemProfilerApi, SciTech.NmpCore.Task, SciTech.NmpDataCollector), but then snapshots can only be collected from within the profiled process. The external API, that allows you...

Yes, we plan to add support for .NET Core applications running on Linux. In version 6.0, both .NET Memory Profiler and NmpCore will be running as .NET Core applications (or more likely .NET 5 applications). The profiler itself uses WPF so it will be be Windows only, but NmpCore will be cross platfor...

I think we are meaning the same thing. I was also talking about getting a list of instances that existed in snapshot #1 and no longer exist in snapshot #2. The "Removed instances" value does represent the number of these instances. However, if you look at the type details, you will not get a list wi...

It is currently not possible to get a list of garbage collected instances, but we're actually working on a feature that will make this possible. It's a four-way compare of snapshots, from up to two different sessions. With this comparison, full instance information will be available for two differen...

The instance graph shows that you have an XmlDocument that is kept alive through the X_Doc field of a Lokal_bon instance. As long as you intend to use the data in the XmlDocument again this is not a memory leak. And since the Local_bon instance is referenced be a method (Send_the_rest) it seems like...

The current version of .NET Memory Profiler does not provide timing information for garbage collections. (Garbage collection timing and other performance data will be included in version 6.0 of the profiler). The count on the y-axis in the screenshot represents the number of garbage collections. In ...

To retrieve analysis issues from a comparison you need to run the comparison analyzer. The analyzer is run by calling AnalyseComparison on the comparison. THis method returns an AnalysisResult which can be used when investigating issues. The code below shows how warning and error issues can be print...

1. To attach to a running process using the API you need to specify the profiling type "Attach" and the id of the process to attach to. The code below shows how you can attach to a process using the API. static void Main(string[] args) { int processId = 21284; // Id of process ProfilerApplicationCor...

A registration key for a new trial has been sent to your e-mail.

Thank you very much and I really appreciate your effort. It's a bit embarrassing that I missed that Namespace could return null, I just assumed that it would return an empty string in case there's no namespace (the documentation clearly states that null will be returned). I have now fixed this issue...

That's really strange. Can your provide the call stack of the exception?

The "Item ... is not available" message is just an informational message and should not affect anything. The "Operation is not valid due to the current state of the object" error is a bug that we have fixed in the upcoming maintenance release of .NET Memory Profiler. It's a bit surprising that it oc...

I'm sorry for the delay. We have been working on the maintenance release of .NET Memory Profiler 5.6, with support for Visual Studio 2019. Now we have built a new version and we will probably release it in the beginning of the next week. Unfortunately, we have not been able to find a solution for th...

Thanks for the information. At the moment I don't know how this can occur. We will investigate this further and see if we can come up with an explanation/fix. I will get back to this thread as soon as we have some more information.

Your code looks fine. I don't understand how you can get a NullReferenceException when performing your assertions. We have investigated the API code and added a few more null-checks, but as far as I can see they should not be necessary. Anyway, can you test with the latest build of the profiler API?...