research on CMultiLock vs CSingleLock class
- CMultiLock Class
- CSingleLock Class
- Microsoft KB Archive/151033
- Formatted MessageBox/AfxMessageBox
- Determine Information about System, User, Processes, Hardware...
- Explicating the new C++ standard (C++0x), and its implementation in VC10
- The Practical Guide to Multithreading - Part 1
- The Practical Guide to Multithreading - Part 2
- Simple Multithreaded Application in pure C, Win32 and MFC
- Thread Synchronization for Beginners
- Synchronization in Multithreaded Applications with MFC
- MFC Thread Synchronization using SYNCHRONIZED macro
- Automatic thread synchronization - Exception based class library
- How to create a Simple Lock Framework for C++ Synchronization
- EpiLibrary ::Visual C++ Utility Library
- https://github.com/juhgiyo/EpLibrary
If the CMultiLock class is used to synchronize on more than eight synchronization objects, a memory leak occurs when using CEvent, CSemaphore, or CMutex as the synchronization objects. The size of the leak equals the number of synchronization objects used multiplied by the memory needed for a BOOL variable.
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ 32- bit Edition version 4.2.
This article explains how to create your own simple Lock Framework for C++ synchronization.
lock framework is good to use
No comments:
Post a Comment