Pega Robotics Memory allocation exception
Hi Team,
I am getting the below error message intermittently, when I run the bot in development environment,
"Pega.Common.Memory.SharedMemoryAllocationException: Error in the application"
Pega Robotics Version : 19.1.120
PBE : 3.8
Target Apps : 2 web application.
Summary :
Previously the bot was working fine when the 2 target web apps were loading in IE mode in Edge browser. Currently one of the target apps is moving away from legacy IE mode and loading up in Edge browser without IE mode.
We have re-interrogated the controls for that web browser and updated the automation files to reflected the new controls. Now to some extent the bot works fine, at times we get the memory exception and the application freezes.
Any pointers will be helpful.
Thanks and Regards,
Varun
***Edited by Moderator Marije to add Capability tags*** INC-B5995
Pegasystems Inc.
US
@VarunK03I have a few questions. I think this is probably best looked at by support as it involves examining your solution and the logs. If you do decide to open a support request, please add the incident number here. With that being said, here are some questions I will start with.
Is this message appearing to the user or just in the logs? Are there any more messages in the logs appearing after this one? What is the last automation step before this occurs (where you are doing anything to the application)? Does this occur after one transaction, or after a series of them?
Updated: 13 Feb 2024 22:36 EST
National Australia Bank Ltd
AU
@ThomasSasnett Thanks for responding,
Currently we are in the build phase of re-interrogating and updating the automation files with the new controls when the target app is moving away from IE mode in Edge browser, FYI, target app is a .net based web application.
1. The message appears while debugging the solution,
2. Below messages that we see in studio logs at multiple places :
Error | 02:50:49.316 PM | 355 | MTA | | | | Exception when running resize thread. Error | 02:50:49.316 PM | 355 | MTA | Exception | | | Invoke or BeginInvoke cannot be called on a control until the window handle has been created., Verbose Message: General Information
@ThomasSasnett Thanks for responding,
Currently we are in the build phase of re-interrogating and updating the automation files with the new controls when the target app is moving away from IE mode in Edge browser, FYI, target app is a .net based web application.
1. The message appears while debugging the solution,
2. Below messages that we see in studio logs at multiple places :
Error | 02:50:49.316 PM | 355 | MTA | | | | Exception when running resize thread. Error | 02:50:49.316 PM | 355 | MTA | Exception | | | Invoke or BeginInvoke cannot be called on a control until the window handle has been created., Verbose Message: General Information
1) Exception Information ********************************************* Exception Type: System.InvalidOperationException Message: "Invoke or BeginInvoke cannot be called on a control until the window handle has been created." Data: IDictionary (System.Collections.ListDictionaryInternal) with 0 items TargetSite: System.Object MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean) HelpLink: NULL Source: "System.Windows.Forms" HResult: -2146233079
3. The last automation steps varies before the error gets displayed : like it might occur when selecting a down down value or listloop, while reading text from extracted proxy value, perform click method. The Memory error does not occur at the same step every time. Next time when I run the debug it runs few more steps and then we get the error.
4. It occurs after series of steps in the automation.Once the memory error comes up the application gets hanged(Freeze), and we need to shutdown the visual studio and relaunch again to continue our work.
Pegasystems Inc.
US
@VarunK03 I think the best way to resolve this is to open a support request. Please note the Incident number here for reference. A full runtime log and an examination of your automation would help. I have seen exceptions like the ones you've mentioned that appear in the logs but do not affect the automation. These may be thrown by the application and simply caught and logged by Runtime.
One thing I do like to check with memory exceptions is to ensure you are properly releasing threads. The most common way I have seen this done improperly is to not use the loop components and instead use Jump Labels to perform looping logic. Could that be the case here?
National Australia Bank Ltd
AU
SR has been opened - INC-B5995
The same automation flows are working as expected with the target app in IE mode within Edge browser.[Currently in production already]
For Future state of the bot, we are upgrading the bot to work with target App without IE mode, we re-interrogated the controls and replaced the controls in the automation files, the logic remains the same. We have used listloop , but some times the error occurs before reaching the listloop, like setting the text box value or perform clicks.