Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.18f1
2022.2.10f1
2023.1.0b5
Issue ID
UUM-30434
Regression
No
Memory leak after opening a specific project
Reproduction steps:
1. Open the attached project “Leak“
2. Check memory usage of the editor
Expected result: Project opens succesfully
Actual result: Project opens and uses all the RAM
Reproducible with: 2021.3.18f1, 2022.2.10f1, 2023.1.0b5
Couldn’t test with: 2020.3.44f1 - Assets\Features\AddSomethingToScreen\AddSomethingToScreenFeature.cs(71,13): error CS0103: The name 'Blitter' does not exist in the current context, 2023.2.0a4 - Assets\Features\AddSomethingToScreen\AddSomethingToScreenFeature.cs(33,23): error CS0619: 'ScriptableRenderer.cameraColorTarget' is obsolete: 'Use cameraColorTargetHandle'
Reproducible on: Windows 11, 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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Spoke to QA stakeholders and all are happy to close now that we have confirmed the supplied script did not cause any memory issues and a response was already sent to the user.