Search Issue Tracker
Fixed
Votes
1
Found in
4.3.0f4
Issue ID
582772
Regression
No
Profiler keeps remote connection after closing
Unity standalone player is running in a Linux machine and the Unity editor is running on a Windows 7 machine.
- From the editor we open up the profiler and connect to player running in the Linux machine to profile the game.
- After we are done with the profiler, close the profiler window (by pressing the 'x' button) or exit the Unity editor
- Note that the Unity player (in Linux machine) is still collecting profiler data even though nobody is consuming it. Because of this it is slow (== high CPU usage and low FPS)
- Expected behavior: upon profiler window close or editor exit, the Linux player should stop collecting profile data and go back to "normal" operation
This issue is reproducible in any unity project (the issue is in Editor). If you have a somewhat heavy Unity game and has a mechanism to display FPS on screen, you can notice that (without connecting profiler, FPS will be at certain number, after connecting profiler it will come down, when you close the profiler window or editor, it will still remain at low FPS).
Comments (1)
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
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
- UI breaks when Multiplayer Center window section divider is moved too far
- Adaptive Performance documentation link leads to outdated package documentation when the documentation hyperlink is pressed in the Project Settings window
skarphace
Jan 20, 2017 03:12
I'm seeing a potentially similar problem in 5.4, with a windows client. In fact, it appears the Editor profiler is still even connecting to that same client whenever the client starts. I can only stop it by going into the profiler and selecting 'Editor' as the 'Active Profiler'.