Search Issue Tracker
By Design
Votes
0
Found in
2020.1
2020.1.0b14
2020.2
Issue ID
1261033
Regression
No
[Profiler] Autoconnect Profiler build setting opens a new Profiler instance even when a standalone Profiler window is open
Reproduction steps:
1. Create a new project or open an existing one
2. Open standalone Profiler (Window -> Analysis -> Profiler (Standalone Process))
3. Open build settings (File -> Build Settings...)
4. Enable "Development Build " and "Autoconnect Profiler"
5. Build and run
Expected result: Standalone Profiler is connected to the build
Actual result: A new Profiler instance is created and connected to the build
Reproduces on: 2020.1.0f1, 2020.2.0a18
Reproduced on platforms: Android, Windows standalone
Notes:
The issue is not reproducible on Unity 2019.4 and below because standalone Profiler is not available
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Standalone Profiler is an independent Unity instance and must have its own connection to Unity Player. This might be addressed in the future when we added multi-connection support for Unity Player debug link.