"Unable to read VR Path Registry ..." warning at startup

NEW
Unassigned

Status

()

Core
WebVR
P4
normal
4 months ago
20 days ago

People

(Reporter: Ray Engelking, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(firefox57 affected)

Details

(Reporter)

Description

4 months ago
Getting 2 new errors with the latest Firefox update 53, and on 54;
Unable to read VR Path Registry from C:\Users\rengelking\AppData\Local\openvr\openvrpaths.vrpath
JavaScript error: chrome://pin4ever/content/pin4ever.js, line 421: TypeError: Components.classes['@mozilla.org/satchel/form-history;1'] is undefined

Comment 1

4 months ago
The second error appears to be from an extension, you should contact the extnesion author directly about that.
Re-labeling and re-classifying this for the first message (which I believe is a warning and not an error, but it is noisy...)

For the WebVR folks, I see that same message even during xpcshell tests that don't do anything related to WebVR...
Component: WebExtensions: Untriaged → WebVR
Product: Toolkit → Core
Summary: Missing functionality: <add summary here> → "Unable to read VR Path Registry ..." warning at startup

Updated

4 months ago
Severity: blocker → normal
(Reporter)

Comment 2

4 months ago
(In reply to Andrew Swan [:aswan] from comment #1)
> The second error appears to be from an extension, you should contact the
> extnesion author directly about that.
> Re-labeling and re-classifying this for the first message (which I believe
> is a warning and not an error, but it is noisy...)
> 
> For the WebVR folks, I see that same message even during xpcshell tests that
> don't do anything related to WebVR...

Thank you; I guess the form-history has been deprecated for 3 to 4 years, and it was just removed. The replacement is FormHistory.jsm, although just learned that all "Legacy" extensions are being replaced with Chrome-like WebExtensions; if I wanted to write extensions like Chrome, I would just use Chrome, and not Firefox.. not sure about the rational behind eliminating all XUL type extensions, but there will be even less reason to use Firefox, when version 57 goes live on November 14th.
The real issue seems to be that WebVR is probing for the OpenVR runtime before hitting WebVR content.

Can we narrow this down to a particular test that is triggering the message from WebVR, or does it happen on all of the xpcshell tests?
Flags: needinfo?(aswan)

Comment 4

a month ago
(In reply to :kip (Kearwood Gilbert) from comment #3)
> Can we narrow this down to a particular test that is triggering the message
> from WebVR, or does it happen on all of the xpcshell tests?

Dunno, I don't see it in recent test output, but I remember it being quite frequent.  Perhaps its been fixed in the ~3 months since comment 1?
Flags: needinfo?(aswan)
status-firefox57: --- → affected
Priority: -- → P4

Updated

20 days ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 5

20 days ago
Started nightly firefox using "firefox --console" and got:
"Unable to read VR Path Registry from C:\Users\Henrik Gemal\AppData\Local\openvr\openvrpaths.vrpath"
You need to log in before you can comment on or make changes to this bug.