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
- Greyed out Icon for Tool Context is misaligned in the Tools Overlay in the URP 3D Sample Template
- HDR colors are recorded in gamma compressed values instead of linear values when using the Animation window
- Scroll bar fails to resize when content is dynamically removed in Player or Play Mode
- Error "Shader error in 'Shader Graphs/ScrollingHologram_Graph" when switching HDR Debug Mode to Gamut View
- "Unable to add Renderer to the Scene after Culling.“ and “NullReferenceException: Object reference not set to an instance of an object“ errors spawned when changing the light shadow settings in the Player
Resolution Note:
Added native array support