1489846 - Crash in ff_vp9_decode_block

Status: RESOLVED WORKSFORME

(Core :: Audio/Video: Playback, defect, P2)

Description

[Calixte Denizet (:calixte)]

This bug was filed from the Socorro interface and is
report bp-a33ec8cc-146c-482a-bb13-4a39a0180909.
=============================================================

Top 10 frames of crashing thread:

0 libmozavcodec.so ff_vp9_decode_block media/ffvpx/libavcodec/vp9block.c:496
1 libmozavcodec.so decode_sb media/ffvpx/libavcodec/vp9.c:1068
2 libmozavcodec.so decode_sb media/ffvpx/libavcodec/vp9.c:1095
3 libmozavcodec.so decode_sb media/ffvpx/libavcodec/vp9.c:1089
4 libmozavcodec.so decode_sb media/ffvpx/libavcodec/vp9.c:1090
5 libmozavcodec.so vp9_decode_frame media/ffvpx/libavcodec/vp9.c:1309
6 libmozavcodec.so decode_receive_frame_internal media/ffvpx/libavcodec/decode.c:398
7 libmozavcodec.so avcodec_send_packet media/ffvpx/libavcodec/decode.c:674
8 libmozavcodec.so compat_decode media/ffvpx/libavcodec/decode.c:769
9 libxul.so mozilla::FFmpegVideoDecoder<46465650>::DoDecode dom/media/platforms/ffmpeg/FFmpegVideoDecoder.cpp:220

=============================================================

There is 1 crash in nightly 64 with buildid 20180908220614. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1488065.

[1] https://hg.mozilla.org/mozilla-central/rev?node=0cf7ab517b72

Comment 1

[Jean-Yves Avenard [:jya]]

doesn't seem to be a new bug by looking at the graph, that signature has existed for a while

Comment 2

[Jean-Yves Avenard [:jya]]

Ron, does this look related to the other issue we're currently investigating?

Comment 3

[Ronald S. Bultje]

No I don't think so. Line 496 is a really weird place to crash?

Comment 4

[Jason Duell]

The oldest crash signature I've found with 'ff_vp9_decode_block' is 20180323154952 (March 23).  

Calixte, do you know how to get a range of likely regressing bugs from a buildid?

Comment 5

[Calixte Denizet (:calixte)]

The older nightly I found is 20180414100503 and the pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6547c27303bc&tochange=37b8862d354e

and for 20180323154952 (which is a release):
https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=3db9e3d52b17&tochange=239e434d6d2b

Comment 6

[Jason Duell]

Nils, what do you think?  Is this actionable?

Comment 7

[Nils Ohlmeier [:drno]]

Crash continues even after the last update of ffmpeg. Crash addresses are all over the place. And the stack traces are also not the same. I don't think this is actionable for us, unless someone has a very clever idea of what could be going on here.

Comment 8

[Neha Kochar [:neha]]

Bulk change for all regression bugs with status-firefox67 as 'fix-optional' to be marked 'affected' for status-firefox68.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.

Comment 11

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit BugBot documentation.