Closed
Bug 672696
Opened 13 years ago
Closed 8 years ago
Sync crash-report data from each client to server
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: cjones, Unassigned)
References
Details
(Whiteboard: [sync-engine-addition?])
When Firefox on (small) handheld devices crashes, it's incredibly useful to be able to pull up the crash reports on a machine with a larger screen. It'd be nice if crash-report identifiers were Sync'd across client instances, so that I could open about:crashes on my desktop and then see a table that listed crashes from my phone. The crash-report identifiers are just the breakpad ids, which are just UUIDs (16 bytes). It would be a rare client that synced more than a few KB of crash-report data. What would be required to implement this? Is this something non-Sync experts could hack in? (E.g., me.)
Comment 1•13 years ago
|
||
This could be implemented easily, although we're completely revamping our internal APIs, partially so that implementing new sync data types is much easier. So I would hold off on this for a bit.
Whiteboard: [sync-engine-addition?]
Reporter | ||
Comment 2•13 years ago
|
||
How much is "a bit"? :) Is there a tracking bug we can dep here?
Comment 3•13 years ago
|
||
(In reply to comment #2) > How much is "a bit"? :) We want to wrap this up this quarter. (As in, land this on m-c.) > Is there a tracking bug we can dep here? Sorta. We have an experimental project branch where we're doing work w/o the Bugzilla overhead (eventually this work will make it back to services-central through the normal review channels, but not for now). The overall "tracking" bug is bug 600059 I'd say.
Updated•12 years ago
|
Component: Firefox Sync: UI → Firefox Sync: Backend
Comment 5•8 years ago
|
||
I don't see us prioritizing this highly in the foreseeable future.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•