Search Issue Tracker
Fixed
Fixed in 2020.3.38f1, 2021.3.8f1, 2022.1.19f1
Votes
1
Found in
2020.3.36f1
2021.3.7f1
2022.1.17f1
Issue ID
UUM-8438
Regression
Yes
[Android] Crash in Player due to an overflow of global references to android.view.MotionEvent
Reproduction steps:
1. Download and open the attached project: "CrashTest.zip"
2. Connect an Android device to your system
3. Go to Window > Analysis > Android Logcat
4. Build and Run the project to the Android device
5. Click the screen a few thousand times
Expected result: The counter increases indefinitely
Actual result: After a varying amount of clicks (4000-10000) the project crashes and the android.view.MotionEvent related error can be seen in the Android Logcat window
Reproduced with: 2020.3.35f1, 2020.3.36f1
Reproduced using:
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Notes:
- It was reported by the users that the issue does not occur in 2020.3.34f1
- After 25000 clicks when built with Unity 2023.1.0a2, the crash did not occur
- Due to the nature of the issue, reproduction and testing on multiple devices and Unity versions would be a very lengthy process thus testing was limited to the 2020.3 stream
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
Resolution Note (fix version 2021.3.8f1):
Android: Fix overflow of MotionEvent global references