Search Issue Tracker
By Design
Votes
0
Found in
2020.3.37f1
2021.3.8f1
2022.1.12f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10525
Regression
No
[CentOS 7][Rocky 8] Standalone Profiler does not record data when profiling, Target cannot be changed to Editor
How to reproduce:
1. Open any project
2. Navigate to Window > Analysis > Profiler (Standalone Process)
3. Enter Play Mode in the Editor and Start Recording in the Standalone Profiler
4. Observe the Data Graph
5. Click on "Playmode" in the Profiler to see options for choosing your Target
Actual result: No data is being recorded, Profiler Target cannot be changed to Editor
Expected result: Data is recorded and visualized in the Profiler and the Editor is available as a Target
Reproducible with: 2020.3.37f1, 2021.3.6f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4
Couldn't test with: 2021.3.5f1 (Crashes on opening Standalone Profiler, UUM-5543)
Tested on: CentOS 7, Rocky 8 (Not reproducible on Ubuntu 18.04)
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
The profiler cannot connect to the editor so it's not displaying all the options nor allows you to profile. This can be worked around by clearing your iptables with `iptables -F`