Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.3.7f1
2020.3.22f1
2021.2
2022.1
Issue ID
1384263
Regression
Yes
Crash on Radeon::DenoiserContext::DenoiseGPUBuffer when Baking Global Illumination and changing the Post Processing settings
Reproduction steps:
1. Open the user's attached project
2. Open "Assets/Unity Asset Unlocks - Backyard/Scenes/ExampleScene" Scene
3. Open Window -> Rendering -> Lighting
4. Press "Generate Lighting"
5. From the Hierarchy select "PostProcessingVolume" GameObject
6. Change the settings of "Color Adjustments" in the Post Processing Component
Expected result: Editor finishes baking with no problems
Actual result: Editor crashes
Reproducible with: 2020.3.7f1, 2020.3.24f1, 2021.2.6f1, 2022.1.0b2
Not reproducible with: 2019.4.33f1, 2020.3.6f1
First lines of stacktrace:
0x00007FF72AB89DFC (Unity) Radeon::DenoiserContext::DenoiseGPUBuffer
0x00007FF72AB88E9E (Unity) Radeon::DLDenoise
0x00007FF72AC9C575 (Unity) RadeonRaysJobCompositeLightmap::RunDenoiser
0x00007FF72AC941DE (Unity) RadeonRaysJobCompositeLightmap::CompositeLightmap
0x00007FF72AC307E5 (Unity) BakeJobCompositeLightmap::Execute
Notes:
- may take several minutes to reproduce the crash
- very rarely may just crash while baking and not editing any Post Processing settings
- sometimes instead of a crash the Console throws an error: "Assertion failed on expression: '!useRadeon || (!radeonDenoiser.IsNull() && radeonDenoiser->GetRefCount() <= 1)'"
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
- Packman: "My Assets" filters section doesn't rescale on filter sections collapse
- "DrawDepthNormalPrepass" exceptions are thrown in Editor when Ctrl key is held with specific renderer settings
- Script file name changes do not display in Editor when Compiler errors are present
- Sprites are not rotating with bones when the Sprite type is Unlit
- Crash on TransferField_NonArray<YAMLRead,Converter_String> when opening a specific project
Resolution Note (fix version 2022.2):
This bug will be fixed by enablement work that is in progress now. To that end we are postponing this and will retest once that lands.