Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2022.1.0a2
2022.1.0a4
Issue ID
1354361
Regression
Yes
[Linux] Switching between profiling modes throws Should not be capturing when there is a hotcontrol warning
How to reproduce:
1. Create a new project
2. Open the Profiler window
3. Check if the recording is enabled
4. Switch between Play Mode and Editor Mode Profiling options
5. Observe the console window (The issue is not consistent, so it may take a couple of tries to trigger the message)
Expected results: No warnings or errors are thrown
Actual results: "Should not be capturing when there is a hotcontrol" warning is thrown
Reproducible with: 2022.1.0a2, 2022.1.0a4
Not reproducible with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1, 2021.2.0b5, 2022.1.0a1
Notes:
1. Issue seems to happen only on Ubuntu platform (Tested with Ubuntu 20.04). The issue does not occur with macOS 11.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment