FIX: Memory Leak Reported in PLEX.CPP When Using CSocket

CAUSE

The CSocket class will queue up socket notification messages while it waits for a particular socket operation to complete. These messages are stored in CPtrList (m_listSocketNotifications) on a per-thread basis. This object is destroyed when the thread-state information for that thread is cleaned-up. Unfortunately the thread-state information for the primary thread is not cleaned-up until after the memory leak detection is performed.

Because MFC does not take care to free the plex objects associated with this list before the list is destroyed, the perceived memory leak is reported.

Because the problem is related to the frequency and sequence of the socket notification messages being received, the memory leak message might not occur every time the program is executed. It might only be seen under certain circumstances.