OHIF Viewer errors

173 views
Skip to first unread message

Alex

unread,
Oct 5, 2023, 6:10:53 PM10/5/23
to xnat_discussion
Hi,

Some of our users complained that they had problems opening their recent studies in OHIF Viewer. These studies came from Siemens scanners (XA30). 

The error I'm seeing in the Viewer is: "ViewerMain: Loading CSS chunk 13 failed."

In the browser console I'm seeing approximately 1500 requests to the server and numerous net::ERR_INSUFFICIENT_RESOURCES errors. The OHIF Viewer log shows nothing suspicious. Tomcat and web server logs also show no related errors.

I was able to view the same study with the legacy XNAT viewer. 

The attached screenshot show what the error looks like in the Viewer interface. 

Any suggestions on what else can I check to figure out what is causing these issues?

Thanks,
Alex

2023-10-04 14_05_07-XNAT OHIF Viewer - Brave.png
2023-10-04 14_06_51-XNAT OHIF Viewer2.png
XNAT OHIF Viewer and 41 more pages - Profile 1 - Microsoft​ E.png

Alex

unread,
Oct 5, 2023, 11:00:15 PM10/5/23
to xnat_discussion
Forgot to mention that I'm running XNAT 1.8.8 and OHIF Viewer 3.5.3.

Mo Al Sa'd

unread,
Oct 6, 2023, 7:42:45 AM10/6/23
to xnat_discussion
Hi Alex,

Could you please send us an anonymised version of the data you are using? So we can try to reproduce this issue.

Kind regards,
Mo

Mo Al Sa'd

unread,
Nov 6, 2023, 4:20:06 PM11/6/23
to xnat_discussion
Hi Alex,

Thank you for sharing the data.

The viewer parses and organises the scans into "displaysets". That is, a displayset is created for each XNAT scan. A separate displayset is also created for each multiframe (enhanced) instance. So, for a scan with two multiframe instances, the viewer generates two displaysets with two thumbnail entries in the scan browser panel.

The data you have shared has 20 scans with a total size of 2.8 GB. Scan number 9 consists of 1,100 multiframe instances. The viewer attempts to eagerly load all the instances in order to create the individual displaysets representing each multiframe instance, which ultimately runs into the net::ERR_INSUFFICIENT_RESOURCES error due to the browser's maximum memory limitation.

As a workaround for this issue and for Google Chrome, you can increase the memory limit by setting the --max_old_space_size parameter when launching the browser from a shell in Linux, or as an argument to the shortcut path in Windows. I was able to display the data with --max_old_space_size=4096. Please note that there should be enough RAM memory available of 16 GB on the machine you are using.

Kind regards,
Mo

Charlie Moore

unread,
Nov 6, 2023, 4:32:58 PM11/6/23
to xnat_discussion
Hi Alex,

I'd also recommend reading through some of the other "XA30" threads on the discussion group here (and the dcm2niix repos). In a previous post, I linked to some pretty dire warnings from the dcm2niix folks about dealing with this type of data: https://groups.google.com/g/xnat_discussion/c/3eQgAaJ-t4U/m/0PCoQHEAAwAJ .

Thanks,
Charlie Moore

Reply all
Reply to author
Forward
0 new messages