Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.5.0a6
Issue ID
UUM-132750
Regression
No
Baking APV causes crash when using Linux/ROCm/Vulkan
Steps to reproduce:
- Using Linux with ROCm installed, extract and open the attached project.
- Make sure Graphics API is set to Vulkan (may require restart). May also repro with OpenGL.
- Open the "Assets/Scenes/TestWorld1.unity" scene
- Open Window → Rendering → Lighting
- Select "Adaptive Probe Volumes"
- Press "Generate Lighting"
Actual results: The process finishes successfully and no errors are thrown.
Expected results: Editor crashes, no logs reported other than polling of OpenCL features.
Reproducible with versions: Unknown. This has not yet been verified by Unity employee.
Notes:
The original issue [https://jira.unity3d.com/browse/UUM-126472] was split into 3 related but distinct issues, and this issue is one of them. The user who reported the original issue used this configuration:
OS: Arch Linux
Renderer: AMD Radeon RX 7800 XT (radeonsi, navi32, LLVM 20.1.8, DRM 3.64, 6.16.8-zen3-1-zen)
Vendor: AMD
Version: 4.6 (Core Profile) Mesa 25.2.3-arch1.2
GLES: 0
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
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
- UI breaks when Multiplayer Center window section divider is moved too far
- Adaptive Performance documentation link leads to outdated package documentation when the documentation hyperlink is pressed in the Project Settings window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.