I have a test case sheet in which I have multiple scenarios, 9 to be exact. When I run it with command “robot testcases/example.robot” it will only be able to run the first scenario successfully before opening 8 different tabs and failing with the following error.
TimeoutException: Message: timeout: Timed out receiving message from renderer: 0.900
(Session info: chrome=133.0.6943.142)
Stacktrace:
GetHandleVerifier [0x00007FF64349C6A5+28789]
(No symbol) [0x00007FF643405B20]
(No symbol) [0x00007FF643298F9A]
(No symbol) [0x00007FF64328643C]
(No symbol) [0x00007FF64328612A]
(No symbol) [0x00007FF643283CBA]
(No symbol) [0x00007FF64328477F]
(No symbol) [0x00007FF6432932EE]
(No symbol) [0x00007FF6432A915A]
(No symbol) [0x00007FF6432B02BA]
(No symbol) [0x00007FF643284EED]
(No symbol) [0x00007FF6432A8F8A]
(No symbol) [0x00007FF64333FB5E]
(No symbol) [0x00007FF643317103]
(No symbol) [0x00007FF6432DFFC0]
(No symbol) [0x00007FF6432E1273]
GetHandleVerifier [0x00007FF6437E1AED+3458237]
GetHandleVerifier [0x00007FF6437F829C+3550316]
GetHandleVerifier [0x00007FF6437EDB9D+3507565]
GetHandleVerifier [0x00007FF643562C6A+841274]
(No symbol) [0x00007FF6434109EF]
(No symbol) [0x00007FF64340CB34]
(No symbol) [0x00007FF64340CCD6]
(No symbol) [0x00007FF6433FC119]
BaseThreadInitThunk [0x00007FFB78E57374+20]
RtlUserThreadStart [0x00007FFB78F9CC91+33]
You’re going to have to give some additional information before anyone can begin to help you.
You have a chrome error message but didn’t mention which library you’re using, is this SeleniumLibrary? Browser Library? one of the RPA libraries?
You mention a “test case sheet”, but this concept doesn’t exist in core robot framework, though it does with extension libraries like DataDriver Library, are you using DataDriver Library with an excel spreadsheet? If so, have you tried creating a few if the tests without using DataDriver Library to see if that resolves the issue?
This stack trace error does not come directly from robot framework, so there is not much for us to go on, what have you done so far to troubleshoot the issue?
Also it’s important to show the robot framework tests and keywords that are related to the error, so people know where to start from when trying to help you
Hello,
You are encountering suggests that the browser is timing out while trying to execute your test cases. This could be due to several reasons, such as resource limitations, improper browser handling, or issues with the test case setup. Here are some steps to troubleshoot and resolve the issue:
Ensure Proper Browser Cleanup
After each test case, ensure that the browser instance is properly closed. If you’re using SeleniumLibrary in Robot Framework, you can add the Close Browser keyword at the end of each test case to avoid multiple tabs or browser instances piling up.
Increase Timeout Settings
The timeout error indicates that the browser is not responding within the expected time. You can increase the timeout settings in your test cases or globally in the Robot Framework configuration:
Library SeleniumLibrary timeout=30
Adjust the timeout value as needed.
Optimize Test Case Execution
If your test cases are resource-intensive, consider running them sequentially or in smaller batches to reduce the load on your system.
Use the --test option to run specific test cases:
robot --test “Test Case Name” testcases/example.robot
4. Update ChromeDriver and Browser
Ensure that your ChromeDriver version matches the installed Chrome browser version. Mismatched versions can cause unexpected errors.
Update both Chrome and ChromeDriver to their latest versions.
Check for Resource Limitations
If your system is running out of memory or CPU resources, it can cause the browser to become unresponsive. Monitor your system’s resource usage during test execution and close unnecessary applications.
Debugging and Logs
Enable detailed logging in Robot Framework to identify the exact point of failure:
robot --loglevel DEBUG testcases/example.robot
Review the logs to pinpoint the issue.
Parallel Execution
If you need to run multiple scenarios simultaneously, consider using the Pabot library for parallel execution. However, ensure that your test cases are independent and can run in parallel without conflicts.