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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
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.