mkajdas.mkprod wrote:
>> mkajdas.mkprod wrote:
>>> I think I found a potential memory leak in Fl_Help_View.
>>> ..
>>> I noticed that my memory usage increases by almost 1 MB
>>> per each page displayed.
>> I can verify this with the 1.1.x test/help program
>> on fedora3.
>>
>> Ya, seems to get bigger ~1M per new page visited.
>
> This seems to be a more generic problem.
> I experience memory leak also when generating Fl_Double_Window in memory with
> just a few widgets for the purpose of dumping it to the printer.
> Everytime I create and print this image, my available memory decreases
> significantly.
> This has nothing to do with Fl_Help_View itself, I think.
> Fl_Double_Window maybe?
This sounds like a different issue, possibly unrelated to
fltk.
When you say 'create and print', what steps are involved?
Are you taking a screenshot with an external tool, or using
fltk's printing support?
What approach are you using to detect 'available memory'?
To identify a memory leak in an app, if using linux, look at
the RSIZE/VSIZE from a 'ps aux' report, or the VIRT/RES fields
in top(1) to see if they're growing,
But if you're looking at the machine's actual available memory,
don't, as that's not a good indicator of leaking so much as
it is just viewing the odd dynamics of disk caching and memory
interaction, which is not useful, as many OS's try to use available
memory for disk caching.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk