Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

12.3 Fat Client, Billing Module Memory Leak

Page 1 / 2 Next

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

16 Posts

6 Users

0 Reactions

169 Views

RSS

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

This has been going on since we upgraded to 12.3 last January. Our office tends to post a lot of billing entries in a batch. Each time you open an entry the system uses 4 MB more RAM. This happens even if you open and then close the same billing entry repeatedly. That 4 MB is never released. If you do this enough times, processing lots of billing entries, eventually the total RAM consumed by the program reaches the neighborhood of about 550MB, and then the program crashes, or freezes, really. The memory usage at that point zooms up to about 800 MB total used and sits there with the program totally frozen until you force it closed and start over again.

This RAM is never released unless you totally exit the software and start from scratch, so this memory leak will gradually increase total memory usage over the course of the day, or even two days if people leave the software open, until it finally crashes.

This behavior has been thoroughly documented, it can be reproduced at will on any computer running 12.3, and we have shown it to our VAR. So far, none of the release notes for patches or updates have addressed this issue. I would love it if our VAR installed these patches and upgrades in their test environment and told us when it has been fixed, so I can apply the necessary upgrades. They seem to prefer using our practice as a beta testing lab for these fixes, which is disappointing.

Has anyone seen this, and can you confirm that this leak has been corrected if you open a billing entry if you have installed any upgrades or patches to 12.3?

Posted : January 2, 2019 2:51 am

Luladin

(@luladin)

Posts: 25

Eminent Member

This is a known issue in CPS 12.3 and is resolved in SP2. Do you have access to the Virence Digital site?

https://digital.gehealthcare.com/s/article/The-RAM-consumption-continues-to-grow-until-an-ACCESS-VIOLATION-crashes-the-CPS-client?lang=en_US

Posted : January 2, 2019 3:00 am

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

Thank you so much. I wonder why our VAR didn't tell us that. It is a known outstanding issue for us, would have been nice to have it fixed.

Thank you again!

Posted : January 2, 2019 3:07 am

tbrown9409

(@tbrown9409)

Posts: 4

New Member

This is probably KM 44402 I would have their VAR run the Support Capture Tool and see if it looks like this ,this needs to be verified before you implement the Patch

tability.CPS

CRITICAL (Farpoint Dlls *MISSING*). This condition is known to cause increased: Freezing, Slowness and OutOfMemory crashes in CPS Billing. Please resolve ASAP, by:
A) Extract files from archive: C:\Temp\SupportCapture\Patches\CPS_12.3.2_FarPointMissingDll_Diagnostic_Patch.zip, And place the two dlls here: C:\Program Files (x86)\Centricity Practice Solution\Client\
-OR-
B) Upgrade to CPS 12.3.3 (or later, as available)
Also See: KM 44402

Here is a link to the Support Capture Tool with the Latest version of the tool

https://data.gehealthcare.com/fs/v.aspx?v=8c6c67885b67b7b670ae

KM 44402

Billing Module Memory Leak Patch 12.3.2

The missing .dll files are in a diagnostic patch for CPS 12.3.2 They are in the link below . This patch will be included in 12.3.3.

12.3.2

https://data.gehealthcare.com/fs/v.aspx?v=8c6c66895e6675aa6d68

CPS 12.3.1

https://data.gehealthcare.com/fs/v.aspx?v=8c6c67885c5ea078a397

CPS 12.3.0

https://data.gehealthcare.com/fs/v.aspx?v=8c6c67885c5fb0bea8a3

To install the diagnostic patch:

Ensure that no instance of CPS is running on the workstation/server where the DP is intended to be installed.

Download the CPS_12.3.2_FarPointMissingDll_Diagnostic_Patch file from the link listed above. If neccessary, unblock the file.

Right-click the zip file and select Properties.

Click Unblock.

Click OK to close the window.

If the files are copied across the network, verify that the copied files are not blocked on the destination machine.

Unzip the file to the desktop or another folder location.

Copy the dlls present in the Unzipped file to the centricity Client Folder, typically C:\Program Files (x86)\Centricity Practice Solution\Client.

Posted : January 2, 2019 4:34 am

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

I have very little faith our VAR will know anything about that tool, nor would I trust them to tell me much of anything at this point. I know a lot about this crash, because they kept kicking it back to me when it started, and this is the issue in question. I will definitely test it on a single machine and keep the rollback handy if it doesn't work, but based on the notes I would be shocked if this does not address our problem.

Posted : January 2, 2019 4:43 am

lic08

(@lic08)

Posts: 286

Reputable Member

We are on cps 12.3.2 and we still get that error message.

Posted : January 2, 2019 6:43 am

lkemp

(@lkemp)

Posts: 16

Eminent Member

Our office is having the same issue. I just spoke to Virence and was told that the billing module memory leak patch had been pulled because it was causing more issues than it was solving. I'm interested to see if they get another patch implemented soon for this.

Posted : January 2, 2019 7:23 am

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

Interesting. Perhaps I'll hold off then. This is always a concern, that each "fix" will cause additional, more problematic glitches that will impact performance even more. Thanks for the heads up. I will keep reading.

Posted : January 2, 2019 7:26 am

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

Is that the 12.3.0 memory leaks patch, or the 12.3.1 memory leaks patch that was pulled? Or both, perhaps? What other problems did it cause?

Posted : January 2, 2019 7:30 am

tbrown9409

(@tbrown9409)

Posts: 4

New Member

I would be curious to know who told you that at Virence that the billing module memory leak patch had been pulled , I am L2 support at Virence and the Billing memory patch has not been pulled the Q4 hotfix Patch has been pulled because it was causing issuing in Billing

Posted : January 2, 2019 7:36 am

slansing

(@slansing)

Posts: 14

Active Member

Topic starter

Also curious, considering that the patch has not been pulled, and is available for download on the linked site in the original response.

Posted : January 2, 2019 7:38 am

lkemp

(@lkemp)

Posts: 16

Eminent Member

Knew I should have gotten his name....He was a bit hard to understand and recommended I sign up for updates on Virence's site but he was adamant that this was no longer available. I'll call again and see if I get the same guy.

Posted : January 2, 2019 7:50 am

lkemp

(@lkemp)

Posts: 16

Eminent Member

Eddie is the guy who told me this-I called again today and this was the same person who told me yesterday that this was removed.

Posted : January 3, 2019 8:43 am

tbrown9409

(@tbrown9409)

Posts: 4

New Member

ok thanks, I have corrected Eddie with the correct information

Posted : January 3, 2019 9:19 am

caswelljm

(@caswelljm)

Posts: 80

Trusted Member

Has anyone ran the CPS 12.3.2.Billing OutOfMemory patch (CPS 12.3.2.3116 only) patch? (Not the one labeled Q4)

I was going to run it this weekend but I am hesitant after the Q4 patch being recalled.

-James

Posted : February 1, 2019 7:37 am

Page 1 / 2 Next

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed