r5sdk/r5dev/thirdparty
Kawe Mazidjatari 9de5f4988f RTech: fixed streamed pak decoding progression bug
During beta tests on a Linux system, we encountered an issue where the I/O could be slower and thus result in not enough bytes being streamed by the time we invoke the decoder (lenStreamed == bufSizeNeeded at this point), after 16 calls with lenStreamed == bufSizeNeeded, the engine errors as ZSTD_NO_FORWARD_PROGRESS_MAX would be reached. Added value of 'ZSTD_nextSrcSizeToDecompress()' to 'PakDecoder_s::bufferSizeNeeded' to make sure we never call the decoder without any new streamed bytes. Also increased the value of ZSTD_NO_FORWARD_PROGRESS_MAX to 1024 since this fixed the issue without applying the aforementioned patch, this was increased as a hardening measure.
2024-06-01 11:43:09 +02:00
..
2024-04-05 16:21:45 +02:00
2024-04-05 16:41:09 +02:00
2024-04-05 16:21:44 +02:00
2024-04-05 17:58:51 +02:00
2023-07-03 00:25:15 +02:00
2023-09-09 14:50:11 +02:00
2024-04-05 18:40:36 +02:00