Selenium-IDE 4 on MacOS: Unable to startup due to chromedriver error: about selenium-ide

[toddtarsi]

Yes, sorry, there is an issue in beta.5 🤦, beta.4 is functional.

[vonlaughing]

Yes, sorry, there is an issue in beta.5 🤦, beta.4 is functional.

Thank you for helping me! I downloaded beta.4 but unfortunately the problem still exists :( .

[toddtarsi]

@vonlaughing - Thank you for reporting. A fix is going out for this in five or so minutes, and then a new version will be live in 30. I'm sorry, this was a goofy mistake on my part. Basically, the logging api called the logging api, which kinda repeated until it all crashed. That won't happen anymore. Thank you for your patience.

[toddtarsi]

Eh, taking a bit to clear CI, but I promise clean version coming up

[vonlaughing]

Thank you!!

[toddtarsi]

@vonlaughing - It's in review here: #1816

Basically, we're looking at adding Chinese localization alongside the fixes. Thanks again for reporting!

[vonlaughing]

@toddtarsi I installed the new 4.0.1-beta.8 version but it is still giving me the same error :(

[toddtarsi]

@vonlaughing - Sorry to take a long time to respond, took a weekend away. Can you try restarting your computer and seeing if it works? If so, I will start working on a feature so that the app recovers more gracefully. Basically, if a chromedriver server is already running, we currently crash. It can lead to bad crashes causing more bad crashes because a rogue chromedriver process is blocking a port. Restarting your computer could kill those bad processes. If that fixes it, I will work on a fix to ask about killing any servers on startup if a collision is encountered.

[vonlaughing]

@vonlaughing - Sorry to take a long time to respond, took a weekend away. Can you try restarting your computer and seeing if it works? If so, I will start working on a feature so that the app recovers more gracefully. Basically, if a chromedriver server is already running, we currently crash. It can lead to bad crashes causing more bad crashes because a rogue chromedriver process is blocking a port. Restarting your computer could kill those bad processes. If that fixes it, I will work on a fix to ask about killing any servers on startup if a collision is encountered.

Thank you!!!!! Restarting the computer did it!

However after running chrome the same error occurred, even if I kill the chrome process. Currently I can only run the app right after restarting my computer. Thank you for your help!!

[toddtarsi]

@vonlaughing - Okay, not ideal but perfect that we know the cause. I'll start working on a system to kill running chromedriver processes on startup so that won't be necessary in the future.