corruptDataSkipped

Packets and frames this decoder skipped as damaged since it was opened, or since flush.

Zero for healthy input. Non-zero means the decoded result is INCOMPLETE: under CorruptData.Skip, which is the default, damaged data is dropped and decoding continues, and this counter is the only way to find out that it happened. Under CorruptData.Fail the first damage throws instead, so this stays zero.

Packets and frames this decoder skipped as damaged since it was opened, or since flush.

Zero for healthy input. Non-zero means the decoded result is INCOMPLETE: under CorruptData.Skip, which is the default, damaged data is dropped and decoding continues, and this counter is the only way to find out that it happened. Under CorruptData.Fail the first damage throws instead, so this stays zero.

Packets and frames this decoder skipped as damaged since it was opened, or since flush.

Zero for healthy input. Non-zero means the decoded result is INCOMPLETE: under CorruptData.Skip, which is the default, damaged data is dropped and decoding continues, and this counter is the only way to find out that it happened. Under CorruptData.Fail the first damage throws instead, so this stays zero.

Packets and frames this decoder skipped as damaged since it was opened, or since flush.

Zero for healthy input. Non-zero means the decoded result is INCOMPLETE: under CorruptData.Skip, which is the default, damaged data is dropped and decoding continues, and this counter is the only way to find out that it happened. Under CorruptData.Fail the first damage throws instead, so this stays zero.

Packets and frames this decoder skipped as damaged since it was opened, or since flush.

Zero for healthy input. Non-zero means the decoded result is INCOMPLETE: under CorruptData.Skip, which is the default, damaged data is dropped and decoding continues, and this counter is the only way to find out that it happened. Under CorruptData.Fail the first damage throws instead, so this stays zero.