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

  1. Resolution Note (fix version 2021.3.8f1):

    Android: Fix overflow of MotionEvent global references

Log in to vote on this issue

Comments (4)

  1. ageana

    Aug 08, 2023 07:33

    Still happens in 2022.3.6f1

  2. Rafael-cmk

    Jul 18, 2023 03:11

    Getting a similar error with 2022.3.5f1.
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] JNI ERROR (app bug): global reference table overflow (max=51200)global reference table dump:
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] Last 10 entries (of 51200):
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51199: 0x1403b660 byte[] (27 elements)
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51198: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51197: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51196: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51195: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51194: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51193: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51192: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51191: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>
    2023/07/17 23:59:18.495 32600 32716 Fatal inment.estilobr java_vm_ext.cc:705] 51190: 0x6fe80ec0 java.lang.Class<android.os.SystemClock>

  3. ahdstudioofficial78

    Jun 23, 2023 12:42

    It also happens on 2022.3.2f1 LTS
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .

  4. akiyamaexe

    Aug 31, 2022 02:26

    It also happens on 2022.1.13f.1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues