Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.6.0b3
Issue ID
594320
Regression
No
Foreach statements allocate memory unnecessarily
To reproduce:
1) Open 'demo' scene
2) Enter playmode and record the scene in the Profiler. Observe that ForeachAllocTest.Update() allocates 24 bytes.
3) Toggle 'Use Explicit' on the Foreach Demo object
4) Record a few more frames in the Profiler. Observe that now ForeachAllocTest.Update() allocates 0 bytes.
Examine the code and you'll see both code paths do the same thing.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment