What about loading All dic images in cache and displaying simultaneously in viewports

[Nikhil Ghuse]

Hello all,

             I have been trying to implement web workers for Image Viewer to load and cache all images at one instant and then display in available view-ports.

Actually I have implemented it by finding all images from stack and looping and caching them but it takes much time and become unresponsive.

[Chris Hafey]

The dev branch of cornerstoneWADOImageLoader has support for decoding in web workers - have you tried that?

[Nikhil Ghuse]

yes I have gone through it... Actually I have implemented it completely but if there are images more than 1000 gets crash...

reference 'cornerstonewadoimageloaderwebworker'

if (signed) {

        "if(Int16Array.from) {

          image.pixelData = Int16Array.from(src32);"

        } else {

          image.pixelData = new Int16Array(length);

          for(var i=0; i < length; i++) {

            image.pixelData[i] = src32[i];

          }

        }

      } else {

        if(Uint16Array.from) {

          "image.pixelData = Uint16Array.from(src32);"

        } else {

          image.pixelData = new Uint16Array(length);

          for(var i=0; i < length; i++) {

            image.pixelData[i] = src32[i];

          }

        }

And error generated in double quoted lines...

[Chris Hafey]

The code snippet you linked appears to be from the JPEG2000 decoder.  JPEG2000 decoding is very memory intensive and the line your get the error on has to do with memory allocation.  It may be that you are running out of memory, here are some things to try:

1) Use fewer web workers.  Each web worker consumes a lot of memory

2) Use another transfer syntax.  I would try explicit little endian, then jpeg lossless then jpeg-ls

Some questions for you:

How much RAM is on your computer?  

Are you using a 64 bit or 32 bit browser?  

Is the browser crashing or is an error displayed on the console?

Chris

[Nikhil Ghuse]

Hi Chris,

                 I have gone through your comment and what I have found is that you have suggested what I have already done...

1)Use less web workers

but I didn't get second point... 

And Following are those question which you want to know.

How much RAM is on your computer?  

- 4 GB

Are you using a 64 bit or 32 bit browser?  

-64 bit

Is the browser crashing or is an error displayed on the console?

-both error displayed in console then browser crash.

[Chris Hafey]

4GB may not be enough memory for decoding JPEG2000 images - see if your server can convert the images to another compression format.

[Nikhil Ghuse]

I don't want to change or convert images into other compression format. I need to use JPEG2000 only.

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Chris Hafey]

OK - not sure I can be of much more help then

[Nikhil Ghuse]

Is it possible or not...? 

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Chris Hafey]

Oh - did you try using the PDF.js codec?  Perhaps it will use less memory...

[JF Pambrun]

Does cornerstoneWADOImageLoader use the fixed or dynamic memory version of OpenJpeg-JS by default?

Looks like the fixed version is set to 4 GB (TOTAL_MEMORY=400000000).

JF

--
You received this message because you are subscribed to the Google Groups "cornerstone platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cornerstone-plat...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cornerstone-platform/633f739c-9e33-4f68-a77a-0d7dfc4a1e51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Hafey]

It uses the fixed for higher performance.  Good idea to try using the dynamic (or build the fixed with a smaller memory size)

On Tuesday, December 20, 2016 at 8:52:16 AM UTC-6, Jean-Francois Pambrun wrote:

Does cornerstoneWADOImageLoader use the fixed or dynamic memory version of OpenJpeg-JS by default?

Looks like the fixed version is set to 4 GB (TOTAL_MEMORY=400000000).

JF

On Tue, Dec 20, 2016 at 9:39 AM Chris Hafey <cha...@gmail.com> wrote:

Oh - did you try using the PDF.js codec?  Perhaps it will use less memory...

On Tuesday, December 20, 2016 at 3:57:01 AM UTC-6, Nikhil Ghuse wrote:

Is it possible or not...? 

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

Hello all,

             I have been trying to implement web workers for Image Viewer to load and cache all images at one instant and then display in available view-ports.

Actually I have implemented it by finding all images from stack and looping and caching them but it takes much time and become unresponsive.

--
You received this message because you are subscribed to the Google Groups "cornerstone platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cornerstone-platform+unsub...@googlegroups.com.

[Nikhil Ghuse]

I have use PDF.js codec by usePDFJS = true  and tried Dynamic memory version in CornerStoneWADOLoaderCodecs but still the same issue occurs

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Chris Hafey]

I just loaded a 1000 slice JPEG2000 CT study in our viewer with one web worker and chrome is using 1.66GB of RAM.  When I use 8 web workers, it took up 3.8 GB of RAM.  This is on Mac OS X Sierra 10.12.2.  What you are doing should be possible.

Chris

[Nikhil Ghuse]

It works fine with mac OS i have loaded 6500 images with 4 web workers in Safari.. But when I tried the same with chrome and on Windows platform it gets crash before 1000 images and same happens with IPad but crash occurs before 100 images.

Nikhil  

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Chris Hafey]

I just tried our viewer on Windows 7 with chrome and it loaded all 1000 JPEG2000 CT images.  Perhaps the problem is in your code?

[Nikhil Ghuse]

hi chris,

             I have tried for 1000 and it works in Windows 7 and Chrome what about more than 1300 CT images try for it..

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Nikhil Ghuse]

I have change Fixed memory to dynamic in Codecs.

On Tuesday, December 20, 2016 at 8:22:16 PM UTC+5:30, Jean-Francois Pambrun wrote:

Does cornerstoneWADOImageLoader use the fixed or dynamic memory version of OpenJpeg-JS by default?

Looks like the fixed version is set to 4 GB (TOTAL_MEMORY=400000000).

JF

On Tue, Dec 20, 2016 at 9:39 AM Chris Hafey <cha...@gmail.com> wrote:

Oh - did you try using the PDF.js codec?  Perhaps it will use less memory...

On Tuesday, December 20, 2016 at 3:57:01 AM UTC-6, Nikhil Ghuse wrote:

Is it possible or not...? 

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

Hello all,

             I have been trying to implement web workers for Image Viewer to load and cache all images at one instant and then display in available view-ports.

Actually I have implemented it by finding all images from stack and looping and caching them but it takes much time and become unresponsive.

--
You received this message because you are subscribed to the Google Groups "cornerstone platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cornerstone-platform+unsub...@googlegroups.com.

[Nikhil Ghuse]

hi chris ,

              A simple question what does  lastCachedImage.imagePromise.reject(); means .?('cornerston.js [line no 526]')

             There isn't any method reject in ImagePromise.

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[idm...@gmail.com]

Facing same issue on 32Bit windows with 4GB RAM using Chrome.

Where did you made those changes to allow dynamic memory allocation ?

[Nikhil Ghuse]

in CornerStoneWADOLoaderCodecs.js

[Chris Hafey]

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/reject

[Nikhil Ghuse]

On Wednesday, December 7, 2016 at 12:03:35 PM UTC+5:30, Nikhil Ghuse wrote:

[Nikhil Ghuse]

Actually there isn't  lastCachedImage.imagePromise.reject(); so i have initialized $.deferred and assigned it to  lastCachedImage.imagePromise so that It can reject the imagepromise.