Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b1
Issue ID
924578
Regression
Yes
[Win] Building of several players to the same folder can cause errors
If user builds several players to the same project folder on Windows and keep players running, errors appear.
To repro:
1. Create a project.
2. Press Build and Run, save scene and exe.
3. Keep player running.
4. Return to Unity and press Build and Run again.
Actual result: Data folder is not created.
If several players build this way are running, CPU is 100% loaded and Windows fails.
Errors in log:
IOException: Sharing violation on path Temp\StagingArea\UnityPlayer.dll" or "D:\UnityProjects\ws-echo1\UnityPlayer.dll
System.IO.File.Copy
Build completed with a result of 'Failed'
UnityEditor.BuildPlayerWindow+BuildMethodException: 3 errors
Expected result: Fewer players should be built with no errors.
As potential solution, UnityPlayer.dll should be moved to Data folder.
Behaviour changed in 2017.2.0a1.
Works as expected in 2017.1.1.f1
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Miscellaneous
Apr 08, 2018 01:33
How can this be BY DESIGN?
Building anything with Networking, and you will run into situations where multiple standalone clients are indeed needed for testing, previous version supported this, right?