Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in media::VaapiWrapper::VADisplayState::Initialize () #11

Open
lrusak opened this issue Jan 6, 2017 · 3 comments
Open

error in media::VaapiWrapper::VADisplayState::Initialize () #11

lrusak opened this issue Jan 6, 2017 · 3 comments

Comments

@lrusak
Copy link

lrusak commented Jan 6, 2017

I'm at a loss here, I've been trying to build chromium using your vaapi patch for a while now and I'm stuck.

I'm developing it for LibreELEC and it would be really nice to have this working.

I've built a debug build of chromium and got the backtrace using gdb but it just ends when libva tries to initialize. I'm hoping to get some pointers for where to look next. Thanks.

we use libva 1.7.3

gdb backtrace http://sprunge.us/PZUg

console output http://sprunge.us/QLRK

@piotrasd
Copy link

piotrasd commented Jan 10, 2017

My log on intel http://sprunge.us/BMNK
btw. why chromium tried GL ES on intel ? #6 0x7f0513e23afd gpu::gles2::GLES2DecoderImpl::Initialize() ??

when i try run with --no-sandbox no crash
or with --disable-gpu-sandbox. (without --disable-gpu-sandbox crash like in log)

but even if i got in console after start

libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/va/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0

and that info appear each time when i started video in chromium, my cpu load is arround 250%

@saiarcot895
Copy link
Owner

@piotrasd, Regarding the GL ES, that appears to be standard on all platforms. Also, why are you using LD_PRELOAD?

@lrusak, What's the line of code that Chromium is crashing at (based on the gdb backtrace)? We have different versions of the file.

@lrusak
Copy link
Author

lrusak commented Jan 10, 2017

We have been using LD_PRELOAD for quite some time. I can't exactly remember why now...

It looks to me like it is here, https://chromium.googlesource.com/chromium/src/+/57.0.2950.4/media/gpu/vaapi_wrapper.cc#1207
Somewhere when there is a call to libva.

I have found that I am able to get it to work when using is_component_build=true, however, I am not a big fan of this and would like to not use it.

Also I have to use --disable-gpu-sandbox. We are using Kernel 4.9.1 currently so maybe some security features changed that are restricting access.

This is how I am building chromium 57.0.2950.4, https://github.com/lrusak/LibreELEC.tv/blob/8d9454f2bfa474b548b2f94a6263f0e6b60d9eb6/packages/addons/browser/chromium/package.mk

and here is the patches I'm using, https://github.com/lrusak/LibreELEC.tv/tree/8d9454f2bfa474b548b2f94a6263f0e6b60d9eb6/packages/addons/browser/chromium/patches

Maybe something stands out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants