Search Issue Tracker
Fixed in 2018.3.X
Votes
2
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1062789
Regression
Yes
Unity Profiler sometimes fails to attach to a Windows standalone build
How to reproduce:
1. Open user-submitted project (Scriptable Object Framework.zip)
2. Build the project with "Autoconnect Profiler" option ticked
3. Run the build and observe profiler
Expected result: Unity profiler always connects and profiles a standalone build
Actual result: Unity profiler sometimes fails to connect and profile a standalone build
Reproducible with: 2018.2.0f2
Not reproducible with: 2018.1.9f1
Could not test with: 2018.3 (Project is not compatible)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment