I have a customer who is developing an application for the MC9590 (WM6.5 - BSP37) series devices and is using our Imaging API (EMDK for .NET v2.5). They state they are experiencing a memory leak ("they eventually get a program memory low error") however, they are unable to reproduce this issue using just our imager simply (isolating our code). Attached are eMscript logs customer generated while experiencing the memory leak using their customer developed software (MobileFrame). Can anyone explain what may be the cause of the memory leak based on these logs? Possible theory was that it was a problem with memory fragmentation (lost clusters?). Can anyone take analyze these logs and come to any conclusions based on them?
Memory Map Analysis - eMscript logs memory leak// Expert user has replied. |
5 Replies
The format of the attached 'eMscript.zip' is not recognized by WinZip, 7zip or gzip.
These logs show a leak in what appears to be a customer application. We typically tell customers to use logging or memory tracking tools to drill down on this. Microsoft's application verifier has been shown to be pretty good at tracking memory leaks. Hope this helps.
These logs show a leak in what appears to be a customer application. We typically tell customers to use logging or memory tracking tools to drill down on this. Microsoft's application verifier has been shown to be pretty good at tracking memory leaks. Hope this helps.
Attached logs
Marc Kurath has also supplied me with a word doc (view) of the eMscript logs for visual representation. "MobileFrameClient.exe" is the name of the customers application which makes use of our Imager API If anyone can derive any conclusions from the supplied info (relating to possible memory leak/lookup/etc), it would be much appreciated.