search

marcelvanherk / Conquest-DICOM-Server

Conquest DICOM server, aiming for complete source code release
121 stars 48 forks source link

Out of memory RAM usage 64GB on Windows 10 #7

Closed informatorius closed 2 years ago

informatorius commented 4 years ago

When I send patient series to PACS 1.5.0a I get out of memory RAM usage 64GB on Windows 10 64bit bugreport_20200820.zip

2020_08_20_13_26_25_NXVSIM_VNC_Viewer

marcelvanherk commented 4 years ago

Hi,

is it one particular image where this happens?

Marcel

On Thu, Aug 20, 2020 at 12:31 PM informatorius notifications@github.com wrote:

When I send patient series to PACS I get out of memory RAM usage 64GB. [image: 2020_08_20_13_26_25_NXVSIM_VNC_Viewer] https://user-images.githubusercontent.com/6989214/90764867-57695680-e2e9-11ea-86d8-b7fbb7c499de.png bugreport_20200820.zip https://github.com/marcelvanherk/Conquest-DICOM-Server/files/5102602/bugreport_20200820.zip

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJKVGHJHDWCBUBEOXS3SBUCQDANCNFSM4QF6JO3A .

informatorius commented 4 years ago

Sending these DICOM data to PACS https://1drv.ms/u/s!Aogthz0-Lde_gTsGfSFVfLSaqqqh?e=sQIaHO

marcelvanherk commented 4 years ago

Copy from conquest to conquest gives no high memory consumption at all nor anything strange.

Maybe a bug in the send triggered by the particular reciever.

Can you tell me exactly what you do when the memory issue occurs?

Marcel

On Fri, Aug 21, 2020 at 10:10 AM informatorius notifications@github.com wrote:

Sending these DICOM data to PACS https://1drv.ms/u/s!Aogthz0-Lde_gTsGfSFVfLSaqqqh?e=sQIaHO

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678132743, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJNHHY74RSD7N2MWJ6TSBY2ZDANCNFSM4QF6JO3A .

marcelvanherk commented 4 years ago

Can you try to update to 1.5.0b?

just dgate64.exe

Marcel

On Fri, Aug 21, 2020 at 10:10 AM informatorius notifications@github.com wrote:

Sending these DICOM data to PACS https://1drv.ms/u/s!Aogthz0-Lde_gTsGfSFVfLSaqqqh?e=sQIaHO

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678132743, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJNHHY74RSD7N2MWJ6TSBY2ZDANCNFSM4QF6JO3A .

informatorius commented 4 years ago

Where can I find 1.5.0b?

marcelvanherk commented 4 years ago

On the forum. Marcel

On Sat, Aug 22, 2020 at 9:28 AM informatorius notifications@github.com wrote:

Where can I find 1.5.0b?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678613196, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJLBEJ2VAWC52BFC4CLSB56S3ANCNFSM4QF6JO3A .

marcelvanherk commented 4 years ago

Sorry,

1.5.0a is on the forum, 1.5.0b on github. But 1.5.0a is fine

Marcel

On Sat, Aug 22, 2020 at 9:28 AM informatorius notifications@github.com wrote:

Where can I find 1.5.0b?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678613196, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJLBEJ2VAWC52BFC4CLSB56S3ANCNFSM4QF6JO3A .

informatorius commented 4 years ago

The problem happened with 1.5.0a and 1.4.x too.

marcelvanherk commented 4 years ago

Hi,

That's not what you debug log shows I think.

Marcel

On Sat, Aug 22, 2020 at 9:56 AM informatorius notifications@github.com wrote:

The problem happened with 1.5.0a.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678615717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJPU2H4OVHESQRHMZMDSB6B4BANCNFSM4QF6JO3A .

marcelvanherk commented 4 years ago

DGATE (1.5.0-alpha-t4) is not 1.5.0a

Marcel

On Sat, Aug 22, 2020 at 9:56 AM informatorius notifications@github.com wrote:

The problem happened with 1.5.0a.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678615717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJPU2H4OVHESQRHMZMDSB6B4BANCNFSM4QF6JO3A .

informatorius commented 4 years ago

Can you post link here for 1.5.0a or 1.5.0b on Windows?

marcelvanherk commented 4 years ago

just google conquest dicom.

On Sat, 22 Aug 2020, 11:48 informatorius, notifications@github.com wrote:

Can you post link here for 1.5.0a or 1.5.0b on Windows?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-678620441, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJPJOBG4WZKGZ5UUGRLSB6H6XANCNFSM4QF6JO3A .

informatorius commented 4 years ago

Tested with latest 1.5.0a and got the same issue. bugreport_20200827.zip OutOfMemory

marcelvanherk commented 4 years ago

Sorry,

you have not updated dgate64.exe,which is the actual server. It still reports 1.5.0-alpha-t4. You can copy it from the install64 folder. Of course the server and service must be stopped before you can copy it.

I also noted nodicomcheck=1 in dicom.ini. Why is that needed?

Marcel

On Thu, Aug 27, 2020 at 8:16 AM informatorius notifications@github.com wrote:

