gzip-compress crash report submission in CrashSubmit.jsm (mostly for B2G)

NEW
Unassigned

Status

()

Toolkit
Crash Reporting
5 years ago
4 years ago

People

(Reporter: Robert Kaiser, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
We should gzip-compress the crash report submissions on B2G to make timeouts less likely over slow connections. B2G uses the generic CrashSubmit.jsm we are also using on desktop and mobile for submission out of about:crashes, and maybe even for plugin reports (i.e. everything we can do from an already running Gecko), so I'm not marking the bug itself as B2G-spcific, even though this is the primary driving factor here.

We should just send the whole POST request with gzip compression to do this, so it will reduce the size of both the minidumps and the annotations. I hope we have code to be able to gzip an XHR, if not, we need to implement that as well.

As with the Android implementation in bug 816164, we will need to do some testing to make sure our server side understands this, but I'm told that Apache will probably just internally decompress the request and the collector will probably not even notice the difference. Still, testing is better than assuming. ;-)

See bug 781630 for more details.
I'm not sure if there's actually an easy way to gzip-compress a POST body in an XMLHttpRequest. If not we could probably add that feature.
There's no easy way no. zip compression support has been discussed some recently, but so far nothing's been added to specs or implementations.

I'd imagine there are js libraries floating around?
(Reporter)

Comment 3

5 years ago
Note that this is chrome JS, on B2G this runs with calls from shell.js - AFAIK telemetry is sending its requests gzip-compressed, are they using something else than XHR?
(Reporter)

Updated

5 years ago
Depends on: 816302
Depends on: 818682

Comment 4

4 years ago
It would be nice to get this in place for emerging markets with low bandwidth, early in 2014.
You need to log in before you can comment on or make changes to this bug.