IE11 fails to parse larger files that FF and chrome handle

[buddamus]

• Use a file that's bigger than 500mb
• drag into the following page in IE11 https://rawgit.com/cornerstonejs/dicomParser/master/examples/dragAndDropDump/index.html

Note: Large files can be found on this page: https://www.dclunie.com/pixelmedimagearchive/upmcdigitalmammotomocollection/index.html, inside the "Case2" file..

[swederik]

Hi there,

Thanks for the report.

Is there a specific error that comes up? I understand you are having issue, but I don't know if there is going to be anything we can do about it. Parsing a 500mb DICOM file in the browser probably isn't a great idea. Is that your only option?

Typically we would use e.g. WADO-RS RetrieveMetadata to retrieve the metadata for the file ahead of time, and then use WADO-RS RetrieveFrame to obtain each section of the pixel data frame by frame.

[buddamus]

In my application, the error I get is "dicomParser.readFixedString: attempt to read past end of buffer".. but on the dragAndDropDump page the error is "Typed array constructor argument is invalid"... the dragAndDropDump error seems to be IE11 being its horrible self.

Yes, I need to parse a large file(s) into memory. The application I'm working on requires the uint8array to be in memory.

[Ragnar-Oock]

The issue most likely comes from the maximum buffer size in IE. I can't test it right now because I don't have access to a pc that can run IE but if you do you can find the maximum allocable aaray buffer size by running the code provided in this stack overflow anwser. https://stackoverflow.com/questions/17823225/do-arraybuffers-have-a-maximum-length

[yagni]

I'm going to go ahead and close this since IE11 reached end of life in 2022. We can open a new issue if this comes up for any active browsers.