Dear Michael,
This is indeed very surprising. This is the first time I hear about such an issue.
Unfortunately, we need more information to be able to reproduce this crash. Please provide a systematic way to independently reproduce it (including DICOM data), so that we can work on a fix.
TIA,
Sébastien-
I’ve reviewed the code and found only one place where this exception could be thrown (and eventually not be caught).
It might happen when trying to convert an invalid DICOM file to JSON (or empty file or ???).
Hopefully, thanks to this change: https://bitbucket.org/sjodogne/orthanc/commits/65b20d922e1039d3e2da75492b401fc84463e2e6, it should now send an exception instead of crashing
But, if you can reproduce the crash, we’re still interested in faulty files so we can test the patch.
Br
Alain