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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
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.