Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.4.11f1
2018.3.0a1
2018.3.8f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
Issue ID
1160492
Regression
No
Memory leaks when instantiating Sprite GameObjects
How to reproduce:
1. Open the attached project
2. Build for iOS and deploy the Xcode project to the iOS device
3. Go to Xcode-> Open Developer tool-> Instruments-> Leaks
4. Profile the Player
5. Press Toggle Active, then Destroy
6. Inspect the leaks
Actual: Memory leaks when instantiating Sprite GameObjects
Reproducible with: 2017.4.29f1, 2018.3.14f1, 2018.4.3f1, 2019.1.7f1, 2019.2.0b8, 2019.3.0a3
Reproducible with: Metal and OpenGL on iOS and also with Metal and OpenGL on macOS
Reproducible with:
iPhone 7 (iOS 10.2)
iPad Mini 4 (iOS 11.4)
Note: The leak will NOT occur if the "Toggle Active" button is used to activate the SpriteRenderer before it is destroyed.
The leak will still occur if the SpriteRenderer objects are destroyed via UnloadSceneAsync (with the condition of not having been activated). This test can be run by using the "SceneLoader" scene to load and then unload the "SpriteLoader" scene.
Could not test on earlier versions because the Player crashes
Could not test with 2019.3.0a4 and above because Xcode build fails
Additional steps:
1. Make a macOS standalone build
2. Open Xcode and create a new project
3. Edit scheme to your created build
4. Run and profile it
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment