Search Issue Tracker
Fixed
Fixed in 6000.5.0b2, 6000.6.0a2
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.67f1
6000.3.8f1
6000.4.0b8
6000.5.0a6
6000.6.0a1
Issue ID
UUM-134649
Regression
No
Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
Reproduction steps:
1. Open the attached "IN-133488_UnityBugReport.zip" project
2. Open the “Assets/Scenes/SampleScene.unity”
3. Wait for 1 minute
4. Close the project
5. Open the File Explorer
6. Navigate to "%LOCALAPPDATA%\Unity\Editor" folder
7. Observe the "Editor.log" file size
Actual result: File size exceeds 100mb
Expected result: File size remains normal (around 1 MB or lower)
Reproducible with: 2023.3.0b10, 6000.0.67f1, 6000.3.8f1, 6000.4.0b8, 6000.5.0a6
Could not test with: 2023.3.0b3 (Missing HDRP features)
Reproduced on: Windows 11
Not reproducible on: No other environments tested
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (6000.4.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.