KDevelop holding on to large chunks of memory

[Nick Savoiu]

> On 18.01.07 09:34:53, Nick Savoiu wrote:
> > >> I have a large custom project with 1000's of
> .cpp/.h files. If I delete the .pcs file to 
> > >>force a recomputation of it then the KDevelop
> session baloons to large amount of
> > >> memory and then hangs on to them until closed.
> > >
> > >Another way would be to run kdevelop through
> valgrinds memcheck
> > > or cachegrind to find leaks.
> > 
> > I don't think these would necessarily be leaks.
> They're more of an issue of ASAP releasing of memory
> when not needed.
> 
> Well, you'd still see where kdevelops memory is
> spent so we would know
> where exactly we need to look to know how to release
> the memory.

OK. I'll pull in 3.4 in a few days and give it a spin.

Nick