Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.37f1
2021.3.8f1
2022.1.12f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10523
Regression
No
[CentOS 7] 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.5 (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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note:
The issue is caused by iptables on centos blocking the broadcast message. Removing the iptable rules helps it connect. Perhaps there should be a better disconnected message indicating the problem?
Resolution Note (2023.1.X):
The issue is caused by iptables on centos blocking the broadcast message. Removing the iptable rules helps it connect. Perhaps there should be a better disconnected message indicating the problem?