Unable to start profiled application - process starts but doesn't proceed

Avatar
David Marshburn
Created

I'm having dotMemory start the process.  After 10-20 seconds, the process does appear - I can see it in Task Manager, and using maybe 3 MB memory.  However, after sitting for 10+ minutes more, nothing changes.  The process doesn't really start, the splash screen doesn't appear, and nothing else seems to happen.

I have “Sampled” allocation collection selected, “Default” process filters, and “Manually” profiling control.

I can run the application stand-alone just fine.  Also, using the same exe and parameters in dotTrace starts the application just fine.

If I start the software then try to attach, the profiled app seems to freeze, and dotMemory is reporting 0 B allocations even after running for several minutes.

It's probably been about a year since I last profiled with dotMemory.  I'm currently updated to 2025.2.

What should I be looking at, please, to get dotMemory to start/run/profile the software successfully?

Votes

0

Share

6 comments
Avatar
Anna Guseva
Created

Could you please collect logs:
 

  • Close standalone dotMemory.
  • Clear %temp%\JetLogs folder.
  • Go to dotMemory installation folder: %localappdata%\JetBrains\Installations\dotMemory[N]
  • Using Windows command-line start dotMemory with arguments: dotMemory.UI.64.exe /LogLevel=Trace
  • Start configuring a profiling session.
  • Press Ctrl+Shift+Alt+F11.
  • In the Expert options dialog window, select the Enable logs checkbox.
  • Type 3887751438631 in “Log mask” field or enable the next checkboxes: Com, Api, Bridge, Snapshot, MetaDataGt, GcCb, GcReferencesCb ,ClassGt, FieldResolverGt, ClassRecoveryGt, MemoryDumpGt, AppDomainRecoveryGt, ThreadRecoveryGt, ClassGt, GcAllocationsCb, MemoryAllocationGt
  • Click Save.
  • Run the profiling session.
  • Reproduce the issue.
  • Stop profiling session.
  • Close dotMemory.
  • Look for the logs in the 'JetLogs' folder.

Please collect logs for the both “start” and “attach” cases. You ca upload them to our ftp.

 

 

0
Avatar
David Marshburn
Created

Okay, I've uploaded two logs, one for the “start” case and one for the “attach” case.  The Upload ID is 2025_11_26_25Vt2kUiniwczrPHauB4np (same upload for both).  In both cases, I let things sit for several minutes with nothing happening and then killed the process.  In the “attach” case, I attempted to detach first, but nothing seemed to happen.

0
Avatar
Anna Guseva
Created

Hi!

Thank you for the logs.

Unfortunately, some log files are missing. Could you please send us the entire JetLogs folder?

Also, when profiling has not yet finished, please open the %temp% folder and search for files matching lgc.*.tmp. If any are present, please copy them and send them to us as well.
Please ensure that the %temp% folder is owned by the user under which your profiled application is running.

0
Avatar
David Marshburn
Created

It seems that this is a conflict with Sophos Endpoint software.  I'm following up in the support ticket about that; do you all still want more logs?

0
Avatar
Anna Guseva
Created

Hi David!

Could you please try disabling the “Monitor Domain Controller Events” option in Sophos? Does dotMemory profiling work after that?

0
Avatar
David Marshburn
Created

This issue was resolved in the 2025.3.2 release, related to this issue:

https://youtrack.jetbrains.com/issue/DMRY-13484/Memory-profiling-doesnt-start-if-ETW-for-Microsoft-Windows-RPC-provider-is-already-running

0

Please sign in to leave a comment.