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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment