Memory leak in MFC and other multi-threaded scan operations
Serveral memory leak conditions have been detected; in the multi-threaded MFC in v3.1 and later, and in all multi-threaded scans in v3.0 and later. This may cause a long-lived Gem session that performs these operations to increase in size.
Workaround
Periodically restart sessions performing MFCs or other multi-threaded scans.
Last updated: 2/5/15