Search Issue Tracker
Third Party Issue
Votes
1
Found in
2021.3.6f1
2022.1.14f1
Issue ID
UUM-11474
Regression
No
Crash in vkCreatePipelineLayout on adreno devices when using Vulkan
Reproduction steps:
1. Open the attached project
2. Build and Run the project on an Android device
3. Wait for 15 seconds
Expected results: The Application continues to run
Actual result: The Application crashes
Reproducible with: 2021.3.6f1
Reproduces with these devices:
Pixel 4a, Android 12, CPU: Qualcomm SDM730 Snapdragon 730G, GPU: Adreno 618
Does not reproduce with these devices:
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
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
VLNQA00122 - Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
VLNQA00293 - OPPO R17 Pro (PBDM00), CPU: Snapdragon 710 SDM710, GPU: Adreno 616, OS: 9.0.0
VLNQA00263 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 12.0.0
VLNQA00319 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 10.0.0
Stack trace:
07-20 14:23:36.648 10138 10157 E AndroidRuntime: managed backtrace: 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #00 (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal_Injected (UnityEngine.Rendering.ScriptableRenderContext&) 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #01 UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal () <0x13> 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #02 UnityEngine.Rendering.ScriptableRenderContext:Submit () </Users/bokken/buildslave/unity/build/Runtime/Export/RenderPipeline/ScriptableRenderContext.cs:110> 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #03 UnityEngine.Rendering.Universal.UniversalRenderPipeline:RenderSingleCamera (UnityEngine.Rendering.ScriptableRenderContext,UnityEngine.Rendering.Universal.CameraData,bool) </Users/ciannoonan/Downloads/TextureAnimationCrashTest/Library/PackageCache/com.unity.render-pipelines.universal@12.1.7/Runtime/UniversalRenderPipeline.cs:431> 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #04 UnityEngine.Rendering.Universal.UniversalRenderPipeline:RenderCameraStack (UnityEngine.Rendering.ScriptableRenderContext,UnityEngine.Camera) </Users/ciannoonan/Downloads/TextureAnimationCrashTest/Library/PackageCache/com.unity.render-pipelines.universal@12.1.7/Runtime/UniversalRenderPipeline.cs:572> 07-20 14:23:36.648 10138 10157 E AndroidRuntime: #05 UnityEngine.Rendering.Universal.UniversalRenderPipeline:Render (UnityEngine.Rendering.ScriptableRenderContext,System.Collections.Generic.List`1<UnityEngine.Camera>) </Users/ciannoonan/Downloads/TextureAnimationCrashTest/Library/PackageCache/com.unity.render-pipelines.universal@12.1.7/Runtime/UniversalRenderPipeline.cs:265>
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 UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note:
Unfortunately, this issue only appears on the specific device listed, with testing not reproducing the issue on other identical hardware and OS configurations (different OEMs). As such, we're marking this as a 3rd party issue that we aren't able to fix directly.