Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f3
Issue ID
912521
Regression
Yes
GZipStream not reading correctly from stream if Flush() is called
Reproduction steps:
1. Open an attached project on 5.6.0f3
2. Press play
3. Observe the console output, first log is bytes written to stream, second log is bytes loaded from file to stream. They are identical.
4. Open the same project on 5.6.1f1
5. Press play
6. The bytes written/loaded are not the same anymore
Not reproduced on: 5.6.0f3
Reproduced on: 5.6.0p1, 5.6.1p2, 2017.1.0b8, 2017.2.0a3
Regression introduced on: 5.6.0p1
---
Users should use Close instead of Flush on the GZipStream. The reason why using Flush worked before, was due to a bug in Mono.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment