Unable to start profiling. Profiler attach failed (HRESULT: 0x80131379)

I am trying to start profiling a dot process on linux, and got below error  "[Undefined resource string ID:0x7379] (0x80131379)"


root@online-trainer-c39e944184354dbdb1834b36e66c0f38-fd7b95866-v9vk9:/app/dotMemoryTool# ./dotmemory get-snapshot 7
Performs memory profiling of .NET applications

Found 1 process(es):
[7] dotnet

Attaching to [7] dotnet runtime...
[Undefined resource string ID:0x7379] (0x80131379)
Can't set event mask: unknown error (hresult_error:80131379)
Unable to start profiling. Profiler attach failed (HRESULT: 0x80131379)

Comment actions Permalink


What Linux version do you use? Also please enter 'lscpu' command to get info about CPU.

Comment actions Permalink

This is a kubernetes pod running on Auzre VM.  This issue seems randomly happen on some pod but not others. 

output of cat /etc/os-release:
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION="10 (buster)"


Output of lscpu:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 16
On-line CPU(s) list: 0-15
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz
Stepping: 7
CPU MHz: 2593.906
BogoMIPS: 5187.81
Virtualization: VT-x
Hypervisor vendor: Microsoft
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
L3 cache: 36608K
NUMA node0 CPU(s): 0-15
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 cpuid pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single tpr_shadow vnmi ept vpid ept_ad fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx512_vnni md_clear arch_capabilities

Comment actions Permalink

Thank you for information.

Profiler core calls attach method with arguments including 2 minutes timeout. This method is executed in dotnet code and waits for the concurrent garbage collector to turn off. Attach can't be completed while concurrent GC mode is enabled.

0x80131379 is 'CORPROF_E_TIMEOUT_WAITING_FOR_CONCURRENT_GC' error. It means that something prevented GC mode switching. It could be a long GC or the process was suspended or in "not responding" state or something else.

Could you please provide more information about your site? Do you have any ideas what could be the reason for such a delay? Could the process be suspended, for example, due to migration to another pod at this moment? 

Comment actions Permalink

Thanks Anna, when this happens,  the process is running on the pod without a problem, and I tried several times, it always got this error.   CPU usage was low (around 2 cores) and we allocated 6 cores to the pod.  Memory usage was around 30G but we allocated 60G to the pod.  When this happens, I did notice the pod running slow, meaning it processing data slowly and that was why I tried to get a dump, trying to help troubleshoot.   I think if GC was busy and caused it to be slow, we should see CPU busy, right? 

Comment actions Permalink

Is there any way to increase this timeout value?  When this error happened, it happened quickly after I ran the command (several seconds), it didn't wait for 2 minutes

Comment actions Permalink

What dotnet version is targeted by your application? How much of these 30GB is used by your application?


Please sign in to leave a comment.