-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[3.12.0] JavaScript Error: "b is null" #5881
Comments
For issues please provide a concise reproducible test case and describe what results you are seeing and what results you expect. See CONTRIBUTING.md |
Bump |
Yes, "Bump!" |
Yes Yes "Bump" No, I don't have time to figure it out. It would probably take me a day to provide a reproducible scenario if at all and so I'm just going to try and work around it, but felt it worth letting you know that someone out there is experiencing the same issue. |
Tell me @diemol, is it better that I say nothing at all? 😕 |
Selenium is an Open Source Project. That is every contributor here does not get paid for his/her time. Furthermore, Selenium is a Project which has contributors from a variety of Timezones, Diversities e.t.c. I mention the above because for the majority of users. The timespan between your previous 2 comments has not spanned a working day (For me it hasn't anyways). I would advise trying to meet with the maintainers halfway by producing an SSCCE - http://sscce.org/ If you cannot do this, then there is little to no incentive to do anything, let alone be able to do anything. Remember once more I reiterate, every contributor here does this for the love of Open Source, not because they are compensated to do so. |
Guys, let's not go too far away from the topic here. :) We all know that no one gets paid here and we are really thankful for the great work on Selenium - half the world cannot live without this project, us included. :) Right now I cannot take the time to create a reproduction so I decided just to open a ticket as a reference. @drennane has the same problem obviously, so this is a real issue. @barancev - please don't close the issue because there is no reproduction - creating one is probably more difficult than fixing the issue and we're not getting paid doing that either so you can understand why we can't do that right away. :) Let's leave it like that for now. I will try each new version of Selenium that comes out and will notify here if the issue is resolved with it. Or will come up with a reproduction when I have the time to sit down and do it. Until then - thanks again for the hard work! |
Thanks @boris-petrov for the measured response. I'm not sure why there was such an offended reaction to my "bump" or me, genuinely, asking the question of @diemol (who gave my comment a thumbs down) as to whether or not I should bother contributing at all? I could just have easily not bothered but instead took the time to let the community know that I'm experiencing the same thing. In short, I also appreciate the work being done by all and just popped in to provide feedback but I guess I'll be more tentative about doing so in future. |
But the maintainers do?
|
@luke-hill This is reference to my own code, not yours. Mine is a proprietary Enterprise Web Application which obviously does not sit on any public repo and for same reasons, it's very difficult for me to get something that is stand alone reproducible for you. Additional info if it helps; |
@drennane I doubt you hit the same issue. The original report is related to legacy Firefox driver (see fxdriver@googlecode.com in the log) that does not support Firefox 57 at all. |
Sorry, reported the wrong version of FF, fixed above. |
@drennane - perhaps you could also share the stacktrace if different? |
Stacktrace:
|
OS: Windows 7 I am observing the same error when calling Select.selectByVisibleText:
I observed it happens on the second selection of a dropdown value. Tested exactly the same thing with 3.11.0 and worked fine. It is definitely an issue with 3.12.0. |
this is not helpful information. |
Oh no, someone kicking this line of argumentative conversation off again. Maybe you didn't manage to get through the entire thread of comments above. |
It's a blind shot, but I hope this change fixes the issue. |
In case this does not fix the issue, or more corroboration is required, we ran into this issue for a build of one of our components today. It had not had any code changes for two to three weeks and suddenly went from pass to fail. This issue alerted us that there was a potential discrepancy in unpinned dependencies, and some examination of the logs showed this to be the case. Failing build (today):
Successful Build:
The failing build had selenium 3.12.0, geckodriver 0.21.0, and chromedriver 2.40 (we are using gecko). |
No Luck using getting below error |
Should be fixed in 3.13, please upgrade. |
Thanks @barancev This got resolved when i'm running in my local instance, but I'm getting the same issue in CI for some reason. Its using same Firefox- 45.0.2 ESR version The only difference i saw was Angular modules are recompiling again in CI for some reasons. Any ideas?
uild 02-Jul-2018 12:39:33 [INFO] [12:39:33] I/start - java -Djava.security.egd=file:///dev/./urandom -Dwebdriver.chrome.driver=/var/atlassian/bamboo-agent/xml-data/build-dir/AIRVIEW-SUI38-JOB1/settingsui/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.40 -Dwebdriver.gecko.driver=/var/atlassian/bamboo-agent/xml-data/build-dir/AIRVIEW-SUI38-JOB1/settingsui/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.21.0 -jar /var/atlassian/bamboo-agent/xml-data/build-dir/AIRVIEW-SUI38-JOB1/settingsui/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-3.13.0.jar -port 4444 |
@keerthindurthi: Sounds weird, because in version 3.13 the line 10294 looks like this:
You can see that it should not fail if |
@barancev, we believe the issue was a stale webdriver-manager process using the old selenium version. Forcibly restarting the server shows passing tests. |
OS:
Linux
Selenium Version:
3.12.0
Browser:
Firefox 47.0.1
The following error started happening in a bunch of tests since 3.12.0. Only on FF 47.0.1, on Chrome it doesn't happen. We're using Capybara 3.0.3 on JRuby.
Please tell me if you need more information!
The text was updated successfully, but these errors were encountered: