wxlua-users Mailing List for wxLua

Hi John,

I noticed that there is a memory leak when wxlua script checks for
non-existing properties inside pcall. For example, the following
script leaks about 5M of memory on Windows:

require "wx"
local ctrl = wx.wxTextCtrl()
for _ = 1, 10000 do pcall(function() return ctrl.foo end) end
io.read()

(if you are checking in TaskManager, you need to look for Lua process
under "background processes" section).

Adding "collectgarbage" doesn't help, so the leak seems to be in the
memory allocated outside of Lua.
"pcall" is needed to avoid "wxLua: Unable to call an unknown method
'foo' on a 'wxTextCtrl' type." If the check is for the existing
property, then there is no leak. If I cause the error in "pcall" in
some other way, there is no leak either. I don't think pcall is
causing the issue; there is probably something wrong with the cleanup
after the error.

Do you have any idea on what may be causing this? I wouldn't worry
about it too much, but there is no way to check if the property exists
without wrapping the check into a "pcall" and leaking 0.5k per check
is a bit too much.

As a side note, I'd prefer "obj.foo" check to return "nil" instead of
failing with an error. This would be a behavior consistent with how
fields behave for tables in Lua.

Paul.

Hi John,

At first, i would like to tell you how big is your works : thanks for all.

I use wxLua with wxWidget 3.0.2 since 1 year on x86 and x64 platforms on Windows 7 with no matter. Since I have jumped on Windows 10, wxLua crash on x64. Same dll, same code. I think, I have found the problem.

In file wxlstate.cpp In function

void* LUACALL wxluaT_getuserdatatype(lua_State* L, int stack_idx, int wxl_type)

             long int o = (long int)wxlua_touserdata(L, stack_idx, false);

should be changed in

             size_t o = (size_t)wxlua_touserdata(L, stack_idx, false);

on Windows platforms to avoid original pointer to be truncated in 32 bits. Why it doesn't crash since 1 year on Win7, I really don't know, probably I'm a lucky man and memory management has changed on Win10 !

I guess, it could help.

Regards,

Laurent.