Search Issue Tracker
Fixed
Fixed in 6000.0.55f1, 6000.1.14f1, 6000.2.0b11, 6000.3.0a3
Votes
0
Found in
6000.0.46f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
Issue ID
UUM-101885
Regression
No
[Linux][URP][Vulkan] Player crash when activating a second display with a second camera targeting it
Reproduction steps:
1. Open the attached “IN-97734_camera” project
2. Click File > Build And Run
Expected results: Display 1 and Display 2 are displaying Player windows and outputs of two cameras
Actual results: Player crashes when running the built player
Reproduced with: 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Not reproduced with: 2022.3.60f1
Reproduced on: Ubuntu 24.04
Not reproduced on: Windows 11 Pro
First lines of the crashing thread stack trace:
Thread 13 (Thread 0x7760d1ffb6c0 (LWP 71121) "Vulkan Submissi"):
#0 0x00007761c79107e3 in __GI___wait4 (pid=71140, stat_loc=0x7760d1ff643c, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
#1 0x00007760fbf15607 in ?? () from /mnt/unity-editors/cases/IN-97734/b_second_camera_Dev/b_second_camera_dev_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#2 0x00007760fc05f4aa in monoeg_assertion_message () from /mnt/unity-editors/cases/IN-97734/b_second_camera_Dev/b_second_camera_dev_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#3 0x00007760fc054af4 in ?? () from /mnt/unity-editors/cases/IN-97734/b_second_camera_Dev/b_second_camera_dev_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#4 0x00007760fc055fbc in ?? () from /mnt/unity-editors/cases/IN-97734/b_second_camera_Dev/b_second_camera_dev_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#5 0x00007760fc0029a8 in ?? () from /mnt/unity-editors/cases/IN-97734/b_second_camera_Dev/b_second_camera_dev_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
Notes:
- Does not reproduce with Built-in rendering pipeline using both OpenGL and Vulkan
- Does not reproduce with HDRP + Vulkan
- Does not reproduce with URP + OpenGL
- Reproduces with both Mono and IL2CPP backends
- Couldn’t find the regression point due to the inability to build the player because of the unfixable errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment