System.OutOfMemoryException: Blue Prism is getting Hanged.

[Abhi-Chattar]

Hi Team,

I am seeking advice regarding a persistent System.OutOfMemoryException we are encountering in our production environment.

Scenario:

• Process: We are running a high-volume process across multiple Digital Workers scheduled 24/7.

• Issue: After a period of execution, the Blue Prism Interactive Client/Resource hangs and the error Exception of type System.OutOfMemoryException was thrown is displayed (as shown in the attached screenshot below).
  
  

  

The environment becomes unresponsive and the environment list fails to refresh. We suspect resource exhaustion over time due to the continuous nature of the run.

Has anyone encountered this in a multi-bot setup, or are there known best practices for managing memory in 24/7 operations?

Thanks in advance!

[naveed_raza]

Logging is enabled only for error ? 

[steven.boggs]

We have some best-practice guidance about this in our Knowledge Base article, "How can I avoid Out Of Memory issues?".  I'd suggest to look into implementing the suggestions to recover memory via Process-design considerations, using regular garbage collection actions, and ensuring the underlying BPE database is in good health.

Making sure your database is healthy is a good first step to determine if data volumes may be causing a performance hit -- run a Top Tables report (or use the Blue Prism AppInspector tool) to highlight any potential issues referencing our database maintenance documentation and take the appropriate actions to clear down the data. 

[Abhi-Chattar]

I am encountering an issue where the Blue Prism Interactive Client becomes unresponsive when monitoring scheduled processes in the Control Room.

The application hangs but the rest of my OS and other open applications work fine. My system has 8GB of RAM.

[steven.boggs]

If you're not using a "true 64-bit" version of Blue Prism Enterprise (i.e. from v7.2 onward), BPE runs as a 32-bit application with a memory usage limit of 4GB. As you're seeing BPE become unresponsive with other applications unaffected, it may just be hitting the upper limit of usable memory and causing this issue.

I'd re-suggest to run AppInspector which will produce a report highlighting any areas within your BPE deployment that may need attention/maintenance, action them accordingly by clearing down database volumes and adjusting logging levels/schedule timings/etc, then determine if the issue still occurs afterwards.

If you're still seeing OOM events occur after performing initial maintenance and addressing any issues highlighted by the AppInspector, you can use the template in our KB article "How to diagnose and report Out Of Memory exceptions" to help create a ticket for us in Support so we could take a deeper look and assist further.

[soniya720]

@Abhi-Chattar  Have you tried checking performance in task manager whenever application gets hang ?

I have observed with few of my processes facing issue. It's desktop application and after few dig-ins got suggestion from application that it expects higher RAM value. Increasing RAM did trick for us!

If it's happening with browser based application. Please try clearing the cache and have a look at performance in task manager, this can help to see which is causing issue with memory consumptions
 

[Jrwork]

@Abhi-Chattar  

Hello,

I've experienced this in high-volume environments. Here are some actions that resolved the issue:

1. Cleaning/purging the BP database: In continuous operations, the database grows rapidly and begins to impact client performance. Check and enable the automatic archiving policy for old sessions.

2. Scheduled Runtime restarts: The BP client wasn't designed to run indefinitely. Schedule restarts of the Digital Workers during low-volume windows (e.g., overnight). This alone significantly reduces the frequency of the problem.

3. Logs configured only for errors: Excessive logging (debug/info) in high-volume processes generates continuous writing to the database and consumes memory. Only log errors.

4. Exception handling with resource release: Each exception not handled correctly can leave objects, connections, and files open in memory. Ensure that every exception block includes explicit cleanup of these resources.