I’ve been working on a new game recently, and development’s been going well, except for one thing: the simulator’s been crashing. It will crash at seemingly random times during the gameplay of my app, about 1/3 or 1/4 of the time. I’m no stranger to crashes (I’ve dealt with my fair share of them!), the odd thing about these is that 1)There seems to be no pattern, and 2) There is nothing written in the terminal. My app will be running as normal, when suddenly the terminal says “logout” and the simulator crashes.
I doubt this is because of a graphics or memory overload, because with my checks it seems to be running just fine, with no memory leaks. Does anyone have any idea what would cause the simulator to crash without warning and so randomly? [import]uid: 38000 topic_id: 30202 reply_id: 330202[/import]
The only time I have ever seen this is when physics has been the culprit. Are you using physics at all? [import]uid: 52491 topic_id: 30202 reply_id: 120958[/import]
I’m not using physics and simulator crashes randomly as well with me when I hit back buttons that use storyboard.gotoScene and I can’t find out whats causing this. [import]uid: 10141 topic_id: 30202 reply_id: 120993[/import]
I am using physics. [import]uid: 38000 topic_id: 30202 reply_id: 121011[/import]
This thread might help you:
http://developer.coronalabs.com/forum/2011/09/20/physics-debugging
[import]uid: 9422 topic_id: 30202 reply_id: 121019[/import]
That’s not exactly my problem though. I haven’t noticed any weird physics effects, just the simulator crashing randomly.
Another piece of information is that the simulator does crash with a segmentation fault or a bus error once in a while. Most of the time it crashes without a warning, but sometimes it gives me a error message.
I don’t know if that has anything to do with this random crashing, but it might. [import]uid: 38000 topic_id: 30202 reply_id: 121068[/import]
Now I just got a new error that I’ve never seen before:
Aug 24 16:59:19 new-host-7.home Corona Simulator[43209] <warning>: ImageIO: ImageProviderReleaseInfoCallback $$$ ImageProviderReleaseInfoCallback: cookie without releaseInfo - leaking<br>Corona Simulator(43209,0xb0081000) malloc: ***error for object 0xe55f290: pointer being freed was not allocated<br>*** set a breakpoint in malloc_error_break to debug<br>/Applications/CoronaSDK/Corona Terminal: line 9: 43209 Abort trap: 6 "$path/Corona Simulator.app/Contents/MacOS/Corona Simulator" $*<br>logout<br>
It occurred right after I relaunched the simulator, before anything else had happened. [import]uid: 38000 topic_id: 30202 reply_id: 121071[/import]
That other thread starts off with a different physics problem but goes on to detail a fix for a similar problem to what you describe here, namely random simulator crashing with unhelpful or nonexistent error messages. [import]uid: 9422 topic_id: 30202 reply_id: 121076[/import]
Sorry, I’ve been really busy these last few days and haven’t had much time to work on this.
Anyways, this crashing bug has become more and more common, to the point where it crashes about 80-90% of the time. Each time it crashes it’s either a bus error, a segmentation fault, or no error message at all. It also only happens when there is a collision between two of my physics objects (a bullet and a ship). Ive had this problem with previous apps, and it was caused by trying to remove a physics object before the collision was finished. However, in this case, I’m not removing anything during collisions. I’m only changing the speed of the object (by using object:setLinearVelocity). Can anyone help me here?
Thanks in advance for your help!
Peter [import]uid: 38000 topic_id: 30202 reply_id: 121552[/import]
The only time I have ever seen this is when physics has been the culprit. Are you using physics at all? [import]uid: 52491 topic_id: 30202 reply_id: 120958[/import]
I’m not using physics and simulator crashes randomly as well with me when I hit back buttons that use storyboard.gotoScene and I can’t find out whats causing this. [import]uid: 10141 topic_id: 30202 reply_id: 120993[/import]
I am using physics. [import]uid: 38000 topic_id: 30202 reply_id: 121011[/import]
This thread might help you:
http://developer.coronalabs.com/forum/2011/09/20/physics-debugging
[import]uid: 9422 topic_id: 30202 reply_id: 121019[/import]
That’s not exactly my problem though. I haven’t noticed any weird physics effects, just the simulator crashing randomly.
Another piece of information is that the simulator does crash with a segmentation fault or a bus error once in a while. Most of the time it crashes without a warning, but sometimes it gives me a error message.
I don’t know if that has anything to do with this random crashing, but it might. [import]uid: 38000 topic_id: 30202 reply_id: 121068[/import]
Now I just got a new error that I’ve never seen before:
Aug 24 16:59:19 new-host-7.home Corona Simulator[43209] <warning>: ImageIO: ImageProviderReleaseInfoCallback $$$ ImageProviderReleaseInfoCallback: cookie without releaseInfo - leaking<br>Corona Simulator(43209,0xb0081000) malloc: ***error for object 0xe55f290: pointer being freed was not allocated<br>*** set a breakpoint in malloc_error_break to debug<br>/Applications/CoronaSDK/Corona Terminal: line 9: 43209 Abort trap: 6 "$path/Corona Simulator.app/Contents/MacOS/Corona Simulator" $*<br>logout<br>
It occurred right after I relaunched the simulator, before anything else had happened. [import]uid: 38000 topic_id: 30202 reply_id: 121071[/import]
That other thread starts off with a different physics problem but goes on to detail a fix for a similar problem to what you describe here, namely random simulator crashing with unhelpful or nonexistent error messages. [import]uid: 9422 topic_id: 30202 reply_id: 121076[/import]
Sorry, I’ve been really busy these last few days and haven’t had much time to work on this.
Anyways, this crashing bug has become more and more common, to the point where it crashes about 80-90% of the time. Each time it crashes it’s either a bus error, a segmentation fault, or no error message at all. It also only happens when there is a collision between two of my physics objects (a bullet and a ship). Ive had this problem with previous apps, and it was caused by trying to remove a physics object before the collision was finished. However, in this case, I’m not removing anything during collisions. I’m only changing the speed of the object (by using object:setLinearVelocity). Can anyone help me here?
Thanks in advance for your help!
Peter [import]uid: 38000 topic_id: 30202 reply_id: 121552[/import]