Code Monkey home page Code Monkey logo

Comments (4)

yagni avatar yagni commented on June 16, 2024

Thanks for the report @OzgeYurtsever. Any chance you could attach some DICOM that's causing the problem? That would help troubleshoot it quicker. Please make sure it doesn't contain any identifiable information.

from dicomparser.

OzgeYurtsever avatar OzgeYurtsever commented on June 16, 2024

Thanks for your response @yagni. I am working on finding a deitentified multiframe image.

from dicomparser.

emelalkim avatar emelalkim commented on June 16, 2024

Hi @yagni, after conducting further troubleshooting, we have determined that the issue seems to be related to the size of the image. When attempting to load a larger uncompressed image, the OHIF viewer crashes almost immediately. However, in the case of compressed DICOMs, it takes longer for the crash to occur.

For testing purposes, you can download the same deidentified data from the following link: sample image

By using this larger multiframe DICOM image, you should be able to replicate the crashing issue more quickly. Please note that this sample data is specifically provided to investigate and address the challenges associated with loading large multiframe DICOM images and we were able to reproduce this issue only in Windows machines.

from dicomparser.

yagni avatar yagni commented on June 16, 2024

@OzgeYurtsever @emelalkim I think this might be a cornerstone3D issue, not a dicomParser issue.

  1. When I drop the file from @emelalkim into the DICOM dump with data dictionary example, it increases memory usage by about the size of the file. I can drop that same file multiple times and not see a memory increase. (Note that I had to comment out the console.log() and replace an innerHtml assignment with a JQuery .empty() call, but those are both specific to the example, not the core dicomParser code)
  2. When I drop the file into the local cornerstone3D example in a separate tab and scroll through a couple of slices, it easily gets up to 7GB and then goes out of memory. Further, it seems like the garbage collector isn't running in time, as I can trigger the garbage collector and it drops back down to ~600MB, which is around what I would expect.

I'll leave this open for now, but I would recommend filing this report in cornerstone3D issues. If it ends up being a parsing bug, we can come back here and dig in to it some more.

from dicomparser.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.