http://blogs.msdn.com/stephen_griffin/archive/2009/03/16/recognizing-mapi-allocated-memory.aspxContinuing our look at lessons learned from James’ article on the MAPI memory leak , we look at the memory that James recognized as MAPI properties. How did he figure this out? As a refresher, here’s what the memory looked like: 0:000&gt; !heap -p -aen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/stephen_griffin/archive/2009/03/16/recognizing-mapi-allocated-memory.aspx#9483690Tue, 17 Mar 2009 17:07:36 GMT91d46819-8472-40ad-a661-2c78acb4018c:9483690SGriffin's MAPI Internals<p>Digging more into lessons learned from James’ blog on analyzing memory usage (my first two articles are</p> http://blogs.msdn.com/stephen_griffin/archive/2009/03/16/recognizing-mapi-allocated-memory.aspx#9492634Fri, 20 Mar 2009 18:26:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:9492634SGriffin's MAPI Internals<p>I think this will be the last article to come from James’ post on debugging MAPI (previous posts here</p> http://blogs.msdn.com/stephen_griffin/archive/2009/03/16/recognizing-mapi-allocated-memory.aspx#9530725Fri, 03 Apr 2009 18:27:06 GMT91d46819-8472-40ad-a661-2c78acb4018c:9530725SGriffin's MAPI Internals<p>Working with a customer the other day, I went looking for my blog post discussing the fact that MAPI</p>