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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
Add comment