Randomly, on 3 files in the test corpus, xpress-huffman compression causes access violations. It doesn't do these every time, but frequently enough. They all seem to be about the same rarity.
The 3 files are geo and paper2 from the Calgary corpus (102400 and 82199 bytes respectively) and xargs.1 from the Canterbury corpus (4,227 bytes).
The access violation for geo always happens at an address ending with 0x2C31. For paper2 it is always 0x0C3A (except once 0x3C3A). The geo access violations are a bit more unpredictable, but have shown up at addresses ending with 0x4DF3 (twice), 0xF14B, 0x59A3, and 0x7B1B.
Randomly, on 3 files in the test corpus, xpress-huffman compression causes access violations. It doesn't do these every time, but frequently enough. They all seem to be about the same rarity.
The 3 files are geo and paper2 from the Calgary corpus (102400 and 82199 bytes respectively) and xargs.1 from the Canterbury corpus (4,227 bytes).
The access violation for geo always happens at an address ending with 0x2C31. For paper2 it is always 0x0C3A (except once 0x3C3A). The geo access violations are a bit more unpredictable, but have shown up at addresses ending with 0x4DF3 (twice), 0xF14B, 0x59A3, and 0x7B1B.