On Friday 18 February 2005 16:23, Dave Andruczyk wrote:
> Anyone know of any good tools to find out where memory is either 1.
> leaking, or 2. excessively allocated?
>
> I've tried valgrind but it slows things down so much as to make it
> completely unusable.. Aside from eating memory like mad, i
I have my GTK+ app and have recently changed a portion to use GLIB's GArray for
dynamic storage, the arrays are created as a glfoat with 4096 elements by
default. About 30 times per second my app reads some data from a device and
tacks it onto the array (g_array_append)
I'm finding my applicati
