build 2011.691 and 2011.703 - change from whats specified in config.lua after resume/restart

Solar2D Daily Builds and Public Releases
#1

I’ve noticed a bug in build 691. It happens when a game resume after a power button suspend event.
Sometimes when it resume it does it with other width and height than I specify in the config.lua file.
This happen just sometimes but more often when doing really heavy graphics on the screen at the moment of pressing the power button.
Once in a while this also freezes the screen for some time upon resume .Often the app restarts instead of resuming too.

After reverting back to the stable build 591 I haven’t been able to reproduce the bug so this seems to be an issue with build 691 [import]uid: 53069 topic_id: 18596 reply_id: 318596[/import]

#2

What kind of device are you using?

Peach :slight_smile: [import]uid: 52491 topic_id: 18596 reply_id: 71533[/import]

#3

I’m developing for Android (using both Google Nexus S and Xperia Arc as my “test phones”) [import]uid: 53069 topic_id: 18596 reply_id: 71551[/import]

#4

I can confirm that the error remains in the new stable release 2011.703 (but less often than in build 691). If I would to guess about the way it seems to happens is that a resume instead becomes a restart and SOMETIMES the stuff specified in config lua doesn’t scale the way it should. Actually the scale always seems to get bigger than it should so a background becomes really big and only a part of the screen remains and to me that suggests some type of crasch while restarting/resuming.

It happens when one spawn alot of images (to the point of almost lagging the phone down) and then press powerbutton (not checked if a call triggers it). As I said it doesn’t happen all the time but when it does it can be troublesome.

It doesn’t happen in the previous stable release 591 so something must have changed since then.

Tried this on different phones. [import]uid: 53069 topic_id: 18596 reply_id: 72769[/import]

#5

Interesting - what kind of memory usage have you got when this is occurring?

If it is in the safe range for the given device(s) could you please file a bug report?

Peach :slight_smile: [import]uid: 52491 topic_id: 18596 reply_id: 72856[/import]

#6

As the bugtracker page is still down and since in 703 it happens only rarely (unlike in 691) I’ll settle for pointing it out this way :slight_smile:

ps: Tried running the same apps to see if I could break the old stable release 591 too but that didn’t happened once. So it looks like it’s something after 591 thats causing it. [import]uid: 53069 topic_id: 18596 reply_id: 72899[/import]