Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2021.1.X
Votes
0
Found in
2021.1.0a7
2021.1.0b6
Issue ID
1293246
Regression
Yes
[Profiler] Errors after switching from Main Thread to another in Editor profiling
To reproduce:
1. Enable Editor Profiling.
2. Enter Playmode, profile a bit,
3. Stop Profiling.
4. Exit Playmode.
5. In (Raw) Hierarchy select e.g. Profiler.DataDeserializer, and find Semaphore.WaitForSignal there.
6. Enable Profiling again.
7. Click on something in graph in CPU Usage.
8. Errors fail:
Missing Profiler.EndSample (BeginSample and EndSample count must match): ProfilerFrameDataTreeView.MigrateSelectedState) .
Actual result:
You're locked in Profiler.DataDeserializer view.
Whatever you do next - enter playmode, change views - you're always there. See screenshot.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Add comment