Search Issue Tracker
Fixed in 5.5.2
Votes
1
Found in
5.5.0p1
Issue ID
861347
Regression
Yes
[Shuriken] Using Sub Emitters on Particle Systems cause memory leaks
When Sub Emitters are used, memory is continuously leaked until the app crashes.
Steps to reproduce:
1) Open the latest attached project (ParticleLeakRepro.zip).
2) Build for any platform (Mac, Windows, iOS).
3) Run and monitor the memory usage. (I used Instruments with Allocations tool on macOS)
The scene consists of several Particle Systems with Sub Emitters. Memory is leaked continuously when running this scene. On macOS, for example DynamicHeapAllocator<LowLevelAllocator>::Allocate(unsigned long, int) allocates 4 MB every ~30 seconds (starting at around 00:01:30). On iOS, 64 KB are allocated on every iteration of the Particle System playback, leading to a crash due to memory warnings.
- Pressing the 'Toggle Sub Emitters' UI button stops the leaking immediately.
Reproduced on:
5.5.0p2, 5.5.0f3
Did not reproduce:
5.6.0b1, 5.4.3p3
Devices tested:
MacBook Pro 2013 macOS sierra 10.12.1
iPhone 7 iOS 10.2.1
Should also occur on other platforms as well.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
swiftfinder
Mar 07, 2020 00:32
View the nearest Target locations on this page: https://findplacesnearme.com/target-stores/