DotMemory - error calling ./ get-snapshot on linux "Unable to start profiling. Profiler attach failed (HRESULT: 0x8013136A)"

I'm trying to use DotMemory on a .net core 3.1 app running in Docker in Kubernetes.  The docker file is based on


I get the following

./ get-snapshot 13
Performs memory profiling of .NET applications

Found 1 process(es):
[13] dotnet

Attaching to [13] dotnet runtime...
Unable to start profiling. Profiler attach failed (HRESULT: 0x8013136A).

Can anyone help me with this error

Results from running lscpu

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
Stepping: 4
CPU MHz: 2500.000
BogoMIPS: 5000.00
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
L3 cache: 33792K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single kaiser fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke


Comment actions Permalink


This message means that another profiler, performance monitoring tool or mocking tool is attached to your process. Please detach another tool or try to restart your process.

What dotMemory version do you use? dotMemory console should display more user friendly message since 2021.1 version:

Comment actions Permalink

Yes that was the issue.  Found we have a newrelic profiler auto attaching to our processes.  I'm not sure what version I was using, I re-downloaded the latest profiler zip and I see a better error message.



Please sign in to leave a comment.