Many developers have experienced an annoying behavior while debugging in Visual Studio that leads to force termination of debugging session. The LoderLock was detected error popped up while debugging application in Visual Studio IDE. It will be a very expensive task for a developer to reinitiate the entire debug activity and re-test once again. In this article we will see how to avoid this exception in order to continue with smooth debugging.
What is the Error?
The loader Lock exception is displayed when the step-through debugging (F10/F11) in progress. This exception is displayed from managed debugging assistants and makes the user force terminate the debugging session when this kind of exception occurred.
LoderLock was detected error in Visual Stodio:
Basically, the system runs the code in DllMain inside a lock (synchronization lock). Therefore, running non-trivial code inside DllMain is “asking for a deadlock”. For more details please read the article here.
Please follow the below steps to avoid loader lock exceptions from your debugging environment.
– Article ends here –