Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.2.1f1
Issue ID
1118859
Regression
Yes
[iOS] GraphicsPerf Particles Collision scene memory regression
To reproduce:
1. Clone this repo: https://github.com/cinight/GraphicsPerf or use project attached by QA
2. Switch platform to iOS
3. Build and run Particles Collision scene on iOS device
4. Inspect memory usage in debug window in Xcode
5. Compare results between 2018.2 and 2019.1 versions
Expected result: No spikes in memory usage, memory usage shouldn't increase in newer version
Actual result: Spike on app launch
Devices: iPhone XS iOS 12.0, iPhone 6s iOS 11.2.1, iPhone SE iOS 11.4.1
On iPhone SE and iPhone 6s app usually crashes with newer version.
Tested versions: Unity 2018.2.1f1 vs Unity 2019.1.0a14
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
Add comment