1195745 - IMAGE_DECODE_SPEED_GIF regressed on the 13th of July

Status: RESOLVED WORKSFORME

(Core :: Graphics: ImageLib, defect)

Description

[Roberto Agostino Vitillo (:rvitillo)]

Alert details: http://alerts.telemetry.mozilla.org/index.html#/detectors/1/metrics/459/alerts/?from=2015-07-13&to=2015-07-13 

Changeset for 20150713030204: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=eab21ec484bb&tochange=38d03bf4616e

Comment 1

[Seth Fowler [:seth] [:s2h]]

This looks like an expected change in behavior from bug 1117607.

We used to allocate the first frame of each image on the main thread, in a way that wasn't charged to the decoder for telemetry purposes, because this telemetry value is measuring time within Decoder::Write, and the allocation of the first frame didn't happen there.

We're now always allocating all frames, including the first, on the decoder threads, and inside Decoder::Write. So IMAGE_DECODE_SPEED_GIF now includes more work than it used to.

I think we can resolve this. (Not sure what resolution status is best; I'll go with 'WORKSFORME'.)