Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.27f1
2022.3.4f1
2023.1.2f1
2023.2.0a21
Issue ID
UUM-41189
Regression
No
[PICO] [Android] Player crashes at launch when VK_EXT_debug_utils extension debug labels are used
Reproduction steps:
1. Open the attached project "ReproProj" with the Android Platform
2. Open the “/Assets/Scenes/3D-over-under.unity” Scene
3. Tick Development Build in File > Build Settings
4. Build And Run on a VR device
5. Observe the Player
Expected result: The player successfully launches and continues to run
Actual result: The player crashes at launch
Reproducible with: 2021.3.27f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21
Reproducible with devices:
PICO (User’s device)
Testing environment: Windows 10 Enterprise 21H2
Notes:
- User states that Player only crashes when Development Build is selected, and it seems to be related to VK_EXT_debug_utils. If GraphicsCapsVK.cpp is modified, vk.hasDebugUtils is set to false and the engine is rebuilt, then it won't crash
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Single device third party issue.
Resolution Note (2023.2.X):
Single device third party issue.