Closed
Bug 846839
Opened 11 years ago
Closed 11 years ago
Crash provider failing if profile directory on UNC-formatted path: Module Path cannot handle UNC-formatted paths yet: \\foo\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending
Categories
(Firefox Health Report Graveyard :: Client: Desktop, defect, P4)
Firefox Health Report Graveyard
Client: Desktop
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 846848
People
(Reporter: gps, Unassigned)
References
Details
FHR errors in the payload have revealed a failure of the crashes provider if the profile directory is on a network share: Error: Module Path cannot handle UNC-formatted paths yet: \\foo\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending Possible OS.File limitation? Can anyone weigh in on the importance of obtaining this data? Do we have any kind of idea how many Firefox users have their profile on a network share? That seems like something that would be interesting for FHR to collect. I imagine profile on a network share would slow down Firefox!
Comment 1•11 years ago
|
||
Definitely a limitation of OS.File: http://dxr.mozilla.org/mozilla-central/toolkit/components/osfile/ospath_win_back.jsm#l256 Opening bug 846848 for UNC-formatted paths. I'll let you tell me how urgent this is for you.
Comment 2•11 years ago
|
||
ASAP, please, Yoric! P4 here just means "less important than FHR on Android".
Depends on: 846848
Priority: -- → P4
Comment 3•11 years ago
|
||
I have a prototype for bug 846848. Is there a way you could contribute a test?
Reporter | ||
Updated•11 years ago
|
Component: Metrics and Firefox Health Report → Client: Desktop
Product: Mozilla Services → Firefox Health Report
Reporter | ||
Comment 4•11 years ago
|
||
I'm going to assert this is fixed with bug 846848.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•