Greg Ercolano wrote:
> One thing to watch out for when looking at the OS's free memory..
> just because free(3) is called doesn't mean it gets reclaimed by the OS.
Sounds like the above is not relevant in your case; I missed the part
where you mentioned the available memory decreases /each time/ you create
and print an image. That certainly would indicate a leak, vs. the above
caching behavior where memory would simply 'hover' when the operation was
repeated.
Would you agree it is something not freeing in the screen printing code,
and nothing to do with Fl_Double_Window's normal "non-printing" operations?
Not many people use the printing/screen grabbing functions, so it's likely
something specific with that.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
