search for: swigdirector_wxbitmap

...00 in ?? () Cannot access memory at address 0x81800100 Cannot access memory at address 0x81800100 #1 0x031d82b4 in wxBitmapRefData::Free() () #2 0x031d831c in wxBitmapRefData::~wxBitmapRefData() () #3 0x031bc450 in wxObject::UnRef() () #4 0x031d87a0 in wxBitmap::~wxBitmap() () #5 0x02e17ad0 in SwigDirector_wxBitmap::~SwigDirector_wxBitmap() () #6 0x0001d6f0 in rb_gc_call_finalizer_at_exit () at gc.c:1858 #7 0x000041d4 in ruby_finalize_1 () at eval.c:1418 #8 0x00004340 in ruby_cleanup (ex=0) at eval.c:1453 #9 0x000044b8 in ruby_stop (ex=105048432) at eval.c:1484 #10 0x00004544 in ruby_run () at eval.c:1505...

I see that this problem was noted a while ago (http://rubyforge.org/ tracker/index.php?func=detail&aid=251&group_id=35&atid=218) but it seems not to have received much attention. Any chance that it will be looked at anytime soon? So far, I prefer wxRuby to Ruby/Tk because of that closer coupling with the native window manager. However, the memory leak is just murdering me.