Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.1.0a22
2020.1.0b9
2020.2
Issue ID
1246165
Regression
Yes
[OSX] Memory leak occurs when cursor is hovered over multiple Inspector windows
How to reproduce:
1. Open the "1246165" project and select "Main Camera" in the "New Scene" Scene
2. Make sure the Camera component is visible in the Inspector windows
3. Hover the cursor over the Inspector windows/Camera components
Expected result: a memory leak does not occur
Actual result: memory slowly increases as the cursor is moved over the Inspector windows
Reproducible with: 2020.1.0a22, 2020.1.0b9, 2020.2.0a1, 2020.2.0a11
Not reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0a21, 2020.1.0b10, 2020.1.0b10, 2020.2.0a12, 2020.2.0a13
Notes:
1. The Inspector needs to be docked in the Editor for the memory leak to occur.
2. The leak is more noticable when multiple Inspectors are docked in the Editor and the inspected object has an unfolded Camera component.
3. Reproducible in these versions:
3.1. 2020.1.0a22-2020.1.0b9
3.2. 2020.2.0a1-2020.2.0a11
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12