> > I know for fact that the synedits get destroyed. At least last time I > worked on it, the did get destroyed, so unless there is a > real huge new > bug.... > If the SynEdits get destroyed, then the textbuffers get > destroyed too, > including the strings containing the text (one string per > line, and I am > pretty sure no other part of the IDE has a ref count on any of them.) > > So the memory is probably available, but due to > fragmentation, and small > pieces still being allocated, it can't be returned to the OS. > > > Clearly you haven't looked at the valgrind massif data I posted earlier. They clearly show that a lot of data is staying in memory. It'll require a lot of digging to figure out exactly where the problems are. One I found out is that synedit creates an image list with gutter symbols for every page! That adds up to 3 M for the 450 file, which apparenltly aren't released when closing the page. An other one is in zlib when reading lfm resources (there aren't any in the 450 tes files afaik). Another few meg's hanging around.
Ludo -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus