Search Issue Tracker
Fixed
Fixed in 2022.3.68f1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Votes
1
Found in
2022.3.48f1
6000.0.20f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-82923
Regression
No
[Android] Crash on "AtomicQueue::Enqueue(AtomicNode*)+12" when a scene transition happens in the Player
How to reproduce:
1. Open the attached “IN-84217.zip” project
2. Switch the Target Platform to Android (File → Build Settings)
3. Build and Run on an Android device
4. Observe the Player
Expected result: The Player switches to a different view showing a cube
Actual result: Crash occurs when the view switch happens
Reproducible with: 2022.3.48f1, 6000.0.20f1
Couldn’t test with: 2021.3.43f1 (Unsupported Shader Code in older streams)
Testing environment: Windows 11, macOS 14.6 (M1)
Reproducible on:
Quest 2 (user reported)
Pico 4 (user reported)
OnePlus 8 (user reported)
VLNQA00520, Samsung Galaxy S22 (SM-S901U), Android 14, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
VLNQA00517, Oneplus OnePlus 10 Pro 5G (NE2213), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
VLNQA00411, Samsung Galaxy Z Fold3 5G (SM-F926B), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00341, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 11, CPU: Exynos 990, GPU: Mali-G77
VLNQA00144, Samsung Galaxy S9 (SM-G960U1), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Not reproducible on:
Samsung Galaxy A32 5G (user reported)
Notes:
- Reporter noted that it might be related to https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-69949
- Not reproducible with OpenGLES3 Graphics API
- Inconsistency in reproduction was noticed when testing, in some cases the issue appeared to not reproduce on the latest Unity 6 versions and a fix was possible to be found between 2023.3.0b5 and 2023.3.0b10, however during sanity tests to verify if the fix was indeed found, the issue started reproducing again on versions it didn’t before.
First few lines of the Stacktrace:
#00 pc 00000000010e5968 /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (AtomicQueue::Enqueue(AtomicNode)+12) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
#01 pc 0000000001a1dd5c /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (vk::GraphicsPipelineCache::EnqueuePipelineForIntegration(vk::PipelineKey const&, vk::DeviceLocalPipelineCacheState, VkPipeline_T)+136) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
#02 pc 0000000001a31dcc /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (vk::CreatePipelineJob(vk::CreateGraphicsPSOJobData)+148) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
#03 pc 0000000000dd9a20 /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (ujob_execute_job(ujob_control_t, ujob_lane_t, ujob_job_t, ujob_handle_t, unsigned int)+164) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
#04 pc 0000000000dda148 /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (lane_guts(ujob_control_t, ujob_lane_t, int, int)+884) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
#05 pc 0000000000dda9d4 /data/app/~~DJuKS7kqB2CtrYB2WISsYQ==/com.UnitySupport.BugShaderWarmUpCrash-39M6Pl8HaDfij6Uo5lxM1A==/lib/arm64/libunity.so (worker_thread_routine(void)+156) (BuildId: e8aa4344e9e9c8606aecbf53d23344363774710d)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.3.68f1):
This port is fixed in 2022.3.68f1, fix has landed.