Viewer crashes with "Aw, Snap" in Google Chrome for Windows when rendering ~1GB multiframe DICOM file in main viewer

[Z-Kate Alpert]

Works fine on Chrome for Mac and fine on Windows Edge and Windows Firefox.

To reproduce:

• Upload ~1GB multiframe DICOM scan to session (test case we used was 700MB)
• Open viewer for this session
• Double click multiframe scan or drag the multiframe scan into main viewer
• After loading % in main viewer reaches 100%, the “Aw, Snap” crash will occur.

From discussion with James Petts:

• Your OS can limit how much memory your browser can use, and as of now, unfortunately, there aren’t many good ways to check how much memory is “left” to be used.
• We’ve toyed with the idea of statically allocating memory on launch until an ArrayBuffer allocation fails (which happens gracefully), then removing refs to this memory so the garbage collector removes it, so as to at least get a feel for the amount of memory you can reasonably use… But then you open up two instances and you are screwed.