Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.4.0f3
Issue ID
822255
Regression
Yes
Meshes constantly increasing while leaving Profiler open
Steps to reproduce:
1. Create New project and open it
2. Go to Window-Profiler
3. Check Memory field
4. Check Profile Editor and Current
5. Wait for ~10 minutes
Result: number of Meshes are continuously increasing and taking more memory.
Note: Number of Meshes returns to 0 after closing Profiler or just moving the window. If left for 30 minutes open, it can increase over 300 Mb (see attached picture).
Reproduced with Windows and Mac.
Reproduced with: 2017.1.0b1, 5.6.0p1, 5.5.0a5, 5.4.0f3.
Not reproduced with: 5.3.6p2, 5.2.5f1.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Satscape
Sep 04, 2017 20:40
I'm getting this on 2017.2.0b6 (Aug 10 2017) Linux editor. After about 40+ minutes it consumes over 3Gb and eventually crashes the OS :-(
The other thing is the meshes do not return to 0 as stated above, I have to totally close out of Unity to clear the memory. Is this reproducible for you guys with 2017.2.0b6 ?