Locks violation detected. Memory location at <address> of size <size> contains an active lock.
This break is generated if a heap allocation contains a critical section, the allocation is freed, and the critical section has not been deleted.
Lock – Critical section address
Owner - N/A
DebugInfo - N/A
Description – Memory location at <location> of size <size> contains an active lock
Trace Description - Critical Section Initialization
Check the contents of the current call stack when the heap allocation was released by selecting Break on the Verifier Stop Message. Check the critical section initialization stack trace in the Tool Window.
Frequency of this error is high.