Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0b4
Issue ID
878470
Regression
No
Misleading 'OS error: The operation completed succesfully' when hard drive fills up during asset import
Misleading error dialog when hard drive fills up during asset import and creation of meta files
Steps to reproduce:
1) Make a new project in Unity, save, and close it.
2) Generate a large number of files inside the unity project that almost fills the hard drive but not quite.
3) Launch Unity and open the project so it starts importing the assets and generating meta files
4) Eventually get a dialog saying "Writing library/metadata/<some number>/<some hash> Unable to write file. OS error: The operation completed succesfully."
Reproduced: 5.6.0b4, 5.6.5f1, 2017.1.2p4, 2017.2.1p1, 2017.3.0p1, 2018.1.0b1
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [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
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team