[Lazarus] RE : RE : RE : RE : RE : RE : RE : RE : Console AppDevelopment

[Ludo Brands]

As for why memory returned to memory manager, does not get back to the OS
(apparently not even when using cmem...) no idea. But memory is definitely
returned to the mem manager.

As for the issue Ludo reported with QT, and requiring even a reset of his
system. *IF* any handles or other resources of the widgetset (not the
lazarus part, but the actual QT or GTK lib or w32) are leaked, then it needs
to be traced. (btw there were people with issues on win98, so it could be).
But such leaks, would be necessarily be likely to be noticeable as huge
memory consumers.
 
 

Got also further on Qt: Lazarus compiled with cmem running outside valgrind
doesn't grow the memory used doing multiple load/unload of the 450 files.
Memory doesn't drop at all when closing files (same on gtk2 using cmem), but
there is no increase. The memory increase and the related pthread memory
problem seems to be linked to running inside valgrind massif with the
--pages-as-heap=yes option. One of the side-effects is that all the memory
that top marks as VIRT is taken into account, including shared with other
processes. The hint came from a trace on the GTK2 machine where a very big
chunk of pthread memory was allocated by arena.c which is a memory pool
library. 
The problem with QFileSystemWatcher spawning threads is apparently a known
problem: https://bugreports.qt.nokia.com//browse/QTBUG-20028
 
Ludo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20110816/fd1112c9/attachment-0003.html>