libcoral/coral — Issue #6: No tests for the destruction of objects referenced from Lua
Author: tbastos
Created: 2011-11-01 18:44:01+00:00
State: open
Labels: lua, problem

As reported by @xvaldetaro, there's a general suspicion that the Lua module may be holding references to Coral objects for longer than necessary, causing "temporary memory leaks" (there are no leaks once all modules are closed, according to valgrind).

We must thoroughly test the destruction of objects referenced from Lua.
These tests should contemplate the following scenarios:

- Objects implemented both in C++ and Lua
- Objects instantiated in C++ and passed to Lua
- Objects instantiated from Lua and passed to C++