ungoogled-chromium-archlinux: Crash on startup
The newest version cannot start on a Nvidia+Intel GPU notebook. If I have libva-vdpau-driver installed, startup fails with GPU at BusId 0x1 doesn't have a supported video decoder; if I uninstall libva-vdpau-driver, it fails with [21560:21560:0807/204751.670679:ERROR:vaapi_wrapper.cc(326)] vaInitialize failed: unknown libva error.
It used to be a warning which will not crash the whole thing, but now it just crashes.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 26 (12 by maintainers)
Commits related to this issue
- Add 75.0.3770.142-1 binaries for Arch Linux — committed to rtMis/ungoogled-chromium-binaries by rtMis 5 years ago
- Remove non-essential build flags Removes flags that are not essential to the core of this project, notably flags about the build mode (debug vs release, debug symbols). These flags should be moved to... — committed to ungoogled-software/ungoogled-chromium by Eloston 5 years ago
- Update PKGBUILD versions to 76.0.3809.100-1 Addresses https://github.com/ungoogled-software/ungoogled-chromium-archlinux/issues/22#issuecomment-520151969 — committed to ungoogled-software/ungoogled-chromium-archlinux by Eloston 5 years ago
I figured it out. Changing
use_allocator="none"touse_allocator="tcmalloc"fixed the crash. Based on core dump the error comes fromGlibcGetSizeEstimateinbase/allocator/allocator_shim_default_dispatch_to_glibc.ccand it has something to do with shim headers. According totools/generate_shim_headers/generate_shim_headers.pyin an offical build they should not be used, butuse-system-libraries-in-official-build.patchchanged that behavior.I do not know C++ good enough to figure out the root cause of this. I think it may have something to do with something like glibc versions.
Thanks, @wchen342. With the added
is_official_build=falseflag, the packages were built and ran successfully