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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment