Search Issue Tracker
Fixed
Fixed in 6000.5.0a2
Votes
0
Found in
6000.5.0a1
Issue ID
UUM-127044
Regression
No
Interpolated string incorrectly flagged as object allocation
How to reproduce:
- Open the “2218818.zip“ project
- Open Window → Analysis → Project Auditor
- Expand Code and select “Code“ on the Left
- Under the Filters section in the center, expand “Array Allocation”
- Observe the item below the “Array Allocation“
Expected result: The Object is displayed as a ‘String’ allocation under the “Object Allocation” header
Actual result: The Object is displayed as an ‘Object’ array allocation
Reproducible in: 0.10.0, 1.0.2 (6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4, 6000.5.0a1)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 6000.5.0a2):
This is actually the correct behaviour, because using string.Format with 4 or more format parameters, causes them to be put into an object[] array.
However, because the message we provide isn't making the problem obvious, I have modified the issue message to try and make this clearer.