Search Issue Tracker
Not Reproducible
Votes
0
Found in
Issue ID
853495
Regression
No
Memory leak after reimporting assets in the SRL
Build: Unity Editor v 5.6.0a5 (64-bit)
Platform: Windows 10 (64-bit)
Project: ScriptableRenderLoop
Clicking 'Reimport' on an asset folder causes the memory consumption of the "Unity Editor" process to go up.
Depending on the size of the folder, it could be several hundred MB at a time.
This memory is never released, so if you perform this action multiple times, then the Editor eventually runs out of memory and crashes.
Tested scenes:
- FPTL.unity
- GlobalIlluminationTest.unity
- HDRenderLoopTest.unity
- LayeredLitTest.unity
I just reimport the entire "Assets\ScriptableRenderLoop" folder.
Comments (2)
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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
MrG
Dec 14, 2016 00:59
Addendum to the steps to reproduce...before doing Reimport, go to packages folder and double-click the Shaders package, followed by the other two MCS___ packages there (in that order). when all that is done, then do reimport from the top level folder.
MrG
Dec 14, 2016 00:42
I can reproduce this 100% on a Win 2012-R2 server with dual Zeon 2.4's (total 16 cores) and 16GB RAM and 1.5TB on a RAID 5...I can kill the server with a folder reimport of Morph3D free assets from the store and nothing else. Unity 5.5.0f3. Create empty project, import all 4 free Morph3D assets, right-click top level Morph3D folder and select reimport all, watching task manager memory...it won't take long for the machine to die of resource starvation.