Skip to main content

Sometimes, while the bot is running on the Emulator, I get this error: Bot Launcher for user session NAME OF RUNNER crashed last recorded.
The emulator is open and ready to respond but from the event log we see that javaw.exe has stopped running (on virtual ZULU). The lines and bots on which it crashes are always different.

I checked this article but cannot find any correspondence with my situation
https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded/

The version is: Automation 360 build no. 13343

Any advice on this? 

 

@CorraCastel can you increase java memory, seems not enough memory to execute commands in emulator. 

@CorraCastel Also you can check this article for Javaw.exe crash issue
https://ugetfix.com/ask/how-to-fix-the-javaw-exe-error/#:~:text=If%20the%20culprit%20of%20the,check%20CPU%20usage%20quite%20frequently.

@CorraCastel ,

Verify if you are using the lastest version of Terminal Emulator package. 

Check Event Logs from Event Viewer in Windows during the time frame of crashes and try to identifed some error related with javaw.exe

Install the utility Gflags as mentions the KB 

https://apeople.automationanywhere.com/s/article/How-to-check-the-reason-for-any-windows-process-getting-crashed-using-GFLAG

this one can be useful when another application is blocking any other.

 

HTH

Regards

@CorraCastel  have you found any solutions?

 

Thanks,

jd

@JD 973, unfortunately no. The machines meet the requirements and we cannot change the version of the package because of linked taskbots.

Do you have the same problem?

Thanks,

cc

yes, one of our bots got this issue occasionally, we guess it might be caused by the memory restriction, so we increased the maximum memory of the bot agent. We’re still monitoring the bot to see if the issue has been fixed or not.

@JD 973, If you resolve, could you let me know?
Thanks,

Reply


Terms & ConditionsCookie settings