Date/Time: 2017-06-02 12:06:38.674 +0100
OS Version: Mac OS X 10.11.6 (15G1510)
Report Version: 11
Anonymous UUID: 5AEA5F9C-C165-9462-3821-0070EA562BC3
VM Regions Near 0xf0c4616c:
Stack 00000000bfffd000-00000000c0000000 [ 12K] rw-/rwx SM=COW
–>
Submap 00000000ffff0000-00000000ffff1000 [ 4K] r–/r-- SM=PRV process-only VM submap
It’s really difficult to say. Are you creating your own extension?
Since the top function in the call stack is lua_gettop, I’d look into stack related issues first.
One of the first things I’d look into is if you can see if any of your Lua functions doesn’t push the right number of lua objects on the stack, or return the wrong number of objects on the stack.
Are you doing any callbacks?
You can perhaps comment out (or stop using) the functions one after another, to try to pinpoint which function is the culprit.
Ah, I see. There’s probably a bug in my timer extension. What kind of code are you running in your timer callbacks? Could it be that the timer callback is creating or removing timers?
I see now that I’m iterating over all created timers and for each timer I invoke it’s callback if the timer has finished and after invoking the callback I remove it. I suspect that the loop will get messed up if new timers are created while iterating. I’ll make some tests.
Yes, probably it is as you say, there are many timers here in this code. Unfortunately it’s something written by somebody else, basically a third-party lua module.
Yes, it’s written by me I’d like to figure out what’s wrong so I can fix it. I’ll try to create a more complex test scenario to try and reproduce the problem. Any additional information that you can provide would help! Is this happening on mobile or desktop?
I meant I’m using third parties lua code. There may be some bugs (or something that Defold doesn’t like) inside here. It seems it happens randomly and at the moment I have tested it only on the Editor (MacOS version). I could try it on a real device.
I’ve update the timer extension so that it handles that timers cancel other timers in their callbacks. Please use Project->Fetch Libraries to get the latest version of the extension and let me know if the problem has been solved. Thanks!
I’d like to figure out what’s wrong so I can fix it. I’ll try to create a more complex test scenario to try and reproduce the problem. Any additional information that you can provide would help! Is this happening on mobile or desktop?
I meant I’m using third parties lua code. There may be some bugs (or something that Defold doesn’t like) inside here. It seems it happens randomly and at the moment I have tested it only on the Editor (MacOS version). I could try it on a real device.