Search Issue Tracker
Fixed
Votes
1
Found in
2023.1.0b19
2023.2.0a16
Issue ID
UUM-39692
Regression
No
Memory leak when unfocusing editor with a second undocked Game view using a separate display
Reproduction steps:
1. Open the attached project “leak.zip“
2. Open a second Game view window (Right click on Game view tab > Add tab > Game)
3. Undock the new Game view window from the Editor
4. Set the Display to “Display 2” in the second Game view Window and snap the window to any side (Windows button + right arrow)
5. Open "Assets/Scenes/SampleScene.unity" scene
6. Enter the Play Mode
7. Unfocus the Editor
8. Observe memory usage
9. If memory usage didn't change unsnap the second Game view
Expected result: Memory usage is the same
Actual result: Memory leaks
Reproducible with: 2023.1.0b1, 2023.1.0b19, 2023.2.0a16
Couldn't test with: 2021.3.26f1, 2022.3.0f1, 2023.1.0a26 - (step 4 cannot be done)
Reproducible on: Windows 10
Notes:
Allocated memory goes back down to normal after focusing the editor again
Snapping Game view might not be necessary, but seems to be more consistent that way
GPU usage seems to go up a lot from undocking the second Game view
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
- TreeView drag and drop operation is not cancelled when a modal opens over it
- Remote Config window causes performance drop in Editor when multiple settings are added
- Property field override bar does not update transparency correctly when switching between valid and invalid GameObjects
- Project window selection is not updated when search term is changed
- Error when adding valid MonoBehaviour script to Prefab in Project window
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-35177