Mac simulator crashes after updating.. worked fine before.

Solar2D Daily Builds and Public Releases
#1

I am working on a windows machine and didn’t update my mac for quite some time. 

So I did an update and after that my app crashes in the simulator when using director slim class to get into a level.

It’s a physics based game - so it might have something to do with that.

The thing is, that it works fine on the windows simulator, also on Android devices (still does) and it used to work as well on the mac simulator,  an Iphone 5 and an IPad 1.

After updating the same code crashes. So I tried to find the last build that the code works on and it seems to be the 2013.1142… The 2013.1143 crashes without an error message.

I checked the info on that build, but it doesnt seem to be any of the mentioned fixes.

Im kinda lost here.

Would love the help…

Thanks

Phil

#2

Thanks for the trouble you took the narrow down where the issue appears!

The first thing I would try is enabling **physics.setDebugErrorsEnabled() **as that changed right around the time you found the bug appears.  You can find documentation on this here.  That might perturb things enough to provide more info (obviously, the Simulator shouldn’t crash at all so there’s still an issue if this workaround works).

Next steps would involve getting a reproducible case which I’ll discuss via PM.

#3

hej Perry,

thanks for looking into the problem.

I tried enabling and disabling  **physics.setDebugErrorsEnabled()****  **but with no luck.

I PMed you the details. Hope that helps…

Thanks

Phil

#4

Thanks for the trouble you took the narrow down where the issue appears!

The first thing I would try is enabling **physics.setDebugErrorsEnabled() **as that changed right around the time you found the bug appears.  You can find documentation on this here.  That might perturb things enough to provide more info (obviously, the Simulator shouldn’t crash at all so there’s still an issue if this workaround works).

Next steps would involve getting a reproducible case which I’ll discuss via PM.

#5

hej Perry,

thanks for looking into the problem.

I tried enabling and disabling  **physics.setDebugErrorsEnabled()****  **but with no luck.

I PMed you the details. Hope that helps…

Thanks

Phil

#6

So it turns out there’s a problem with physics.setDebugErrorsEnabled() which can cause the Simulator to crash.  We’re working on a fix.

The change that was made was to surface previously silent Box2D errors to the Lua code which is usually what you’d want since, if Box2D is throwing errors, your code is at the very least inefficient and more likely will fail entirely under some circumstances.  Turning physics.setDebugErrorsEnabled() off should return you to the old behavior but it seems to have a bug.

#7

So it turns out there’s a problem with physics.setDebugErrorsEnabled() which can cause the Simulator to crash.  We’re working on a fix.

The change that was made was to surface previously silent Box2D errors to the Lua code which is usually what you’d want since, if Box2D is throwing errors, your code is at the very least inefficient and more likely will fail entirely under some circumstances.  Turning physics.setDebugErrorsEnabled() off should return you to the old behavior but it seems to have a bug.