<div dir="ltr">Thanks. Unfortunately I don't use Linux or OS X, and it doesn't seem like there are too many easy Windows alternatives.<div><br><br><div class="gmail_quote">On Wed, Mar 3, 2010 at 9:19 PM, Johannes Schickel <span dir="ltr"><<a href="mailto:lordhoto@scummvm.org">lordhoto@scummvm.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">yotam barnoy wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I don't really know the tools to do this measurement properly (other than some hacks that could take a while), but using Process Explorer on Windows, it seems like several of the engines are no longer cleaning up after themselves properly. Scumm may be the worst offender (CoMI itself for instance) but possibly also Teen Agent and some others.<br>
</blockquote>
<br></div>
It should be pretty easy to use valgrind (<a href="http://valgrind.org/" target="_blank">http://valgrind.org/</a>) on x86 or amd64 Linux or Intel OS X (I think it works nowadays on that too) to do memory leak checking. It also features a nice output including call-stack for the leak allocations.<br>
<font color="#888888">
<br>
// Johannes<br>
<br>
</font></blockquote></div><br></div></div>