Serious memory leak in Gideon

[Harald Fernengel]

Hi,

On Thursday 13 February 2003 17:47, Andras Mantia wrote:
>  Recently I see a serious memory leak in Gideon. After loading the project,
> gideon uses about 49M memory. As soon as I start to type some text, the
> memory usage goes up. After entering two lines of code, now it uses 73M.
> And after all the memory and swap is consumed by Gideon, it gets killed.
> It's not funny at all. :-(

hm... I just loaded a C++ project with a persistant classstore in valgrind and 
I couldn't find any leaks.

This is the summary:

==1536== LEAK SUMMARY:
==1536==    definitely lost: 8779 bytes in 167 blocks.
==1536==    possibly lost:   223944 bytes in 506 blocks.
==1536==    still reachable: 10124131 bytes in 274107 blocks.
==1536==         suppressed: 0 bytes in 0 blocks.

The definitely lost bytes are a joke, the still reachables are some static 
members that don't get cleaned up (and aren't a leak).

Can you run

valgrind --leak-check=yes --show-reachable=yes --num-callers=40 gideon

and post the last 100 lines?

Thanks,
Harry