Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.30f1
2022.3.0f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-49100
Regression
No
Memory leak when refreshing AssetDatabase after editing script
Reproduction steps:
1. Open the attached project "ReproProj
2. Open the “/Assets/Scenes/GameScene.unity“
3. Set External Script Editor to Visual Studio 2022 by going to Edit > Preferences
4. In Unity, click Assets > Open C# Project
5. Make changes to any script within Assets/Scripts/
6. Save changes in Visual Studio
7. Switch back to Unity Editor, and wait for AssetDatabase to refresh
8. Repeat steps 3, 4, 5, and 6 at least 3 times
9. Observe the Editor’s memory usage
Expected result: Memory usage stays the same
Actual result: Memory usage increases after each time step 8 is repeated
Reproducible with: 2.0.18 (2023.3.0a5), 2.0.20 (2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5)
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment 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
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
- Last segment of a Sprite Shape Spline is affected by other segments' Sprite Variant change when no edge Sprite is selected
- [iOS] Application frequently crashes on Social.LoadAchievements call when many achievements are registered
- Errors “RenderPass: Attachment 0 is declared as depth attachment but RGBA8 sRGB is not a valid depth format.“ and “BeginSubPass: Not inside a Renderpass“ are present when using Native RenderPass with a RenderTexture that only has depth output
- ArgumentOutOfRangeException is thrown when an empty DropdownField is clicked at runtime
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 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.