Re: Tracking down memory leaks

[Bastian Bense <bastibense@gmail.com>]

Hi,

in REALbasic this can have two causes:

The first one is circular references - that is two objects that
somehow hold references to each other, so that the garbage collector
can not delete those objects from memory. For this you can use the
Runtime object and get yourself a list of allocated objects in the
current runtime.

The second cause can be a "real" memory leak, either caused by a
Plugin or by REALbasic itself. For this you might have some luck with
Valgrind, which is a memory leak checker. You could also try
commenting out code that you added/modified recently and see if the
leak disappears.

Anyway - good luck with hunting it down - I know how much pain it can be.


2009/3/31 Paul Mulroney <pmulroney@logicaldevelopments.com.au>:
> Hi Everyone,
>
> I've written a graphing program that records information from an ethernet
> based temperature probe, and graphs it in a window.  I wrote the graphing
> routine from scratch, and it's basically a NewPicture(), with a bunch of
> lines, dots and text added.
>
> I've noticed in the latest version that there's a memory leak - the
> application progressively uses up more and more memory over time.  This is
> in Windows XP.
>
> It only happens when the graph window (where I create the picture) is open,
> and not at any other time.
>
> Can anyone offer some suggestions about how I might be able to track down
> this memory leak?


-- 
Best regards,
Bastian Bense

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>