Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2018.1.0b6
Issue ID
1001595
Regression
No
Switching between Animations with AssetBundle, cause AnimationPlayableAsset remain in memory
How to reproduce:
1. Download attached project and open "A" scene
2. Enter Play Mode and press "Space" with keyboard (it will load "SampleScene" in "AssetBundles/s", simple scene will play a timeline loop)
3. Press "Space" again (will return from SampleScene to "A" scene)
4. Check Profiler -> Scene Memory -> MonoBehaviour , AnimationPlayableAsset still in memory
5. Repeat 2 -> 4 steps and Check Profiler, AnimationPlayableAsset will instance more than once
Actual result: Load one timeline in the scene via AssetBundle and then switch to another scene, cause AnimationPlayableAsset remains in memory
Reproduced with: 2018.1.0b7, 2018.2.0a1 (210ec0022b93)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment