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
- Adaptive Probe Volumes Fails to Bake with Dilation Enabled and exception "Cannot allocate more brick chunks, probe volume brick pool is full" is printed
- AssertionException thrown and Mesh turns invisible when changing Material Offset manually via the Inspector or through SetTextureOffset() on a Mesh with more than one Material
- NavMesh is not usable when using empty Bounds in BuildNavMeshData
- A 404 page is opened when selecting "Open Documentation" for any SpeedTree Sub-graph Asset
- A 404 page is opened when selecting "Open Documentation" for any custom Sub-graph in Shader Graph
Add comment