Openspan Automation automatically terminated
Hello,
My Automation has been automatically terminated after processing some request correctly with the below message.
The program '[17576] OpenSpan.Runtime.exe: Pega Robotics Runtime' has exited with code -1073741819 (0xc0000005) 'Access violation'.
Or
there is also one error in attached screenshot.
Pegasystems Inc.
IN
This issue seems to be a overflow issue. Can you please attach RuntimeLog.txt file after enabling verbose, which was generated at the time of issue.
You can verify below signs to understand if this is a Memory overflow issue:
1. Are there a lot of jumps in the solution?
2. Are there loops?
3. Is the crash happening inside one of these loops or jumps?
4. In the RuntimeLog.txt, do the automation blocks mostly execute on a single thread?
If answer to any above questions is yes, generally this is a bad design which generally causes overflow issues.
You can easily test this by changing one of the automation links to be asynchronous but you need to make sure not to make a link asynchronous in a bad place because it could cause automation to continue on in a wrong sequence.
It's ideal to do it either at the beginning of a frequently "jumped-to" automation or at the end. The effect should be that, in the RuntimeLog.text, you will see automations on different threads and the crash should not occur.
For example: Start of each automation change to asynchronous:
This issue seems to be a overflow issue. Can you please attach RuntimeLog.txt file after enabling verbose, which was generated at the time of issue.
You can verify below signs to understand if this is a Memory overflow issue:
1. Are there a lot of jumps in the solution?
2. Are there loops?
3. Is the crash happening inside one of these loops or jumps?
4. In the RuntimeLog.txt, do the automation blocks mostly execute on a single thread?
If answer to any above questions is yes, generally this is a bad design which generally causes overflow issues.
You can easily test this by changing one of the automation links to be asynchronous but you need to make sure not to make a link asynchronous in a bad place because it could cause automation to continue on in a wrong sequence.
It's ideal to do it either at the beginning of a frequently "jumped-to" automation or at the end. The effect should be that, in the RuntimeLog.text, you will see automations on different threads and the crash should not occur.
For example: Start of each automation change to asynchronous:
