AppLuaRuntime Memory Issue

[GoogleCodeExporter]

What steps will reproduce the problem?
----------------------------------------------
1. Compile and run the default AppLuaRuntime application (which loads & runs 
Test1.lua)
2. Wait until the application loads the scene and starts up
3. Exit the application

What is the expected output? What do you see instead?
----------------------------------------------
The expected outcome (in the debug logs) is to see the basic shutdown sequence 
of instructions. instead the shutdown sequence shows there is two pointers 
being freed incorrectly according to the malloc check (the "Camera" & "Lamp" 
gkGameObject instances).

What version of GameKit? On what operating system?
----------------------------------------------
Latest version of GameKit (r975) on Mac OSX (10.6.8). Given the issue (deletion 
of objects that exist in the scene throwing an error), I doubt the operating 
system is at fault though.

Please provide any additional information below.
----------------------------------------------
I am not sure exactly what is causing the issue, but the pointers are 
referencing real objects as their resource name variables have valid values. It 
could be a double delete (i.e. trying to free the object more than once) or it 
could be that the pointer being deleted is not actually the exact pointer that 
was allocated (i.e. the delete is occurring on a pointer generated from a 
virtual class cast).

I can do more tests if given an area to look into, but right now it's "needle 
in a haystack" for me.

Original issue reported on code.google.com by BenT.Sol...@gmail.com on 5 Aug 2011 at 7:12

[GoogleCodeExporter]

The called loadBlendFile() has a issue in Test1.lua. 
--self:loadBlendFile("Test2.blend");

Thanks for reporting.

Original comment by harkon...@gmail.com on 7 Aug 2011 at 3:59

• Changed state: Accepted

[GoogleCodeExporter]

Can you try my patch at issue #207 (called DoubleFree_fix.patch) and let me 
know if it fixes it for you? (Duplicating comment here in case someone else 
arrives to this issue)

Original comment by vek...@gmail.com on 7 Jan 2012 at 10:52

[GoogleCodeExporter]

Is this bug still valid? I do not experience reported problems in the current 
version (r1090). Both output and logs do not show any incorrectly freed 
pointers.

Original comment by martin.f...@gmail.com on 16 Jun 2012 at 12:44

[GoogleCodeExporter]

Yes I think this was fixed when my patch was applied in r1013 as documented in 
issue #207.

Original comment by vek...@gmail.com on 16 Jun 2012 at 5:59

[GoogleCodeExporter]

Closing this.

Original comment by kungfoobar@gmail.com on 18 Jun 2012 at 3:38

• Changed state: Fixed