Feature request: Support attaching from .Net Library in native application

Hello!

First of, DotMemory looks amazing, I'd love to utilize it in my Unity3D project, as it suffers from one or more memory leaks. 

Which brings me to the following request; could you support attaching or manually recording snapshots from a .NET runtime library that's loaded through a native application? 

The .NET framework version of Unity I'm using is .NET 4.x and I've tried loading in dotMemory's API and SelfApi packages through Nuget but I wasn't able to record a snapshot or attach to dotMemory. 

 

With kind regards,

Eamon

5 comments
Comment actions Permalink

Hello,

Thank you for your feedback.

Currently, dotMemory doesn't support Unity profiling and we don't have such plans for now. You're welcome to vote and comment related ticket in our tracker: https://youtrack.jetbrains.com/issue/DMRY-7706

0
Comment actions Permalink

Hi Anna,

Thanks for the quick response.


Do you know if there's any plans on supporting profiling generic .NET libraries (loaded in through a native, or non C# app) that's no related to Unity? Or do you think dotMemory can not get enough runtime information from the .NET Library's AppDomain?

0
Comment actions Permalink

dotMemory is able to profile .NET code started from native code, simple examples: IIS, Visual Studio process (devenv.exe). Or do you mean anything else?

0
Comment actions Permalink

Oh I'm sorry, I am confused then why dotMemory would be able to attach to .NET code but not Mono.

I can see dotTrace is able to (however limited) to attach to Mono/Unity apps, are the mono capabilities so broken that it can not perform a simple memory overview (ignoring the more advanced features of dotMemory)?

 

0
Comment actions Permalink

> Oh I'm sorry, I am confused then why dotMemory would be able to attach to .NET code but not Mono.

Attach to mono is not implemented in dotMemory. Most likely it is technically possible, but has not been researched for now. .NET 4.x Equivalent (used by Unity) and .NET Framework are not the same and additional changes are needed in the profiler core to support this.

0

Please sign in to leave a comment.