Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X
Votes
0
Found in
2021.3.19f1
2022.2.8f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
6000.0.0b11
Issue ID
UUM-27914
Regression
No
Profiler shows wrong call stack information when profiling a player that is built using Visual Studio
Reproduction steps:
1. Open the attached project “ProfilerBug”
2. Open the Visual Studio Solution “Project location/Build/profiler_callstack”
3. Build the player via the Visual Studio Editor
4. Open the Profiler Window>Analysis>Profiler
5. In the Profiler controls section enable Call Stacks
6. In the Module details panel search for “gc.alloc”
7. In the Module details panel change the No Details option to Related Data
8. In the player press the button called “Button”
9. Observe the call stacks shown in the Profiler
Expected result: The call stack list does not contain the call stack “FileIndex”
Actual result: Call stack “FileIndex” appears in the call stack list
Reproducible with: 2021.3.19f1, 2022.2.8f1, 2023.1.0b6, 2023.2.0a4
Couldn't test with: 2020.3.45f1 (Profiler does not show any data)
Reproducible on: Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
Add comment