Makes sense (assuming the Libva etc. is the same), thanks for
investigating this further!
Since you are the one working on this it is more accurate to transfer
the assignment status to you. If you feel otherwise please let me know.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
