Memory Leak on every image load

[radhikamattoo]

Hi everyone,

We use cornerstone to render DICOM images within my company's web-based viewer. As we've moved on to rendering CT images, we've noticed the viewer slows down significantly the more it is used, indicating a memory leak. After testing different parts of our codebase we could see the heap size increase significantly with each image load.

I've created a repo with a reproducible example that has the minimum requirements for loading an image. I've also included the two images I used while testing this example. After you load each image and take a heap snapshot, you can see the size continuously increase:

This isn't a big issue when working with smaller images, but as you scale up the image size/amount this problem scales in parallel.

[gogara91]

Hi @radhikamattoo ! This is also happening to me, but my files are like 30mb. This was happening on stack scroll. It would end up eating up to 2gb memory, which is unacceptable. I was reading a lot of stuff and I believe that the problem is with files being decoded inside browser, but garbage memory isn't collected correctly.

I was searching for other options and I believe that i found one:

• I broke dicom multiframe to multiple single frame JPEG-s using dcmtk.
• I'll probably set the server up in a way that it will return array of urls which should be loaded
• I also included cornerstoneWebImageLoader: cornerstoneWebImageLoader.external.cornerstone = cornerstone;

The result is much faster scroll through frames, no browser blocking by javascript while waiting for it to decode frames

I hope this helps with your problem!

[ITCore99]

hello @radhikamattoo I also encountered the same problem. Have you solved it? How