Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

getting error 'Firefox has stopped working' when close the window via selenium automatic testing script

  • 1 reply
  • 3 have this problem
  • 4 views
  • Last reply by guigs

kelvin.zou
kelvin.zou
more options

I am using selenium to do some automation testing activities, the firefox browser run fine but it always getting error 'Firefox has stopped working' in the last step when want to close the browser. i searched in google and looks like it's a common issue caused by due version update, i am using the latest one 55.0.3, when i tried to downgrade to 47.0, it was not compatible with the latest selenium. So i just want to know how to fix this error when close the window. thanks.

I am using selenium to do some automation testing activities, the firefox browser run fine but it always getting error 'Firefox has stopped working' in the last step when want to close the browser. i searched in google and looks like it's a common issue caused by due version update, i am using the latest one 55.0.3, when i tried to downgrade to 47.0, it was not compatible with the latest selenium. So i just want to know how to fix this error when close the window. thanks.

All Replies (1)

guigs
guigs
more options

HI kelvin.zou, I know that this does not directly solve the issue with the issue in selenium, but it does try to achieve a similar task.

There is a headlessmode - https://developer.mozilla.org/en-US/F.../Headless_mode were you use Node.js to run the selenium test.

Check that out and let me know what you think.