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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment