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
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
Add comment