Search Issue Tracker
Active
Under Consideration for 6000.2.X
Votes
0
Found in
6000.2.0b11
6000.2.0b12
Issue ID
UUM-112860
Regression
Yes
Profiler is not able to flush data to a file or socket warning thrown after Auto connecting Profiler to Build Create
Steps to reproduce:
1. Create new Unity project
2. Open Build Profiles window
3. Select Development Build and Autoconnect Profiler
4. Press Build And Run button
5. Once project is build, observe the Console window
\\
Actual results: Warnings are thrown in the Console window
Expected results: No warnings in the Console window
\\
Reproducible with versions: 6000.2.0b11, 6000.2.0b12, 6000.3.0a2
Not reproducible with versions: 6000.2.0b10, 6000.3.0a3
\\
Tested on (OS): macOS Silicon, Sequoia 15.5
\\
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Add comment