Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.3.0b9
2021.2.0a18
2022.1
Issue ID
1355812
Regression
Yes
[Profiler] GC Alloc call stacks have unrelated stack trace lines
Steps to reproduce:
1. Download the attached "UIToolkitSamples-master.zip" project
2. Open the Trade scene
3. Open profiler, activate "Call Stacks" with GC.Alloc option
4. Enter play mode and wait for a few frames to be recorded
5. Pause the game
6. Select the first frame
7. In the Timeline view of the profiler look through Magenta tiles called "GC.Alloc"
Expected result: The stack trace shows the correct stack for the allocation.
Actual result: The top line of the stack trace is unrelated
Reproducible with: 2021.2.0a18, 2021.2.0b7, 2022.1.0a5
Not reproduce with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0a17
Incorrect stack traces:
"get_rawType()"
"set_isPaused()"
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
- [ChromeOS] Pixelbook can switch to portrait orientations which result in vertical resolution that cannot be undone
- Compute Shader with RWBuffer<> type throws an error when it is compiled with Vulkan API
- [Device Simulator] When simulator window is narrow, toolbar controls deform and some become inacessible
- [Device Simulator] Only one Touch Input is recognized when using Device Simulator
- "PropertiesGUI() is being called recursively" warning produced when trying to open color picker when object picker is opened
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a8
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b13