Search Issue Tracker
Fixed
Votes
0
Found in [Package]
2.0.0a10
Issue ID
UVSB-701
Regression
No
2a10 Memory allocation caused by array-to-list conversion
[Original Issue link|https://support.ludiq.io/communities/5/topics/4952-2a10-memory-allocation-caused-by-array-to-list-conversion] - Opened by Lazlo. Has this already been addressed?
----
The Bolt 1 design choices of automatic enumerable-to-list and enumerable-to-array conversions can easily lead to avoidable memory allocation in Bolt 2, as well as unclear indication that we are working on a copy of the original collection.
Solutions to consider:
Removing these conversions (which may break Bolt 1 legacy graphs)
Native support for array units (more work but proper solution)
Intermediary solution of casting arrays to IList<T> under the hood (maybe using an automatic conversion) and using those strongly typed methods directly, until we have native array support. This would imply exposing/adding IList<T> to the default types, which may add confusion for non-technical users.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
Resolution Note:
Added native array support