memory profiler crashing when taking snapshot

SR_BRU

Hi
If we start our application from within the .NET memory profiler, when taking the snapshot the profiler crashes.
and
If we start the application in independent  mode, and attach the Memory profiler, then the application crash when taking the snapshot.

In both ways we are not able to analyze the memory of the application.
Logs for both cases attached.

Can you please give some suggestion on how to proceed?

robm2

For what it's worth, our application also crashes on taking a snapshot, if started from within the profiler.  If the profiler is attached after startup, however, it works for us.

Not much help I'm afraid, but possibly an additional case of the issue?

Peter_Laws

Hello SR_BRU 

Based on the logfile, it appears that the process you've launched lacks the debug permissions to perform the task. You or your administrator will need to assign your account the 'Debug programs' privileges.

If it still doesn't work after that modification, please come back to us.

SR_BRU

Hi 

Both the application and the memory profiler is started using the option "run as administrator."

SR_BRU

Peter_Laws said:

Hello SR_BRU 

Based on the logfile, it appears that the process you've launched lacks the debug permissions to perform the task. You or your administrator will need to assign your account the 'Debug programs' privileges.

If it still doesn't work after that modification, please come back to us.

Its not working, Its still the same issue.

the account itself had been given administrator privileges, and also when starting application  "run as administrator." option is used.

Peter_Laws

I'm sorry to say, this is largely out of our hands, as the logs state 'This process does not have the debug privilege' and admin privileges aren't equivalent to that policy being allowed. However if it is allowed, the remaining avenue you could explore would be to check the profiler service and see what account / privilege it's running under and elevate it.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debug-privilege

You're essentially in this scenario https://stackoverflow.com/questions/59745613/do-not-have-enough-privilege-on-visual-studio-2019-to-attach-w3p-process-on-loca

SR_BRU

Peter_Laws said:

I'm sorry to say, this is largely out of our hands, as the logs state 'This process does not have the debug privilege' and admin privileges aren't equivalent to that policy being allowed. However if it is allowed, the remaining avenue you could explore would be to check the profiler service and see what account / privilege it's running under and elevate it.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debug-privilege

You're essentially in this scenario https://stackoverflow.com/questions/59745613/do-not-have-enough-privilege-on-visual-studio-2019-to-attach-w3p-process-on-loca

Thanks for the help. But its not related to privileges I could say that hence Our application can run in 2 modes, 1 is production mode, which is a light weight mode and another is Lab mode which has full functionality. 

when running in light weight mode the Redgate can attach and work correctly. 
Only when its in lab mode the issue is there. It attaches to the exe correctly, but the issue happens when trying to take snapshot.

if the application is started from Profiler then the profiler crashes, if its attached to profiler then application crashes.

Peter_Laws

My apologies SR_BRU I hadn't understood your use case.

I'd probably approach troubleshooting this application as thought it were two separate apps given the disparity of functionality, Does your lab app have sufficient logging to identify where it's falling down?

Presumably in an area of functionality that doesn't exist in the other mode?
Lastly could you estimate the average snapshot size?