Closed Bug 1292628 Opened 4 years ago Closed 4 years ago
Crash in ssse3
_fetch _bilinear _cover
This bug was filed from the Socorro interface and is report bp-9029f4cc-3301-4663-bd95-48bcd2160805. ============================================================= Seen while looking at beta crash stats: https://crash-stats.mozilla.com/signature/?product=Firefox&_sort=-date&signature=ssse3_fetch_bilinear_cover. Crash seems to be unique to beta. ni on jeff since it appears he may have worked in this area of code.
[Tracking Requested - why for this release]: This is a crash regression during video playback that we should be able to avoid.
204 crashes in the last week with beta 3. Nothing showing up for beta 4 yet. There's also one crash on 50 aurora.
It looks like most of these have 'Unknown cairo format -1'.
Attachment #8783094 - Flags: review?(mstange) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/1ba19d1f07da Make sure our surface is good before locking it. r=mstange
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/7249543cf71a Make sure our surface is good before locking it. r=mstange
Relanded the patch after a Try push with this patch applied but bug 1110928 backed out returned a green reftest for Windows XP: https://treeherder.mozilla.org/#/jobs?repo=try&revision=22da75fc4238&selectedJob=26089235 https://hg.mozilla.org/integration/mozilla-inbound/rev/7249543cf71acbe21ab6306ce321f1207611cf5d
Comment on attachment 8783094 [details] [diff] [review] Check the error status of a surface before returning the data inside it Approval Request Comment [Feature/regressing bug #]: 1292628 [User impact if declined]: Possible crash in ssse3 code [Describe test coverage new/current, TreeHerder]: Has been on nightly for a very short time. [Risks and why]: Very low risk, but may just push the problem further down the line.
Comment on attachment 8783094 [details] [diff] [review] Check the error status of a surface before returning the data inside it I see a lot of crash instances on Beta49 (none on Aurora or Nightly) but given the one-line change, it's worth uplifting to Aurora50 and Beta49.
You need to log in before you can comment on or make changes to this bug.