> I got rid of the previous crash, but still there is something causing > memory corruption according to the "free"-function with debugging > builds. My code calls Lua incremental GC during execution, so > I guess I maybe more sensitive for these, but this is of course > good so that the bugs don't stay hidden. >
SetColAttr and related functions seem also be part of the problem, and IncRef makes the symptoms less, but these functions also contain a call to wxluaO_undeletegcobject so I guess I should need to understand more of wxLua internals... Also using IncRef here is propably not ok in case the same Attribute set is used on multiple colums/rows, although a minor memory leak is not the worst thing now. (I have been using IncRef so that the wxWidget object does not get destroyed when the Lua object is garbage collected, after the wxWidget-object has been given to the custody of some other object) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
