[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
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:
Fix Released
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Ah... that explains a lot!
Please send me the revised build guide! Mine is v0.5 from june!
Thanks!
On Thu, Oct 20, 2022 at 3:00 PM Qinling Wang <1990...@bugs.launchpad.net>
wrote:
> Which build guide do you have? Is that Revision 0.7? There are 7 patches
> rather than 3.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990010
>
> Title:
> VA error: resource allocation failed
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
>
>
--
Owner/Director of Game Studio Abraham Stolk Inc.
Vancouver BC, Canada
b.st...@gmail.com
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Which build guide do you have? Is that Revision 0.7? There are 7 patches
rather than 3.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Yes, your r105 debian package works on my machine, with HW-decode under
Wayland.
Are there any patches applied, other than the 3 mentioned in the
building guide?
** Attachment added: "Screenshot from 2022-10-20 11-11-45.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5625584/+files/Screenshot%20from%202022-10-20%2011-11-45.png
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Could you please test the attached chromium browser build 105.0.5195.19?
Thank you! Hw decoding works fine with it on my setup.
** Attachment added:
"chromium-browser-unstable_105.0.5195.19-1_amd64-HW-decoder-working.deb"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5625526/+files/chromium-browser-unstable_105.0.5195.19-1_amd64-HW-decoder-working.deb
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I tried building a snap with 104.0.5112.101 version of chromium, and
that gives me working HW-decode on Wayland.
A later change in chromium must have broken vaapi playback.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
FFMpeg decoder either way for me. `intel_gpu_top` reports Cofeelake and
confirms no video decoding.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
>From build guild:
use VaapiVideoDecoder:
--enable-features=VaapiVideoDecoder,\
VaapiVideoEncoder,UseChromeOSDirectVideoDecoder
use legacy VDA:
--enable-features=VaapiVideoDecoder, VaapiVideoEncoder \
--disable-features=UseChromeOSDirectVideoDecoder
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Thank you for letting me know 104.0.5112.101-1 does work on your
Alderlake.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
The deb does indeed vaapi hw decode for me on Alderlake.
$ LIBVA_TRACE=$HOME/va.log /usr/bin/chromium-browser-unstable --enable-
logging=stderr ~/Downloads/*mp4
** Attachment added: "va trace"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620150/+files/va.log.222000.thd-0x00032256
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
@helainewang I can confirm that your .deb file indeed plays with HW
decoding on my Alderlake machine, but not via VAAPI.
If I pass:
```
--enable-logging=stderr
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder
--disable-features=UseChromeOSDirectVideoDecoder
```
Then the decoding is in sofware, with the following error from chromium:
```
[188746:188746:0929/141918.619668:ERROR:vaapi_wrapper.cc(2128)] vaCreateContext
failed, VA error: unknown libva error
[188746:188746:0929/141918.619871:ERROR:vaapi_video_decode_accelerator.cc(726)]
Failed to create Context
```
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Validated HW decoding working fine with chromium-browser-
unstable_104.0.5112.101-1_amd64.deb as the attached picture. Tested on
Wayland.
** Attachment removed: "HW decoding working with Chromium Browser"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620117/+files/HW-Decording-working.png
** Attachment added: "HW decoding working with Chromium Browser"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620118/+files/HW-Decording-working.png
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Attachment added: "HW decoding working with Chromium Browser"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620117/+files/HW-Decording-working.png
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
> ** Attachment added: "chromium-browser-unstable_104.0.5112.101-1_amd64"
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620071/+files/chromium-browser-unstable_104.0.5112.101-1_amd64.deb
>
Thanks Qinling.
Playback is software accelerated as verified in about:media-internals
(kDecoderName is FfmpegVideoDecoder).
Tested on Wayland. Execution log is attached.
--->
% vainfo
libva info: VA-API version 1.15.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.15 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3 ()
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
<---
** Attachment added: "log"
https://bugs.launchpad.net/bugs/1990010/+attachment/5620076/+files/log
--
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
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Could you please test the attached chromium-browser-
unstable_104.0.5112.101-1_amd64.deb? Thank you!
** Attachment added: "chromium-browser-unstable_104.0.5112.101-1_amd64"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5620071/+files/chromium-browser-unstable_104.0.5112.101-1_amd64.deb
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I get this both on dev, and edge-hwacc, and snaps I build myself.
It consistently gives me a VA error on wayland, but works on X11.
On Wed, Sep 28, 2022 at 2:30 PM Nathan Teodosio <1990...@bugs.launchpad.net>
wrote:
> > Which build guide did you follow to build your chromium browser? Could
> > you please provide us the version of your chromium browser and vainfo
> > output information? Thank you!
>
> Qinling, the snap against which we have been testing is built from [1].
> (Please correct me, Bram, if you tested a different build.)
>
> [1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1990010
>
> Title:
> VA error: resource allocation failed
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions
>
>
--
Owner/Director of Game Studio Abraham Stolk Inc.
Vancouver BC, Canada
b.st...@gmail.com
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
> Which build guide did you follow to build your chromium browser? Could
> you please provide us the version of your chromium browser and vainfo
> output information? Thank you!
Qinling, the snap against which we have been testing is built from [1].
(Please correct me, Bram, if you tested a different build.)
[1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
The chromium version and vainfo output are in the upstream issue:
https://github.com/intel/media-driver/issues/1498
The chromium build is via our snap, that integrates your patches.
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Which build guide did you follow to build your chromium browser? Could
you please provide us the version of your chromium browser and vainfo
output information? Thank you!
--
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
Tracking upstream in https://github.com/intel/media-driver/issues/1498
** Description changed:
+ 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
** Bug watch added: github.com/intel/media-driver/issues #1498
https://github.com/intel/media-driver/issues/1498
--
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:
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Tags added: kinetic
--
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:
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Description changed:
When I play a H264/AAC video with HW decoding enabled on Alderlake
- 12600k, I get the error:
+ 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/
+ 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
--
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:
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
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
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:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, 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.
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
** Attachment added: "trace from libva"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+attachment/5617882/+files/va.log.161716.thd-0x00021d72
--
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:
New
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, 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.
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
The hex value 0100 0008 decodes to:
#define I915_FORMAT_MOD_Y_TILED_GEN12_RC_CCS_CC fourcc_mod_code(INTEL,
8)
This is not listed as supported by
MediaLibvaCapsG12::SetExternalSurfaceTileFormat()
--
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:
New
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, 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.
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I added logging of the unsupported modifier value.
This is the value that it fails on:
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:379: Unsupported
modifier: 0x108
--
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:
New
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, 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.
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
