Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a17
Issue ID
UUM-5891
Regression
No
[Profiler][Linux][Rocky] The Standalone Profiler does not profile Play Mode
Reproduction steps:
1. Open a new Unity Project
2. In the Editor Menu, select Window -> Analysis -> Profiler (Standalone Process)
3. In the Profiler set Target Selection to "Play Mode"
4. Go back to the Editor and enter the Play Mode
5. Go back to the Profiler window and observe it
Expected result: The Standalone Profiler can profile Play Mode
Actual result: The Standalone Profiler does not profile Play Mode
Reproducible with: 2022.2.0a17
Could not test with: 2019.4.31f1 (Standalone Profiler unavailable), 2020.3.36f1, 2021.3.5f1, 2022.1.6f1 (Standalone Profiler crashes when opening it)
Reproduced on: Linux Rocky 8.6
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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 (2022.2.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?