Package Details: chromium-dev 88.0.4302.0-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL:
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 158
Popularity: 0.014726
First Submitted: 2010-05-17 09:04
Last Updated: 2020-11-02 18:49

Dependencies (32)

Required by (0)

Sources (4)

Latest Comments

« First ‹ Previous ... 8 9 10 11 12 13 14 15 16 17 18 ... Next › Last »

bm456 commented on 2018-02-02 19:12


may be a segfault?

please read this (use lesser jobs)

recomended: 1.6gb per thread

sl1pkn07 commented on 2018-01-27 17:53

@misc that patch is knowed by upstream?

misc commented on 2018-01-27 00:20

Haven't followed the AUR changes for this package in so long, here's my patches if they're of any use. All apply to chromium git.

  1. General build fixes, the one to media/base/decoder_buffer.h is required with next ffmpeg

  2. Undoes freetype & harfbuzz being combined to one target, with this it's possible to use system libs for both again.

  3. Working VAAPI patch. Somehow GPU usage no longer shows for me in task manager, doubt that's related though.

prazola commented on 2018-01-22 13:17

Compiled, but says this at runtime: ../../third_party/tcmalloc/chromium/src/] Attempt to free invalid pointer 0x5596ee2da030

bm456 commented on 2018-01-13 19:35


can you add an alert (at nijna line) about possible oom-related troubles?

just like this warning (at my benchmarks, with an amd fx cpu i estimate it at >1.46GB per job), they say 1.25 at their warning because they're using gcc instead of google's clang trunk (clang 6)

feel free to use my alert

bm456 commented on 2018-01-09 23:22

somebody failed again lol

sl1pkn07 commented on 2017-12-30 21:54

that is because you add zero logs of the problem, only the solution

bm456 commented on 2017-12-30 21:43

yeah, but they prefer make "jokes", or just ignore it (since agust many peple reported some bugs if you disable webrtc and google ignored it)

just like "please give me your chrome://crash log"

ehen its a build issue, not a run issue

sl1pkn07 commented on 2017-12-30 21:31

What do they do?

i only support official patches (and fix for the patches iself)

bm456 commented on 2017-12-30 21:27

i report the issues, and google (sometimes) fix it

but if google doesnt fix it, i mantain the patches


its your package, with my patches (only the 4 mandatory patches, the rest of patches are my features)