Export (0) Print
Expand All

Released Virtual Memory Containing An Active Lock

Application Verifier stop message

Locks violation detected. The region of virtual memory at <location> of size <size> contains an active lock.

Probable cause

This stop is generated if the current thread is calling VirtualFree on a memory block that contains an active critical section. The application should call DeleteCriticalSection on this critical section before if frees this memory.

Information displayed by Application Verifier in Tool Window

Lock – Critical section address

Owner – N/A

DebugInfo – N/A

Description - The region of virtual memory at <location> of size <size> contains an active lock

Trace Description – Critical Section Initialization

Additional information

The call stack in the tool window shows where the critical section was initialized.

Check the current call stack where the virtual memory is released using VirtualFree. The probable culprit is the module that calls VirtualFree.

This stop does not occur in Windows XP.

Frequency of this error is low.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft