Arch Linux User Repository

FAQ:

• Build failed with clang++: error: unable to execute command: Killed: You have run out of memory. 16GB is enough if nothing else is running. Otherwise Try disabling jumbo builds
• Does VAAPI work? No

The VAAPI patches for the X11 builds are not compatible because Ozone uses a significantly different codepath for video decoding generally.

I don't believe the Igalia team working on this have made desktop VAAPI a priority, although it seems they have video acceleration via v4l2 working for embedded devices: https://github.com/OSSystems/meta-browser/tree/master/recipes-browser/chromium

I've personally tried to make it work. A minor fox is required to make it build with the use_vaapi flag, but then I couldn't find a combination of minigbm, libdrm etc that made the video acceleration actually happen.

@hedgepigdaniel

Can you please explain why VAAPI does not work? Is the VAAPI-patch incompatible or is there another reason?

Any chance of adding a binary version as AUR package chromium-ozone-bin?

What I'm looking for is an ungoogled-chromium with VAAPI and Wayland support. If I only had the knowledge and time...

@osandov I just saw this: https://bugs.chromium.org/p/chromium/issues/detail?id=988396

The window title is fixed on the current master branch.

@osandov I suspect that is on the TODO list (along with the fact that the close button has no effect). Check the existing list of bugs first.

FAQ:

• Build failed with clang++: error: unable to execute command: Killed: You have run out of memory. 16GB is enough if nothing else is running. Otherwise Try disabling jumbo builds
• Does VAAPI work? No

Does anyone else have the issue that Chromium windows in GNOME are titled "Unknown"? I'm planning on opening a bug upstream but I wanted to make sure it's not just something about my setup.

Getting the following errors while building. Is there anything I can do to fix these?

clang++: error: unable to execute command: Killed
clang++: error: clang frontend command failed due to signal (use -v to see invocation)
clang version 10.0.0 (https://github.com/llvm/llvm-project/ 8455294f2ac13d587b13d728038a9bffa7185f2b)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: ../../third_party/llvm-build/Release+Asserts/bin
clang++: note: diagnostic msg: PLEASE submit a bug report to https://crbug.com and run tools/clang/scripts/process_crashreports.py (only works inside Google) which will upload a report and include the crash backtrace, preprocessed source, and associated run script.
clang++: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang++: note: diagnostic msg: ../../tools/clang/crashreports/browser_jumbo_2-0a253f.cpp
clang++: note: diagnostic msg: ../../tools/clang/crashreports/browser_jumbo_2-0a253f.sh
clang++: note: diagnostic msg: 

********************
[17799/20462] CXX obj/content/browser/browser/browser_jumbo_7.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: chromium-ozone

ah lol. should be fixed now :)

There is an unfortunate white-space error in the last commit which prohibits compiling the package. By accident the argument to ozone_auto_platforms was changed from false to fals e.

@jakebailey

I wonder if is possible to avoid it by configuring chromium to not run in the background (since it seems to be crashing while creating the app indicator, which I think it only does when configured to run in the background),

What compositor are you using? GNOME? Sway? KDE? Anything else relevant to app indicator/system tray support?

Perhaps its worth reporting a bug upsream at crbug.com. Be sure to mention that it relates to the ozone platform for wayland (that way it will get assigned o the right team). Also if you have time to build the latest master (see instructions for building chromium on linux) and confirm that the issue is still reproduceable, that would make a fix more likely.