FIX: Calling GetMsgInfo() in Zetafax COM API results in memory leak Print ZTN1906 ID: ZTN1906 This Zetafax technical note applies to: Zetafax 2012 and earlier Symptom Calling the GetMsgInfo() function in the COM API results in a memory leak in the calling application. The more often the call is made, the bigger the leak. If the call is made in a tight loop from a test application, for a large number of messages with attachments, then memory usage can grow from 2MB to around 150MB until the calling application is restarted. Cause This was due to some memory resources not being cleanly released in some related functions in the Zetafax COM API layer. Resolution This issue has been resolved in the Zetafax 2012 Platform Feature Pack, available for download here. This update is available free of charge to existing Software Assuancre customers and can be accessed using the password provided in your Software Assurance newsletter. For more details on gaining access to this password email: support@equisys.com. Status This fault was corrected in the Zetafax 2012 Platform Feature Pack Last updated: 26th November 2012 (NT/MW) Keywords: Zetafax COM API GetMsgInfo memory leak