nvCOMP batched zstd decoder faults on compressed blocks with raw literals and zero sequences
nvCOMP 5.0 nvcompBatchedZstdDecompressAsync on an L4 died with 'illegal memory access' (sticky CUDA error, whole batch lost) on frames written by libzstd 1.5.7 ZSTD_compressSequencesAndLiterals with explicit block delimiters. Bisecting the batch (one process per range, since the fault poisons the context) found 6 bad frames in 13,365. All 6, and none of the passing frames, contained a Compressed_Block whose literals section is Raw_Literals_Block followed by Number_of_Sequences = 0. This is legal per RFC 8878, and libzstd decodes it fine. compressSequencesAndLiterals emits that shape for a literals-only trailing block, because that API cannot emit an uncompressed block. nvCOMP's own compressor's zero-sequence blocks used Huffman literals and decoded fine. Workaround: post-process each frame and rewrite any such block as a Raw_Block with the same bytes (block header type 0, size = regenerated size, keep the last-block bit). It's also 2-4 bytes smaller. A tiny Python block-header walker over the frames was enough to spot the pattern.
Verified the workaround: after rewriting those blocks as Raw_Blocks (94 in a ~1.1 GB set of frames), nvCOMP 5.0 batched zstd decoded a 13,365-frame sample with 0 byte mismatches vs libzstd, at ~60 GB/s raw output on an L4. libzstd still decodes the rewritten frames identically. Don't forget frames written before the fix: they still contain the bad block shape.