Search Issue Tracker

Won't Fix

Votes

0

Found in

2021.3.27f1

2022.2.21f1

Issue ID

UUM-40536

Regression

No

[Android] The Player crashes after a few seconds when Particles are generated and deleted continuously over time

--

-

Reproduction steps:
1. Open the attached project “ParticleProject”
2. Open the “Assets/Scenes/SampleScene.unity“ scene
3. Build the project and run it on Android
4. While the app is running wait for the about 1-2mins
5. Observe the crash

Expected result: The app does not crash
Actual result: The app stays for a few seconds and then crash

Reproducible with: 2021.3.27f1, 2022.2.21f1
Not Reproducible with: 2023.1.0b19, 2023.2.0a18
Fixed in: 2022.3.0f1

Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0

Not reproducible with these devices:
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1

Reproducible with these devices (by User):
Mi 10(64-bit, Android 12)
Redmi 8A(32-bit, Android 10)

Reproduced on: Intel macOS 13.3.1

First few lines of the stack trace:
05-09 13:50:19.234 10078 10135 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x78 in tid 10135 (Job.Worker 3), pid 10078 (icleSystemCrash)
05-09 13:50:19.278 10191 10191 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
05-09 13:50:19.278 772 772 I tombstoned: received crash request for pid 10135
05-09 13:50:19.278 10191 10191 I crash_dump64: performing dump of process 10078 (target tid = 10135)
05-09 13:50:19.285 10191 10191 E DEBUG : failed to read /proc/uptime: Permission denied

Notes:
- An Inconsistent reproduction occurs on Xiaomi Mi 5s with 2022.2.21f1, 2022.3.0f1

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

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.