InitializeCriticalSection (Compact 2013)
This function initializes a critical section object.
The threads of a single process can use a critical section object for mutual-exclusion synchronization. Although there is no guarantee about the order in which threads will obtain ownership of the critical section, the system will process ownership requests from all threads.
The process is responsible for allocating the memory used by a critical section object, which it can do by declaring a variable of type CRITICAL_SECTION. Before using a critical section, some thread of the process must call the InitializeCriticalSection function to initialize the object.
Once a critical section object has been initialized, the threads of the process can specify the object in the EnterCriticalSection or LeaveCriticalSection function to provide mutually exclusive access to a shared resource. For similar synchronization between the threads of different processes, use a mutex object.
A critical section object cannot be moved or copied. The process must also not modify the object, but must treat it as logically opaque. Use only the critical section functions provided by the Microsoft Win32® API to manage critical section objects.
In low-memory situations, InitializeCriticalSection can raise a STATUS_NO_MEMORY exception.
Each object type, such as memory maps, semaphores, events, message queues, mutexes, and watchdog timers, has its own separate namespace. Empty strings, "", are handled as named objects. On Windows desktop-based platforms, synchronization objects all share the same namespace.
Do not use uncached memory for critical sections, as this is not compatible with multi-processor systems.