Because the VR type "UV" has its 32-bit length not properly accounted for, reading a value of this type slightly offsets the read. The next item to be read then also ends up incorrect, further worsening the offset. The parsing spirals out of control, leaving all the data past the "UV" tag unsalvageable (unless luck is on your side and the parser accidentally stumbles back into the right offset).
For this reason, I've implemented a possible fix: #280
However, this implementation might suffer from a lack of backwards compatibility, due to my use of BigInts. Do let me know if that's an issue and I'll look to ways of fixing it.
Because the VR type "UV" has its 32-bit length not properly accounted for, reading a value of this type slightly offsets the read. The next item to be read then also ends up incorrect, further worsening the offset. The parsing spirals out of control, leaving all the data past the "UV" tag unsalvageable (unless luck is on your side and the parser accidentally stumbles back into the right offset).
For this reason, I've implemented a possible fix: #280
However, this implementation might suffer from a lack of backwards compatibility, due to my use of
BigInts. Do let me know if that's an issue and I'll look to ways of fixing it.