Search Issue Tracker

Won't Fix



Found in




Issue ID




[Android] [IL2CPP] [Vulkan] App crashes on some devices when loading assets in coroutine



This case was created based on case 1345518 (a sporadic freeze). The freeze is fixed with When debugging this it's recommended to graft the freeze fix.

Reproduction steps:
1. Open the attached project ""
2. Build and Run on Android device

Expected result: The cube in the Scene continues to spin
Actual result: After 10 seconds the app crashes with this stacktrace:
at libunity.vk::Texture::Create(vk::CommandBuffer*, vk::ScratchBuffer*, TextureID, TextureDimension, vk::ImageData const&, VkExtent3D const&, GraphicsFormat, int, VkSampleCountFlagBits, TextureUploadFlags, bool, bool)(Create:196)
at libunity.GfxDeviceVK::AcquireTexture2DUploadMemory(TextureCreateData&, TextureUploadMemory*&)(AcquireTexture2DUploadMemory:136)
at libunity.AcquireTexture2DUploadMemory(GfxDevice&, TextureCreateData*, TextureUploadMemory*&)(AcquireTexture2DUploadMemory:56)
at libunity.0x18f434(Native Method)
at libunity.AsyncUploadManager::AsyncResourceUpload(GfxDevice&, int, AsyncUploadManagerSettings const&)(AsyncResourceUpload:320)

Reproducible with: 2022.1.0a10, 2022.1.0b3, 2022.2.0a2
Not reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0a9

Reproducible with:
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76

Not reproducible with:
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630

- Not reproducible with Mono Scripting Backend
- Only reproducible if ARM64 target architecture is selected
- Only reproducible with Vulkan Graphics API
- Issue can be reproduced in 10 seconds after app launch (this happens in 1 out of 4 launches) or after running app for longer times (usually over 30 min)

  1. Resolution Note (2022.2.X):

    Issue postponed to see if any users are seeing this outside of Unity. It's likely this is related to old drivers on a singular device. If we see any user votes or duplicate errors, we'll see what we can do when the bug reactivates.

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.