Tested with latest 1.5.0a and got the same issue. bugreport_20200827.zip https://github.com/marcelvanherk/Conquest-DICOM-Server/files/5134669/bugreport_20200827.zip [image: OutOfMemory] https://user-images.githubusercontent.com/6989214/91409635-f6d89d00-e845-11ea-8208-b5dab0e4dabb.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-681669909, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJPZY3ZP5YFI6YGAKXTSCYB5RANCNFSM4QF6JO3A .

marcelvanherk commented 4 years ago

By the way,

the built in dicom checking is to avoid out of memory. A malformed dicom object with nodicomcheck=1 coule easily case this behavior.

Marcel

WankersonPerspicaz commented 3 years ago

Hi!

I have the same problem, but i dont use "nodicomcheck=1" on my dicom.ini I use SQL Server, and 1.5.0b on windows server 2012

just my memory goes up and crashes at 5.000.000

My Bug Report bugreport_20200820.zip

WankersonPerspicaz commented 3 years ago

Hi!

I have the same problem, but i dont use "nodicomcheck=1" on my dicom.ini I use SQL Server, and 1.5.0b on windows server 2012

just my memory goes up and crashes at 5.000.000

My Bug Report bugreport_20200820.zip

Well, i searching someting here, maybe... Maybe can be Oviyam 2.8 (new version), he have one config says "Enable windowing tool onload"

When a stay ON this feature, the memory just goes up. I disable that feature and estabilize the memory.

can be that ?

marcelvanherk commented 3 years ago

Hi,

You may have attached the wrong bug report, butis days dgate.exe is not from 1.5.0b. Can you use dgate.exe from the install32 folder on github?

Marcel

On Tue, Jun 15, 2021 at 2:25 AM WankersonPerspicaz @.***> wrote:

Hi!

I have the same problem, but i dont use "nodicomcheck=1" on my dicom.ini I use SQL Server, and 1.5.0b on windows server 2012

just my memory goes up and crashes at 5.000.000

My Bug Report bugreport_20200820.zip https://github.com/marcelvanherk/Conquest-DICOM-Server/files/6651934/bugreport_20200820.zip

Well, i searching someting here, maybe... Maybe can be Oviyam 2.8 (new version), he have one config says "Enable windowing tool onload"

When a stay ON this feature, the memory just goes up. I disable that feature and estabilize the memory.

can be that ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-861101327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJM5EVKT6Q5D7H3RDG3TS2TZHANCNFSM4QF6JO3A .

marcelvanherk commented 3 years ago

Curious what oviyam does. Is it using WADO to load images?

Marcel

On Tue, Jun 15, 2021 at 2:25 AM WankersonPerspicaz @.***> wrote:

Hi!

I have the same problem, but i dont use "nodicomcheck=1" on my dicom.ini I use SQL Server, and 1.5.0b on windows server 2012

just my memory goes up and crashes at 5.000.000

My Bug Report bugreport_20200820.zip https://github.com/marcelvanherk/Conquest-DICOM-Server/files/6651934/bugreport_20200820.zip

Well, i searching someting here, maybe... Maybe can be Oviyam 2.8 (new version), he have one config says "Enable windowing tool onload"

When a stay ON this feature, the memory just goes up. I disable that feature and estabilize the memory.

can be that ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcelvanherk/Conquest-DICOM-Server/issues/7#issuecomment-861101327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJM5EVKT6Q5D7H3RDG3TS2TZHANCNFSM4QF6JO3A .

WankersonPerspicaz commented 3 years ago

Curious what oviyam does. Is it using WADO to load images?

Hi Marcel, uses C-MOVE on Oviyam

WankersonPerspicaz commented 3 years ago

Hi, You may have attached the wrong bug report, butis days dgate.exe is not from 1.5.0b. Can you use dgate.exe from the install32 folder on github? Marcel … On Tue, Jun 15, 2021 at 2:25 AM WankersonPerspicaz @.***> wrote: Hi! I have the same problem, but i dont use "nodicomcheck=1" on my dicom.ini I use SQL Server, and 1.5.0b on windows server 2012 just my memory goes up and crashes at 5.000.000 My Bug Report bugreport_20200820.zip https://github.com/marcelvanherk/Conquest-DICOM-Server/files/6651934/bugreport_20200820.zip Well, i searching someting here, maybe... Maybe can be Oviyam 2.8 (new version), he have one config says "Enable windowing tool onload" When a stay ON this feature, the memory just goes up. I disable that feature and estabilize the memory. can be that ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVDWJM5EVKT6Q5D7H3RDG3TS2TZHANCNFSM4QF6JO3A .

Sorry, here, this bug report is the last bugreport_20210615.zip

WankersonPerspicaz commented 3 years ago

I saw now on bug report, that line "[MDPACS] C-Find (StudyRoot) located 51227 records"

Maybe he was searching ALL with no data, takes all imagens to FIND. making the memory goes up...

But he was making this without command

marcelvanherk commented 3 years ago

Indeed it is searching all studies. Can you try with 'EnableComputedFields = 0' in dicom.ini?

Marcel

marcelvanherk commented 2 years ago

Closed due to inactivity