Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.0f3
Issue ID
866796
Regression
Yes
Memory leak when moving mouse over scene
Reproduction steps (might need 2 screens):
1. Open project attached (UnityJump.zip)
2. Open scene "Scene_SP_BattleEncounter"
3. Make sure to monitor your memory usage. (Task manager will be enough)
4. Move mouse over scene (moving in circles will be enough) for about 5-15 seconds or until error Assertion failed on expression: 'SUCCEEDED(hr)' appears.
5. Move mouse away from scene.
Expected result: Moving mouse over scene will have no unpleasant outcomes.
Actual result: Memory leak appears, possible crash of Unity, others programs and pc itself.
Note: Gif attached for reference.
Turning off scene lightning seems to make this issue disappear. Also while using profiler with GPU Usage memory leak disappears.
Deleting all scripts did not fixed this problem.
Might appear only on one monitor so if you can not reproduce problem on one monitor, transfer scene window to another.
Sometimes you need to select objects and then move mouse over scene.
Were not able to reproduce on new scene.
Reproduced on: 5.5.0f3, 5.5.0p4, 5.6.0b3.
Referring to user it is regression that was introduced in 5.4
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
This is a duplicate of issue #869375