Selenium webdriver issue: Permission denied to access property 'nr@context'

1,369 views
Skip to first unread message

Igor Baloš

unread,
Apr 3, 2014, 9:47:43 AM4/3/14
to seleniu...@googlegroups.com
I have been running selenium tests on a Linux Centos and it worked fine for over a year, until yesterday, when I started receiving error on my tests from Selenium:

Selenium::WebDriver::Error::UnknownError:
 
Permission denied to access property 'nr@context'
 
Build info: version: '2.39.0', revision: 'ff23eac', time: '2013-12-16 16:11:15'
 
System info: host: 'selenium', ip: 'ip_address', os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-431.3.1.el6.x86_64', java.version: '1.7.0_51'
 
Driver info: driver.version: unknown (org.openqa.selenium.remote.ErrorHandler$UnknownServerException)


I am using Firefox as the main browser for testing and I initiate the browser like this from code:

caps = Selenium::WebDriver::Remote::Capabilities.firefox(:firefox_profile => get_firefox_profile)
@driver = Selenium::WebDriver.for :remote,:url => "http://#{host}:#{port}/wd/hub", :desired_capabilities => caps , :http_client => client



host is: address of my machine for testing
port is 4444 on which Selenium Grid is.

What I noticed is that some of tests do pass and the once which do not pass visit different domains (though Cross Domain Testing should not be a problem for WebDriver?)

Anyone experienced similar thing, or have an idea what this could be?

the Selenium Grid is started up before tests run on that machine like this:

PORTS="5555 5556 6666 6667"


java
-jar SeleniumGrid/selenium-server-standalone.jar -role hub & sleep 10


for port in $PORTS

do


  java
-jar SeleniumGrid/selenium-server-standalone.jar -role node -hub http://mymachine.com:4444/grid/register -port $port -singleWindow -firefoxProfileTemplate 'BrowserProfile/selenium' &


done


From tests side nothing changed yesterday. Browser, Selenium server version, code is identical as it was before it started happening.
It starts to happen soon as I visit another domain and try to sign in for example

gau...@gmail.com

unread,
Apr 4, 2014, 2:04:41 AM4/4/14
to seleniu...@googlegroups.com
Hi, 

Did you find solution for this problem?

I've been struggling for this issue for 2 days :(

Any help would be appreciated.

Sebastian Schneck

unread,
Apr 4, 2014, 4:19:52 AM4/4/14
to seleniu...@googlegroups.com

Igor Baloš

unread,
Apr 4, 2014, 6:25:14 AM4/4/14
to seleniu...@googlegroups.com
Hey guys,

yeah, I can confirm too that it is definitely related to New Relic. I can see the issue only on web pages which have New Relic JS in the page, tried it out on two different web apps.
I will ask our dev team today to disable Browser Beta module in our New Relic account and see if that helps.

Igor

Igor Baloš

unread,
Apr 4, 2014, 9:42:34 AM4/4/14
to seleniu...@googlegroups.com
Hey guys,

developer disabled Browser Beta module in our New Relic account, now everything is back to normal, tests are passing.

igor
 

Max Aguirre

unread,
Apr 4, 2014, 12:27:28 PM4/4/14
to seleniu...@googlegroups.com
Hello,

New Relic Browser agent v378, which contains a fix for this bug, was just released this morning. You will want to restart your application server to pickup the new version. To verify that you're running it, just search the HTML source for 378.min.js

vinay karumuri

unread,
Apr 9, 2014, 2:44:20 PM4/9/14
to seleniu...@googlegroups.com
Hi All,

I am facing the issue. Please let me what is resolution for this in detail. I am not sure what is NEW RELIC BROWSER AGENT. 

Thanks,
Vinay Karumuri
Reply all
Reply to author
Forward
0 new messages