Be aware that glib has it's own allocation and deallocation functions which may
keep destroyed widgets or other data structures around in a memory pool, so the
OS may think your program is using memory but it's just glib's memory pool.
That memory would still be still "is use" (has references t
On 12/18/06, Fernando Apesteguía <[EMAIL PROTECTED]> wrote:
> > executing... There are no problems (no errors or warnings) during
> > compilation and valgrind, with: -v --leak-check=full doesn't show any
> > problems of my code.
>
> OK, after the application reached 7.3 MB it went down (according t
On 12/18/06, Fernando Apesteguía <[EMAIL PROTECTED]> wrote:
> Hello list!
>
> I'm developing a gtk application. The point is that I see in Gnome
> System Monitor that my application (a loop that continuously read a
> file and update data in the window) is eating more memory as it is
> executing...
Hello list!
I'm developing a gtk application. The point is that I see in Gnome
System Monitor that my application (a loop that continuously read a
file and update data in the window) is eating more memory as it is
executing... There are no problems (no errors or warnings) during
compilation and va
