Large DICOM image storage objects leads to crash about ruby-dicom HOT 5 CLOSED

That's quite a big DICOM file you've got there. Looking at the stack trace it's obvious that this is a memory issue.

I won't rule out that the ruby-dicom library might be consuming more memory than what might be possible to achieve, but Im inclined to think that you are running into a limitation of your actual computer system here.

How much memory do you have on this particular computer?

from ruby-dicom.

Hi Christoffer,

it is a VM machine that has 4GB RAM available. I have not tested it so far on a native machine, because I have to finish first my current task. If I have more information I will provide it to you, latest tomorrow.

Regards, Felix

Felix Petriconi
Development Manager
Certified Scrum Master (CSM)

MeVis BreastCare Solutions GmbH & Co. KG
A MeVis Medical Solutions company
Universitaetsallee 29
28359 Bremen
Germany
Phone: +49 (0)421 33074-(9)20
Fax:      +49 (0)421 33074-50

E-mail: [email protected]
Website: www.mevis.de

Trade Registry: Bremen HRA 25204 HB
VAT ID: DE262661277

Executive Board:
Carl J.G. Evertsz, Ph.D., Robert Hannemann, Ph. D.
MeVis BreastCare Solutions Verwaltungs-GmbH

-----Ursprüngliche Nachricht-----
Von: Christoffer Lervåg [mailto:[email protected]]
Gesendet: Mittwoch, 26. Oktober 2011 17:15
An: Petriconi, Felix
Betreff: Re: [ruby-dicom] Large DICOM image storage objects leads to crash (#29)

That's quite a big DICOM file you've got there. Looking at the stack trace it's obvious that this is a memory issue.

I won't rule out that the ruby-dicom library might be consuming more memory than what might be possible to achieve, but Im inclined to think that you are running into a limitation of your actual computer system here.

How much memory do you have on this particular computer?

Reply to this email directly or view it on GitHub:
#29 (comment)

from ruby-dicom.

Hi Felix

It would be great if you could try this on a well equipped, native machine as well. If it succeeds on another machine, it would be nice to know how much peak memory ruby-dicom used while handling this file.

Regards,
Chris

from ruby-dicom.

Should this be closed for inactivity?

from ruby-dicom.

Yes, I think you're right. Closing this issue. Please reopen if this can be verified on a native machine.

from ruby-dicom.