Search Issue Tracker
Fixed in 2020.3.38f1, 2021.3.8f1, 2022.1.19f1
[Android] Crash in Player due to an overflow of global references to android.view.MotionEvent
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
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
- 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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform