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
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
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?