I opened a new thread because I believe this problem should be fixed.
Writing a script with Chromedriver functions freezes the EXE file at any Chromedriver function when the Chrome Browser Window was closed manually during execution. An On_Error condition is NOT raised.
Compiled Scripts with Chromedriver functions are freezing
Moderators: Dorian (MJT support), JRL
- Dorian (MJT support)
- Automation Wizard
- Posts: 1390
- Joined: Sun Nov 03, 2002 3:19 am
- Contact:
Re: Compiled Scripts with Chromedriver functions are freezing
Using Macro Scheduler 15.0.10 / Chrome 84.0.4147.105 / ChromeDriver 84.0.4147.30 (Win32)
I just successfully compiled the "Chrome Example" script which you can find in samples, and everything executed successfully.
I attempted to force an issue by removing my ChromeDriver file, but that simply gave me the ChromeDriver warning - not a freeze - so we know that's not the issue.
I also realized that my Chrome had updated to v84 but my ChromeDriver was still v83. ChromeExample.exe still worked perfectly using either version of ChromeDriver.
This does not sound like it's specifically a Macro scheduler issue.
I just successfully compiled the "Chrome Example" script which you can find in samples, and everything executed successfully.
I attempted to force an issue by removing my ChromeDriver file, but that simply gave me the ChromeDriver warning - not a freeze - so we know that's not the issue.
I also realized that my Chrome had updated to v84 but my ChromeDriver was still v83. ChromeExample.exe still worked perfectly using either version of ChromeDriver.
This does not sound like it's specifically a Macro scheduler issue.
Yes, we have a Custom Scripting Service. Message me or go here
Re: Compiled Scripts with Chromedriver functions are freezing
Sorry I did not declare the problem to understand correctly. I do not mean to remove the chromedriver.exe file but close the Chromedriver Browser window during execution of the script.
In fact it means I lost the session_id of the started Chrom Browser window.
In fact it means I lost the session_id of the started Chrom Browser window.