Search Issue Tracker
Active
Votes
2
Found in
2020.3
2021.2
2021.2.11f1
2022.1
2022.2
Issue ID
1405093
Regression
No
[Android] Application crashes after continuously loading and activating different remote addressable Scenes
Reproduction steps:
1. Open the user's attached project "wavexr-crash-test.zip"
2. Make sure that Development Build is enabled
3. Build for Android
4. The app will first start to download the remote addressable scenes, wait for the loading percentage to reach 100% and it will start cycling through the downloaded scenes
Expected result: Application does not crash after continuously loading and activating different remote addressable scenes
Actual result: Application crashes after continuously loading and activating different remote addressable scenes
Reproduces on: 2020.3.31f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a8
Could not test on 2019.4.36f1 due to script errors when downgrading the project
Reproducible with these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
N/A, Xiaomi Mi Note2 (Mi Note 2), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
N/A, Vivo V1924A (V1924A), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
N/A, Google Pixel 3 (Pixel 3), Android 12, CPU: Snapdragon 845, GPU: Adreno (TM) 630
N/A, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
N/A, Samsung - (SM-G991U), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
User reported devices:
HTC Vive Focus 3 (using Wave XR package): Instantly upon the first scene load
Sony Xperia XZ2 Compact (using Unity's MockHMD XR package): After about a minute / 10 scene loads
Oculus Quest 2 (using Oculus XR package): After about 10-30 minutes
Notes:
-Issue is reproducible with IL2CPP and Mono backends
-Depending on the device, you might need to wait a few minutes for it to crash according to the user
-Android logcat crash stacktrace is attached "crash.txt"
-Crash occurs when Development Build is enabled
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
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
bryandickson
Apr 08, 2022 21:07
Unity, please provide more information on this ticket, and what workarounds if any are possible. Should we be contacting HTC about this issue instead?
ertugrulerdogan
Apr 01, 2022 11:14
We are also experiencing crashes on remote addressable scenes load with editor version 2021.2.17f1 and addressable package 1.19.19.
ertugrulerdogan
Apr 01, 2022 11:14
We are also experiencing crashes on remote addressable scenes load with editor version 2021.2.17f1 and addressable package 1.19.19.
talespin-mathijs
Mar 31, 2022 09:19
I don’t understand why the posted resolution note means that the issue would not get fixed. The issue is maybe not caused by Addressables, but only exposed by using Addressables. But the issue does still look like a bug originating from Unity’s engine code. Therefore we still need this issue fixed by Unity developers as it is something we cannot debug and rectify on our own as users of Unity.