-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime panic because out of touchID #2407
Labels
bug
Something isn't working
Milestone
Comments
changkun
added a commit
to changkun/gomobile
that referenced
this issue
Aug 27, 2021
From practical observation, out of touchIDs may occur. This conflicts the maximum number of handled touchs in iOS devices. Therefore the only reason that may cause out of touchIDs is that the touchIDs are intrinsically non-concurrent safe. This change adds a read-write lock to the touchIDs array. Fixes fyne-io/fyne#2407.
changkun
added a commit
to changkun/gomobile
that referenced
this issue
Aug 27, 2021
From practical observation, out of touchIDs may occur. This conflicts with the maximum number of handled touches in iOS devices. Therefore the only reason that may cause out of touchIDs is that the touchIDs are intrinsically non-concurrent safe. This change adds a read-write lock to the touchIDs array. Fixes fyne-io/fyne#2407.
changkun
added a commit
to changkun/gomobile
that referenced
this issue
Aug 27, 2021
From practical observation, out of touchIDs may occur. This conflicts with the maximum number of handled touches in iOS devices. Therefore the only reason that may cause out of touchIDs is that the touchIDs are intrinsically non-concurrent safe. This change adds a read-write lock to the touchIDs array. Fixes fyne-io/fyne#2407.
changkun
added a commit
to changkun/gomobile
that referenced
this issue
Aug 27, 2021
From practical observation, out of touchIDs may occur. This conflicts with the maximum number of handled touches in iOS devices. Therefore the only reason that may cause out of touchIDs is that the touchIDs are intrinsically non-concurrent safe. This change adds a read-write lock to the touchIDs array. Fixes fyne-io/fyne#2407.
andydotxyz
pushed a commit
to fyne-io/mobile
that referenced
this issue
Aug 27, 2021
From practical observation, out of touchIDs may occur. This conflicts with the maximum number of handled touches in iOS devices. Therefore the only reason that may cause out of touchIDs is that the touchIDs are intrinsically non-concurrent safe. This change adds a read-write lock to the touchIDs array. Fixes fyne-io/fyne#2407.
Thanks, merged a change to go.mod to bring in the change from mobile project. |
@andydotxyz I just encountered the problem again. It looks like the issue is not yet fixed. Let's reopen it again... |
Make sure to double check it was built with |
What just happened? |
It got auto-closed because the issue we thought resolved it hit master. I’ve unresolved it |
3 tasks
This will be rolling out in v2.1.1 :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug:
While debugging #2406 , a runtime panic crashes the app. Here is a stack trace:
It looks like sendTouch may happen concurrently. Adding an RWMutex would be a quick fix.
To Reproduce:
Device (please complete the following information):
The text was updated successfully, but these errors were encountered: