We have a few hundred instances of this error being reported by clients: Provider error: org.mozilla.crashes: Failed to collect: Win error 3 during operation open (The system cannot find the path specified. Since we have millions of records, the rate is low. And, we don't have stack traces for this error for some reason. My guess is the crash reports directory is missing or something. Can that happen?
We ought to be creating this on startup, but if someone is running a --disable-crashreporter build they wouldn't have this. Is FHR enabled on self-builds?
FHR is enabled on self-builds.
Then you should probably just have that provider check if the crashreporter service is present, and fail gracefully if it's not.
Curve ball: People are seeing this error in official channel builds. We have crash reporter enabled on all our official channel builds, right? Perhaps I should dig more into the app info of the affected clients...
FHR is going away per bug 1209088, closing.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.