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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment