Maybe it is a bug, maybe not...

I am trying to save a tinted image using display.save(), I am also using Storyboard.
My problem is that after some time (not attempts, time), after clicking the button that calls display.save, the thing freezes, the screen becomes completely black except the thing I am saving, and get stuck that way…
It successfully saves what I want, but does not return to normal.

So… someone has any clue on where I start looking? [import]uid: 138716 topic_id: 26886 reply_id: 326886[/import]

Extra information I figured here:

There are a character made of multiple files, that I chance between them manually (since the new API does not support multiset yet), this character was shown in main.lua, so it is the same one across all Storyboard screens.

When that character is animating, even if hidden (ie: if I change the screen while the animation is playing, it disappears but after the animation end the callback puts the character back on the screen), display.save() in a unrelated thing (on a image, that is part of the group that comes with the scene), works fine.
When the character is NOT animating, the bug happens.

This is why I had impression it was time-based (it was the time needed to some ways of reach the buggy screen that involve the character playing animation, to the animation end).

If I change the scren while animation, and wait for it to end the animation, or change the screen without animation and hide the character, it freezes. [import]uid: 138716 topic_id: 26886 reply_id: 109117[/import]

Note: I am using build 807 [import]uid: 138716 topic_id: 26886 reply_id: 109267[/import]