Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0b12
Issue ID
783736
Regression
Yes
[AMD-only][Animation][GLCore] Memory leak and crash having high poly meshes with animations
Steps to reproduce:
1. Open Unity with command line argument -force-glcore (or 4.5 or 4.0)
2. Download and import attached project. (Animation-Lag.zip)
3. Open scene: Animation-lag
4. Make sure your game view is not a separate window.
5. Play.
6. Move with mouse around.
7. Resize the Unity window or disattach game view, or change the layout in any way.
8. Move again with mouse around.
9. Look at task manager or any other app to inspect the used RAM by process.
Expected result: Memory allocation does not grow when moving with mouse around.
Actual result: Memory leaks somewhere, used RAM does not stop growing until it crashes Unity editor on DrvPresentBuffers
Notes: reproduces with both 4.5 and 4.0 OpenGL versions
Regression from: 5.3.3f1 (910d71450a97)
Reproduced on: 5.4.0b14, 5.3.4f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #788812