Scroll View error in daily build 2015.2706

Solar2D Daily Builds and Public Releases
#1

I updated to this build from the last public release (2646 -> 2706) to get a bug fix associated with android sounds not stopping on screen time outs.

However, now when I change composer scenes I am getting the error below. This was working fine on my previous build.

This issue happens after the destroy scene event ( Checking with a print statement on the end of function scene:destroy( event ) )

The scene that is being called next seems to be unassociated with the crash as it happens when transitioning to many different scenes.

Any ideas what this might be? 

( EDIT: This has to do with the fact that there are 2 scroll views being used in this composer scene. If I comment one out 1, therefore leaving only 1, it will no longer crash. FYI: Only a single scroll view is visible at any one time. If one is set to .visible = true, the other is set to .visible = false and disabled.)

I can’t really post code b/c it is interwoven with ton of other elements and would take me forever to isolate. However a working version of the app can be found at the link below. It crashes after tapping the main menu button “Dungeon” and then then either tapping the “Back” button or selecting a dungeon to enter.

https://play.google.com/store/apps/details?id=com.superultrahyper.gameofloot

https://itunes.apple.com/app/id1016781837

Corona Runtime Error

?:0: attempt to perform arithmetic on field ‘_scrollWidth’ (a nil value)

stack traceback:

?: in function ‘_listener’

?: in function <?:167>

?: in function <?:221>

Do you want to relaunch the project?

Yes   No   

#2

I have exactly the same issue. Was not present in earlier daily builds nor the public release; although the build logs don’t say that anything was changed for the scroll views?

My code gets this error when i perform remove:self() on the scroll view. Seem that theres some Corona code still referencing the scroll view after its been destroyed.

I tried to post a bug report, but can’t submit unless i post a code file? unfortunately I don’t have time to write code to prove the bug, so hopefully some Corona staff will pick this up.

edit: i’m using build 2707

#3

We’ve asked the engineers to look at this, but there is a strong chance they will come back and ask for a bug report.  There is a good case you’re doing something that our test cases are not catching, so having your case will expedite finding the problem.

Rob

#4

Earlier I posted “If I disable one, therefore leaving only 1, it will no longer crash.”

I meant to say " If I comment out 1, therefore leaving only 1, it will no longer crash."

Sorry for any confusion.

#5

Any news on this one?

#6

Hi guys,

This should be fixed in an upcoming daily build. I am locking this thread, so if there are any further comments, please continue there:

https://forums.coronalabs.com/topic/59081-latest-available-build-scrollview/

Thanks,

Brent

#7

This should be fixed in the next daily build.

Rob

#8

I have exactly the same issue. Was not present in earlier daily builds nor the public release; although the build logs don’t say that anything was changed for the scroll views?

My code gets this error when i perform remove:self() on the scroll view. Seem that theres some Corona code still referencing the scroll view after its been destroyed.

I tried to post a bug report, but can’t submit unless i post a code file? unfortunately I don’t have time to write code to prove the bug, so hopefully some Corona staff will pick this up.

edit: i’m using build 2707

#9

We’ve asked the engineers to look at this, but there is a strong chance they will come back and ask for a bug report.  There is a good case you’re doing something that our test cases are not catching, so having your case will expedite finding the problem.

Rob

#10

Earlier I posted “If I disable one, therefore leaving only 1, it will no longer crash.”

I meant to say " If I comment out 1, therefore leaving only 1, it will no longer crash."

Sorry for any confusion.

#11

Any news on this one?

#12

Hi guys,

This should be fixed in an upcoming daily build. I am locking this thread, so if there are any further comments, please continue there:

https://forums.coronalabs.com/topic/59081-latest-available-build-scrollview/

Thanks,

Brent

#13

This should be fixed in the next daily build.

Rob