Closed Bug 1771632 Opened 3 years ago Closed 3 years ago

VAAPI: i965 crash loading multiple tabs with AVC/H.264 video

Categories

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

Product:
Core
Component:
Audio/Video: Playback
Platform:
Desktop
Linux
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1751363

People

(Reporter: kevin, Unassigned)

References

(
URL
)

Details

Using Nightly build 20220528190153 with media.ffmpeg.vaapi.enabled:true on Wayland (sway and mutter) on a ThinkPad T430 with Intel 3rd Gen Core Graphics (8086:0166) using the i965 mesa driver, opening multiple tabs with video can cause Firefox to crash. Example Crash Report: https://crash-stats.mozilla.org/report/index/bf6a7947-56ba-4a65-b174-09fd70220529

The best reproduction I've found (apologies in advance) is https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/
Launching >3 tabs is sufficient to produce a crash. 5-6 is ~50% reliable:

mozregression --pref media.ffmpeg.vaapi.enabled:true \
     --arg 'https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/' \
     --arg 'https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/' \
     --arg 'https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/' \
     --arg 'https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/' \
     --arg 'https://old.reddit.com/r/wallstreetbets/comments/l8rf4k/times_square_right_now/'

The earliest crashing build I've found is 20220520093126 (f6f71994696724abc3b194de6f152944f9a9b0cb) although I suspect earlier builds are affected, testing is tedious due to the crash being unreliable.

vainfo:

vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Ivybridge Mobile - 2.4.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Simple            :	VAEntrypointEncSlice
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileH264StereoHigh         :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc
      VAProfileJPEGBaseline           :	VAEntrypointVLD

Possibly related: Bug 1770407

Thanks for the report!
This crash occured with a build from the day before bug 1770407.
Yes, this crash should be fixed by it.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE

Thanks :Darkspirit, this does sound like bug 1751363. Not sure how I missed it. I thought the issue started (or got significantly worse) in the past week or so, but I may have been mistaken. I've been unable to observe a crash with MOZ_DISABLE_RDD_SANDBOX=1, which strongly suggests this is a duplicate of that issue.

However, I'm a bit confused. In bug 1751363 comment 67 you mention "MOZ_DISABLE_RDD_SANDBOX=1 is no longer needed for Mesa users." However, I'm experiencing crashes on build 20220529090310. Can you clarify?

Some or all of these reports must be yours then. They are tracked by bug 1771382.

Strange: bp-0d11c47a-3616-4ac4-bc4b-6f9520220529 from crash-stats does not show an Nvidia card in the Telemetry tab, but is caused by the Nvidia driver ("libnvidia-glsi.so.390.151") being blocked by the sandbox.
Do you have an Nvidia graphics card?
Do you just have their driver installed without having an Nvidia card anymore?
Are you trying to use nvidia-vaapi-driver?

Interesting, thanks! In addition to the Intel 3rd Gen Core Graphics, my T430 also has an NVIDIA NVS 5400M (for Optimus "switchable graphics") which is disabled in the BIOS. The drivers are installed for the rare occasions I need to run something on it. I'm surprised they are being loaded, since glx is currently set to mesa (using update-glx on Debian). Is that expected? I'll see if I can figure out why. Any hints for investigating would be appreciated.

Moved discussion to bug 1771382.

You need to log in before you can comment on or make changes to this bug.