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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment