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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment