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

Selenide calls SeleniumException.getMessage() multiple times #415

Closed
asolntsev opened this Issue Oct 14, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@asolntsev
Contributor

asolntsev commented Oct 14, 2016

The problem is that SeleniumException.getMessage() can be very slow (it tries to detect IP and name of current machine).

I believe it should be fixed in Selenium, and there is even a pull request for this.
But meanwhile, we could optimize Selenide a little bit to avoid executing getMessage() multiple times.

@asolntsev asolntsev added this to the 3/11 milestone Oct 14, 2016

@asolntsev asolntsev changed the title from Selenide calls SeleniumException.getMessage() to many times to Selenide calls SeleniumException.getMessage() multiple times Oct 14, 2016

@asolntsev asolntsev closed this Oct 14, 2016

BorisOsipov added a commit to BorisOsipov/selenide that referenced this issue Nov 23, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment