Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why chrome.exe doesn't close completely? #3230

Closed
akhabarovIT opened this issue Aug 18, 2023 · 3 comments
Closed

Why chrome.exe doesn't close completely? #3230

akhabarovIT opened this issue Aug 18, 2023 · 3 comments
Labels

Comments

@akhabarovIT
Copy link

Hello!
I use the code after performing the autotest:
image
and watching the processes in the task manager.

During the execution of the autotest, 7 processes are started chrome.exe, after the end of the run there are 2 of them. Why chrome.exe is it not completely killed?
image

Serenity BDD version 3.9.8 .

@wakaleo
Copy link
Member

wakaleo commented Aug 18, 2023

Do not do this. Serenity will close the browsers and drivers automatically. If you do it yourself, you can disrupt the Serenity processes.

@akhabarovIT
Copy link
Author

akhabarovIT commented Aug 18, 2023

Do not do this. Serenity will close the browsers and drivers automatically. If you do it yourself, you can disrupt the Serenity processes.

Oh, thanks!
And I found how to solve the problem. I started using serenity.conf instead of serenity.properties. All processes chrome.exe closed correctly. I don't understand how this is related and why it helped.

@wakaleo
Copy link
Member

wakaleo commented Aug 31, 2023

serenity.properties is deprecated - for W3C capabilities you need to use serenity.conf

@wakaleo wakaleo closed this as completed Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants