Bitmap memory leaks (Bug 251)?

Evan Light wrote:
> I see that this problem was noted a while ago 
> (http://rubyforge.org/
tracker/index.php?func=detail&aid=251&group_id=35&am
p;atid=218 
> <http://rubyforge.
org/tracker/index.php?func=detail&aid=251&group_id=3
5&atid=218>) 
> but it seems not to have received much attention.
Don't know about the other devs, but I'd forgotten this bug
mentioned 
any specific issue rather than 'we should check for memory
leaks'.

Bugs related to over-eager SWIG/Ruby memory management have
had higher 
priority because they cause segfaults. SWIG/Ruby was pretty

underdeveloped when this bug was created, but features added
since 
should make it a lot easier to reclaim objects that have
fallen out of 
scope.
> Any chance that it will be looked at anytime soon?  
Yes. Thanks for the report. Since Bitmap is such a widely
used class 
that we should try and fix this specific one for the
upcoming 0.40 release.

Generally, please do file leaking classes as specific bugs,
ideally with 
code samples.
> Unfortunately, I cannot merely load and cache bitmaps
easily as I am 
> modifying them (drawing text on them) at run time. 
While I could 
> cache the unique bitmaps with the drawn text, it seemed
more of a 
> nuisance than it was worth.
wxRuby should definitely be doing the work, not you.

Are you using MemoryDC?

alex
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users