Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4.26f1
2019.4.28f1
Issue ID
1340973
Regression
No
Unity crashes with "Fatal Error! The file 'MemoryStream' is corrupted!" ("IOException: Too many open files") when using Rider
How to reproduce it:
1. Open the project from Google Drive link "users_project.zip"
2. Open any script using JetBrains Rider
3. Try to edit the script and save it
4. Observe the Unity
Expected result: Unity doesn't crash
Actual result: Unity crashes with error: "Fatal Error! The file 'MemoryStream' is corrupted!"
Notes:
- Could not reproduce on my MacBook Pro 8-Core Intel Core i9 2.4 GHz 32 GB; Intel UHD Graphics 630 1536 MB Radeon Pro 5500M 8 GB
- Could be related to Asset Pipeline
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
- [iOS] Final Image misaligned when using "ScalableBufferManager.ResizeBuffers" to resize
- GameObjects are not updating when Materials and Cubemaps are updated from Environmental Reflections
- "Lens Flare (SRP)" Component is missing documentation link
- Reflection problems when unbaked Reflection Probes are present
- Light Explorer columns sorting arrow is too small
Resolution Note (fix version 2022.1):
The issue at hand was the and Android Logcat window was leaking PIPE handles, while polling for 'adb devices'.
Upon further debugging, it was discovered that the way external programs were launched was leaking PIPEs, and as such a larger fix has been made.
This is the ticket that fixes it: https://issuetracker.unity3d.com/issues/android-adb-functionality-leaks-a-pipe-causes-too-many-open-files-error
Backports have been scheduled for:
2021.2
2021.1
2020.3
2019.4