Search Issue Tracker
Fixed
Fixed in 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Votes
0
Found in
2021.3.19f1
2022.2.8f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
7000.0.0a1
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
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
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
- Shader Graph Material is left in broken state when switching from a .git branch with no HDRP to a branch that contains HDRP
Resolution Note:
postponed for Unity 7