Search Issue Tracker
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).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- CIL Linker errors are thrown when building with IL2CPP/WebGL
- Some normal maps has ripple effect and appears to be lower in quality when using default compression settings
- <color=red><></color> does not work with 呸 symbol
- Warning on affected shader count is not thrown when trying to collect shader variants with Async Shader compilation enabled
- Japanese diacritic symbols are missing from the build executable file when building the project