Latest 2016.8.1 iOS Gideros Player crashing a lot

EricCarr

Updated to the latest player on my iPhone 6 and it now crashes multiple times a day. It hardly ever crashed before. By crash I mean the application exits to the home screen. This happens randomly while playing (multiple different projects), and also sometimes when pushing a new set of valid code to the device from the IDE.

Wondering if anyone else is experiencing this?

I'll try some stuff like not playing any sounds to see if it still crashes. I'm not using any of the new features. This is existing code bases that ran fine on the older player without any crashes.

Will collect any logs I can over the next couple weeks.

john26

Can you try the latest 2016.8.2? It may not make a difference as I can't recall changes specific to this but worth a try...

EricCarr

I'm away from my mac so can't try the new version but I narrowed down the steps to reproduce. After resuming an app, executing print() crashes the app:

1. Start the Gideros App like normal
2. Press Home to exit the app
3. Run the Gideros App, it resumes where it picked off.
4. Execute any code with print() and the app closes immediately.

Sample code - the red button executes a print statement but the green does not:

function createRect(x,y,w,h,color) local rect = Shape.new() rect:setFillStyle(Shape.SOLID, color, 1) rect:beginPath() rect:moveTo(-w, -h) rect:lineTo(w, -h) rect:lineTo(w, h) rect:lineTo(-w, h) rect:closePath() rect:endPath() rect:setPosition(x, y) return rect end     r = createRect(50,50,50,50,0xff0000) counter = 0 stage:addChild(r) r:addEventListener(Event.MOUSE_DOWN, function(s, event) if not s:hitTestPoint(event.x, event.y) then return end print ("Hello") end, r)   r = createRect(50,200,50,50,0x00ff00) stage:addChild(r) r:addEventListener(Event.MOUSE_DOWN, function(s, event) if not s:hitTestPoint(event.x, event.y) then return end -- not printing end, r)

totebo

@hgy29, could this have something to do with the network code changes we had trouble with a couple of weeks back?

hgy29

Yes, it seems related, and it was fixed in 2016.8.2

EricCarr

Confirmed this is fixed in 2016.8.2. Thanks!