Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112596
Regression
No
Crash on Calc::Event::Event when generating lighting in a specific project
How to reproduce:
1. Open the attached “CrashRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Open the Lighting window (Window > Rendering > Lighting)
4. Press “Generate Lighting“ and wait a few minutes
Reproducible with: 6000.0.54f1, 6000.1.12f1, 6000.2.0b11, 6000.3.0a3
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: The lighting generation can get stuck at some point (it happened at 65% when testing)
First few lines of the stack trace:
0x00007FF8E87CB6A8 (radeonrays) Calc::Event::Event
0x00007FF8E87E206F (radeonrays) Calc::Event::Event
0x00007FF8E87E30AF (radeonrays) Calc::Event::Event
0x00007FF8E87D6930 (radeonrays) Calc::Event::Event
0x00007FF8E87D4BAE (radeonrays) Calc::Event::Event
0x00007FF8ED154AE5 (Unity) RadeonRaysMeshManager::StoreToGPU
0x00007FF8ED153388 (Unity) RadeonRaysContextManager::SetSceneStateOnTechnique
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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 is 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.