Search Issue Tracker
By Design
Votes
0
Found in
5.6.5f1
Issue ID
1015100
Regression
Yes
[Particle System] Increasing memory usage between each version
Steps to reproduce:
1. Open user attached project
2. Open profiler and play the scene
3. Select the Memory Usage tab
4. Choose the "Detailed" mode if the memory profiler
5. Select System Memory and compare the usage results with other versions of Unity of "Particle System"
Expected result: Since 5.6.0a3, memory usage of Particle System in the editor has almost doubled. If possible, Particle System could use some optimization.
Test results:
2018.2.0a5 67.0KB
2018.1.0b11 67.0KB
2017.3.2f1 60.6KB
2017.2.2p1 59.3KB
2017.1.3p2 58.0KB
5.6.2p2 54.6KB
5.6.0b1 42.7KB
5.6.0a3 38.7KB
5.6.0a2 34.7KB
5.6.0a1 36.7KB
5.5.5p1 36.8KB
5.4.6f3 40.6KB
5.3.8p2 35.5KB
Does not occur testing on Standalone
Reproduced in: 2018.2.0a5, 2018.1.0b11, 2017.3.2f1, 2017.2.2p1, 2017.1.3p2, 5.6.2p2
Regression introduced in 5.6.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Add comment