Why openRPA force close when using get Element (OpenRPA.Image))
-
why when using the activity in the image group, after a long time running the robot, OpenRPA always crashes when in the image activity ??
-
it would help if you could explain what you mean by "crash" and send the error message you get.
And if you want to report this as a bug, then create an small workflow that demonstrates this issue, export it, and upload it here. -
@allan-zimmermann crash I mean when the robot has been running for a long time and has entered the activity get element image, suddenly openrpa forceclose. The robot process also stops and openrpa needs to be re-opened, but when it just re-opens, it happens again. So I need to restart my pc
-
@allan-zimmermann but i was update my open rpa to 1.2.66, it not happen until right now. But i stil watching this issue if that happen again, i will update here
-
@allan-zimmermann
its happen again even though I have updated the version, the second activity make openRpa force close after rpa running for a long time, without any error message. -
so it does work some times ? or does it crash every time ?
Can you try removing "run" from processname ( leave the field blank / unfilled ).
In the event viewer on your computer, there should be 2-3 events in the Application log, if openrpa crashes with an unhandled exception. Can you check if one of those contains an error message and strack trace ? -
@allan-zimmermann said in Why openRPA force close when using get Element (OpenRPA.Image)):
so it does work some times ? or does it crash every time ?
Can you try removing "run" from processname ( leave the field blank / unfilled ).
In the event viewer on your computer, there should be 2-3 events in the Application log, if openrpa crashes with an unhandled exception. Can you check if one of those contains an error message and strack trace ?it crash every time while robot work in that activity, my solution for now is restart my pc, do you have another solution? Is there any instability in the version I'm using? which version should I use? now i'm using version 1.2.71.0
-
I'm not aware of any specefic issues regarding image recognition ( 1 bug where OpenCV will crash if an image is to small, but then you would see the issue right away, not over time )
But to be honest, not alot of poepl use image recognition to find elements so you may have hit something not alot of people see.
But what you decribe could also be a memory issue ( or memory leak ) and not specefily an issue with image recogntion.
Then workflow, how often do you call, how do you call it ? If the robot has been running for a while, does the memory consumption increase ? ( for most when NOT using workflow designer, should not see memory usage above 200-400mb ) -
@allan-zimmermann Hi Allan! I was also trying to look at something familiar you mentioned here. I have a workflow which increases memory usage to the limits as it executes in a loop scrapping a website, is there any way to free up memory (RAM)?
-
@victor-andres-pelaez-guzman Need to know what is in memory. Is it a alot of nested sequences and get elements ? are you filling data in datatables or worse, alot fo strings. Are you doing a looping action that runs for a very very long time ?
One of the first things I do, when I need to assist people is "normalize" the workflow. If a workflow is more than 3-4 pages, it's time to split it up to smaller workflows and call them using "Invoke OpenRPA" and make sure you are sending serializable data between them ( for instance, never send a datatable/datarow between workflows )
Next is looking at how data is stored. For a workflow that is scraping data: If there is a lot data it might make sense to stored it externaly, ( excel, files, database, openflow etc. ) or maybe it's time to split it up using work items and queues.
