What happens:
http://www.stillhq.com/pdfdb/000590/data.pdf causes PDFsharp to emit the warning "Invalid number of operands".
(Note: this pdf later causes PDFsharp to run out of memory. See
http://forum.pdfsharp.net/viewtopic.php?f=3&t=3411 .)
Cause:
This pdf contains an LZW-encoded contents stream. When decoding this stream, PDFsharp fails to emit some bytes.
Here's a diff between the data as decoded by QPDF and PDFsharp (the 0A bytes at the beginning and end may or may not be significant):
— 000590-obj3-qpdf.txt 2016-02-16 11:39:45.635258700 +0100
+++ 000590-obj3-pdfsharp.txt 2016-02-16 11:40:00.814040300 +0100
@@ -1,3 +1,4 @@
+0A
71
0D
30
@@ -142,7 +143,6 @@
2E
33
33
-33
20
54
63
@@ -10470,7 +10470,6 @@
2E
31
31
-31
20
39
37
@@ -10710,7 +10709,6 @@
2E
39
39
-39
20
37
33
@@ -25930,7 +25928,6 @@
30
20
30
-20
30
20
6B
@@ -30328,4 +30325,3 @@
0D
66
0D
-0A
Note:
It would also be nice if the LZW decoder supported /EarlyChange .