Failed to read VR Path Registry from

Question

• Version: geckodriver-v0.20.0-win64
• Platform: Windows 10 Home Single
• Browser: Firefox: 59.0.2 (64-bit)
• Selenium: selenium-java-3.11.0
• intelliJ Idea: 2018.1 Community Edition

Hello, I am starting to use WebDriver with Java in intelliJ IDEA. I imported Selenium from Maven and added a dependency with the code provided on the Selenium web page. I downloaded geckodriver and updated the path to Windows. I started coding, but I get an output that seems like an error to me. Can someone help me understand what is happening?

import org.openqa.selenium.WebDriver; import org.openqa.selenium.firefox.FirefoxDriver; public class firstTry { public static void main (String [] args){ WebDriver driver = new FirefoxDriver(); driver.quit(); } } 

Firefox opens and closes without problems, but in the console I have an output that seems like an error to me. As below:

 1522649487586 geckodriver INFO geckodriver 0.20.0 1522649487598 geckodriver INFO Listening on 127.0.0.1:31435 1522649488194 mozrunner::runner INFO Running command: "C:\\Program Files\\Mozilla Firefox\\firefox.exe" "-marionette" "-profile" "C:\\Users\\Lolaika\\AppData\\Local\\Temp\\rust_mozprofile.0neo1vgzqEe7" Unable to read VR Path Registry from C:\Users\Lolaika\AppData\Local\openvr\openvrpaths.vrpath 1522649490188 Marionette INFO Enabled via --marionette Unable to read VR Path Registry from C:\Users\Lolaika\AppData\Local\openvr\openvrpaths.vrpath Unable to read VR Path Registry from C:\Users\Lolaika\AppData\Local\openvr\openvrpaths.vrpath Unable to read VR Path Registry from C:\Users\Lolaika\AppData\Local\openvr\openvrpaths.vrpath 1522649494926 Marionette INFO Listening on port 54726 1522649495670 Marionette WARN TLS certificate errors will be ignored for this session abr 02, 2018 1:11:35 AM org.openqa.selenium.remote.ProtocolHandshake createSession INFORMACIÓN: Detected dialect: W3C 1522649495872 addons.xpi WARN Exception running bootstrap method shutdown on [e-mail] : [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://activity-stream/lib/SnippetsFeed.jsm :: uninit :: line 125" data: no] Stack trace: uninit()@resource://activity-stream/lib/SnippetsFeed.jsm:125 < onAction()@resource://activity-stream/lib/SnippetsFeed.jsm:141 < _middleware/</<()@resource://activity-stream/lib/Store.jsm:51 < Store/this[method]()@resource://activity-stream/lib/Store.jsm:30 < uninit()@resource://activity-stream/lib/Store.jsm:153 < uninit()@resource://activity-stream/lib/ActivityStream.jsm:274 < uninit()@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Program%20Files/Mozilla%20Firefox/browser/features/ [e-mail] !/bootstrap.js:80 < shutdown()@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Program%20Files/Mozilla%20Firefox/browser/features/ [e-mail] !/bootstrap.js:196 < callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4419 < observe()@resource://gre/modules/addons/XPIProvider.jsm:2279 < GeckoDriver.prototype.quit()@driver.js:3270 < despatch()@server.js:557 < execute()@server.js:531 < onPacket/<()@server.js:506 < onPacket()@server.js:505 < _onJSONObjectReady/<()@transport.js:500 [Child 2272, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346 [Child 2272, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/cUnable to read VR Path Registry from C:\Users\Lolaika\AppData\Local\openvr\openvrpaths.vrpath Promise rejected while context is inactive: Message manager disconnected [Parent 5308, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346 [Child 5336, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346 [Child 5336, Chrome_ChildThread] WARNIN[Parent 5308, Gecko_IOThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346 [Child 8788, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346 [Child 8788, Chrome_ChildThread] WARNING: pipe error: 109*** UTM:SVC TimerManager:registerTimer called after profile-before-change notification. Ignoring timer registration for id: telemetry_modules_ping [GPU 10500, Chrome_ChildThread] WARN ###!!! [Child][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv 1522649503244 geckodriver::marionette ERROR Failed to stop browser process Process finished with exit code 0 

My workspace

What can I do to correct this conclusion? Thanks!!

Answer 1

With GeckoDriver v0.20.0 and Firefox Quantum v59.0.2 (64-bit), your code block looks good, and the log stack trace looks equally good if no log message is specified:

 Promise rejected while context is inactive: Message manager disconnected 

According to the discussion in the Mozilla Support Forum, this error looks like Privacy Badger . In short, this problem is caused by an extension that does not load / work properly.

Decision

• Update JDK to the latest JDK 8u162 levels.
• Update Selenium to current levels Version 3.11.0 .
• Clean up the project workspace through your IDE and rebuild the project only with the necessary dependencies.
• Use the CCleaner tool to erase all operations from the OS before and after the test package.
• If your base version of Firefox is too old, uninstall it using Revo Uninstaller and install the latest version of GA and the released version of Firefox.
• Reboot the system.
• Run @Test .

TL; DR

Are promises allowed before the window.unload event?

---

Update

Well, as I mentioned in my answer, your stack trace was fairly fair, as in current implementations. But personally, I did not see this trace on my local host:

 Promise rejected while context is inactive: Message manager disconnected 

Some rough tracks may depend on the underlying OS. Now let's look at the whole discussion. Are promises allowed before the window.unload event? The line seems:

The problem of promises from page unloading (or indeed a script call on unloaded pages in general) is not specified very well and cannot be implemented mutually exclusive. See also https://bugzilla.mozilla.org/show_bug.cgi?id=1058695 , where we ended up with some mitigations at Gecko that are technically out of specification, because technically following the specification is a world leak in normal cases .... Problem that there is currently no specification for this event loop event, and the specification for Promise is part of ES6, which in fact does not allow the possibility of Realms needing to go away in a way, so there’s nothing to even raise such problems.

Consequently, conclusion. You are well ahead.