Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

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

  • 1 odpověď
  • 3 mají tento problém
  • 1 zobrazení
  • Poslední odpověď od 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.

Všechny odpovědi (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.