We recently upgrade to new Dell Optiplex 5000 desktop PC (64bit, 8gb ram, I7) , and getting strange method aborting at custom dialog calls. It seems intermittent, since it runs fine initially but if have to call custom dialog (with custom image) more than 3x then it aborts method and crashes method editor.
I suspect there is a memory leak, but same exact method works perfectly on older dell computer with same memory size. I am puzzled…
I am running Venus 4 (4.5) and error happens on both while running method manager and direct from method editor.
Has anyone seen this problem before? Thanks in advance!!!
I remember reaching a Run Control memory cap running a long running Scheduler workflow. I’m pretty sure there’s a hot-fix that increases the memory allocation for any given Run Control execution.
In the meantime, do you see the same behavior…
when you remove the Custom Dialog? Not disable, remove altogether. Copy it into another method in the interim.
when you replace the images in your Custom Dialog with ones with much smaller file sizes?
Hi @WillTurman , we had that problem for long running of scheduler workflow, the memory usage can soon reach about 1G, and it caused many problems. Can you share more information or document about that fix? Thank you.
Answering Will’s question, images size are 1.57MB, and when I remove them all together problem goes away and when I replace them with smaller image and problem became intermittent.
This is when it dawn on me, HR control is a 32 bit application running on 64 bit system. It can only utilize 2GB of virtual memory(at the most). Further researching a solution to increase virtual memory, I found a patch application (NT core 4GB patch) which let 32 bit application access the additional 2GB of virtual memory and voila, it worked over and over again. This is patch page, 4GB Patch – NTCore
@Andre Ah! A clever solution to a problem I have encountered in the past. I had a similar issue putting “large” images in custom dialog boxes. The work-around I used was compressing the images to <1MB, which did solve the issue. The 4GB Patch seems like a much better fix. Thanks for sharing!