Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a2
Issue ID
598396
Regression
Yes
Memory leak when doing grid slicing
- Import the attached UNET - LowLevel.jpg file
- Set Tecture type to Sprite and Sprite Mode to Multiple
- In the Sprite Editor select Grid Slicing and slice the image
- Press Apply
Result:
!GetPersistentManager().IsStreamLoaded(metaDataPath)
UnityEditor.AssetDatabase:StopAssetEditing()
UnityEditor.SpriteEditorWindow:DoTextureReimport(String) (at C:/clones/uGUI/Editor/Mono/SpriteEditor/SpriteEditorWindow.cs:1045)
Asset import did not unload metadata path. This will leak memory. File a bug with repro steps please.
UnityEditor.AssetDatabase:StopAssetEditing()
UnityEditor.SpriteEditorWindow:DoTextureReimport(String) (at C:/clones/uGUI/Editor/Mono/SpriteEditor/SpriteEditorWindow.cs:1045)
This is a regression compared to Unity 4.6.0b5. The whole process of slicing and applying the changes also takes much, much longer than before (probably caused by the memory leak)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment