Build 2544 crashes

With the ‘finalize’ bug fix, build 2544 crashes when testing with ProgressRing.

The issue is the function fixFinalize() is still called, and something inside it causes the crash.

A slight delay prevents the function to be called and won’t cause the crash:

timer.performWithDelay(1, function()
    if not finalizeFixed then fixFinalize() end
end)

I haven’t determined what exactly inside the function causes the crash though.

Mac OS 10.10.1 with all the latest updates.

Dave

Hi Dave,

Good catch! Looking at the timestamp on your post, I think you actually beat me to it!

I’ve fixed the progressRing module using the same method you employed above. The new version is now posted on my website. I didn’t write the fixFinalize function - it was created by Sergey Lerg (view his original post here), and he had warned that is could cause breakage when the bug was finally corrected by Corona Labs.

It makes sense that there would need to be a delay, because the finalize event isn’t called until the display group is actually removed, and that could take an additional cycle. And since the finalizeFixed variable isn’t set to “true” until the finalize event is actually called, then the code dictates that the fixFinalize function be run.

Still - way to go CL for fixing that nasty old bug that had hung around for way too long! :slight_smile:

Hi Jason,

Thanks for the excellent module and the prompt update!  :slight_smile:

Cheers,

Dave

Hi Dave,

Good catch! Looking at the timestamp on your post, I think you actually beat me to it!

I’ve fixed the progressRing module using the same method you employed above. The new version is now posted on my website. I didn’t write the fixFinalize function - it was created by Sergey Lerg (view his original post here), and he had warned that is could cause breakage when the bug was finally corrected by Corona Labs.

It makes sense that there would need to be a delay, because the finalize event isn’t called until the display group is actually removed, and that could take an additional cycle. And since the finalizeFixed variable isn’t set to “true” until the finalize event is actually called, then the code dictates that the fixFinalize function be run.

Still - way to go CL for fixing that nasty old bug that had hung around for way too long! :slight_smile:

Hi Jason,

Thanks for the excellent module and the prompt update!  :slight_smile:

Cheers,

Dave