Search Issue Tracker
Fixed
Won't Fix in 2021.3.X
Fixed in 2022.3.7f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1
Votes
0
Found in
2021.3.19f1
2022.3.5f1
2023.1.0b5
2023.2.0a3
2023.3.0a1
Issue ID
UUM-32862
Regression
No
Frame Debugger continuously allocating ram when looking at Shadows.RenderShadowMap
Reproduction steps:
1. Open the attached project “SampleProject”
2. Go to Assets > Aircraft Physics > Game > Scenes
3. Open the “DebugArea” scene
4. Click Window > Analysis > Frame Debugger
5. Hit the “Enable” button
6. Click on Camera.Render > Drawing > Render.OpaqueGeometry > RenderForwardOpaque.Render > Shadows.RenderShadowMap
7. Wait a few seconds
Expected result: Nothing happens
Actual result: Unity starts allocating ram indefinitely until GPU freezes and PC crashes
Reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Reproducible on: Windows 10
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 (2021.3.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this version will be resolved as "Won't Fix".This does not mean that the issue isn't a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case for this version will now be closed, and will not be reopened unless new information arises that would change the issue's impact. Please let us know if you have additional information relating to the severity of this bug.