Windows 11, 10
How to install, update and remove Chromium, on Windows?
About updates: your settings, bookmarks, extensions, history, passwords, cookies... will be saved. Do not worry!
For automated updates, choose one of the Chromium #updaters
Installer
- Download the EXE executable file (This is a 7-zip self-extracting archive. So you can unzip it to see its content)
- Close Chromium browser if opened
- Execute this EXE file
- Wait for 2 or 3 seconds (Installation is silent)
- Open Chromium browser. It is updated!
- To remove it definitively: use the standard way (or a software like Bulk Crap Uninstaller, Geek Uninstaller, Revo Uninstaller, Ccleaner...)
Archive
- Download the ZIP archive file
- Close Chromium browser if opened
- Unzip this ZIP file
- Delete all the files from your installation directory
- Move the files from the unzipped directory to your installation directory
- Open Chromium browser. It is updated!
- To remove it definitively: delete your installation directory
Portable
Note: Chromium has #secure-preferences feature based on the machine SID. So extensions, certificates and passwords are not portable. The best way to migrate your data is to synchronize them.
- Download and unzip "chrlauncher-xxxxxxx.zip"
- Execute chrlauncher.exe (chrlauncher is a free and open-source Chromium launcher/updater)
- Close Chromium browser if a notification displays a new version
- Click on the "Download" button
- Wait for download and automatic installation
- Open Chromium browser. It is updated!
- To remove it definitively: delete the chrlauncher folder
Package
- Install Chocolatey (A free and open-source package manager) in command-line
- Chromium will be automatically updated via Chocolatey (using our API)
- To remove it definitively: use the "uninstall" command-line via Chocolatey
Windows 8.1, 8, 7, XP, Vista... and old versions
Since version 110, Chromium is not available on Windows 7, 8, 8.1, Server 2012 and Server 2012 R2 (Archive: 1)
For help, version 109 works fine. The last stable version for them is 109.0.5414.120
- installer, archive (win64 • stable)
- installer, archive (win32 • stable)
- installer, archive (win64 • stable • ungoogled)
- Thorium releases for Windows 7/8: installer, archive (win32/win64 • stable)
Since version 89, Chromium needs a CPU with SSE3 support (Archive: PDF)
For help, version 88 works fine on older CPU processors. The last stable version is 88.0.4324.190
- installer, archive (win32 • stable)
- installer, archive (win32/win64 • stable • ungoogled)
Since version 50, Chromium is not available on XP and Vista (Archive: 1)
For help, version 49 works fine. The last stable version for Windows XP and Vista is 49.0.2623.112
- installer, archive (win32 • stable • archived source)
- portable (win32 • stable)
- Other old versions: portable (win32 • dev)
Since version 35, Chromium needs a CPU with SSE2 support (Archive: 1)
For help, version 34 works fine on older CPU processors.
- portable (win32 • dev)
- builds before 253860 (win32 • dev)
Chromium for 64-bit Windows
Reference: Google Chrome 135.0.7049.114/115 • Tuesday, 22 Apr 2025Portable • Archive • Installer • Package →
Info:
135.0.7049.115 (1427262) • Thursday, 24 Apr 2025
Info:
- sha1: 801ae57c0253182b9bd138041628923a010fcf12
.(virus?) - chrome.sync.7z - sha1: 031d61ad3881b8ec4ab33695e823fae4dd3770a0
.(virus?) - mini_installer.sync.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Package: The free and open-source Chocolatey tool is used to install, update and launch Chromium.
- List of changes
- Previous versions (win64)
- Source: Github repository
Portable • Archive • Installer
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser".
Info:
136.0.7103.56 (1440670) • Friday, 25 Apr 2025
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser".
Info:
- sha1: 323933a33591cfb5af7b858387a844e65701014b
.(virus?) - ungoogled-chromium-136.0.7103.56-1_Win64.7z - sha1: eacb6d0b378f89c3d7756b47ae13cbe0f92c8277
.(virus?) - 136.0.7103.56_ungoogled_mini_installer.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Previous versions (win64)
- Source: Github repository
Archive • Installer
Info:
137.0.7129.0 (1447845) • Wednesday, 16 Apr 2025
Info:
- sha1: 17b3cfac1716ee67b20e35cc757b7ddbb185137f
.(virus?) - chrome.zip - sha1: bb47e4b511d959aab0791790ba9dd65cccafba9f
.(virus?) - mini_installer.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Previous versions (win64-avx512)
- Source: Github repository
Portable • Archive • Installer
Info:
137.0.7129.0 (1447845) • Wednesday, 16 Apr 2025
Info:
- sha1: 177c5c88796dc9359302fff275afc8a1c42d7288
.(virus?) - chrome.zip - sha1: 137c6e45461dd9b36bb98d9c322c877392fcebcc
.(virus?) - mini_installer.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Previous versions (win64-avx2)
- Source: Github repository
Portable • Archive • Installer
Info:
137.0.7129.0 (1447845) • Wednesday, 16 Apr 2025
Info:
- sha1: 3b2a10b51080d8d74024f70c201bd75b6b974f5c
.(virus?) - chrome.zip - sha1: 91a5f13c85f18432c695e173f160291feda1023d
.(virus?) - mini_installer.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Previous versions (win64-avx)
- Source: Github repository
Portable • Archive • Installer • Package →
Info
137.0.7149.0 (1452332) • Sunday, 27 Apr 2025
Info
- md5: cc690fa64a2788af56b60d6cb3051640
.(virus?) - chrome-win.zip - md5: 00a7b0774bb0d1b191f4eb90e80eb6a4
.(virus?) - mini_installer.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Package: The free and open-source Chocolatey tool is used to install, update and launch Chromium.
- Install an #older-version
- List of changes
- Source: Google repository
Chromium for 64-bit Windows on Arm
Reference: Google Chrome 135.0.7049.114/115 • Tuesday, 22 Apr 2025 In collaboration with the Open Source Software group at Arm, we share Chromium for Windows on Arm. (Official announce)
Chromium for 32-bit Windows
Reference: Google Chrome 135.0.7049.114/115 • Tuesday, 22 Apr 2025Portable • Archive • Installer • Package →
Info:
109.0.5414.120 (1070088) • Wednesday, 25 Jan 2023
Info:
- sha1: 0914ccdc66e8ebd58cbad511584bd23a8aea02e8
.(virus?) - chrome.sync.7z - sha1: 2982a6dc966da2ddd3db47464b5f14d091177b7f
.(virus?) - mini_installer.sync.exe - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Package: The free and open-source Chocolatey tool is used to install, update and launch Chromium.
- List of changes
- Previous versions (win32)
- Source: Github repository
Portable • Archive
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser".
Info:
109.0.5414.120 (1070088) • Sunday, 26 Feb 2023
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser".
Info:
- sha1: 7674d5f744db66f457800caab16b489b1de84ce0
.(virus?) - ungoogled-chromium-109.0.5414.130-1_Win32.7z - Portable: The free and open-source chrlauncher tool is used to install, update and launch Chromium.
- Previous versions (win32)
- Source: Github repository
Portable • Archive • Installer • Package →
Info
137.0.7149.0 (1452332) • Sunday, 27 Apr 2025
Info
- md5: d4e5ba345ab6836d38aa09963689bc71
.(virus?) - chrome-win.zip - md5: dedb0168f8f1f61795f076fbed169283
.(virus?) - mini_installer.exe - The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
- The Package version uses the free and open-source Chocolatey to install, update and launch Chromium.
- Install an #older-version
- List of changes
- Source: Google repository
macOS 11+
How to install, update and remove Chromium, on macOS?
About updates: your settings, bookmarks, extensions, history, passwords, cookies... will be saved. Do not worry!
For automated updates, choose one of the Chromium #updaters
Installer
- Download the DMG file
- Close Chromium browser if opened
- Execute this DMG file
- Drag its icon on Applications folder
- You may then "Eject" and throw away this disk image
- To remove it definitively: drag the app from the Applications folder to the Trash.
Archive
- Download the ZIP archive file
- Close Chromium browser if opened
- Unzip this ZIP file
- Double click on the unzipped folder to open it
- Drag its icon on Applications folder
- To remove it definitively: drag the app from the Applications folder to the Trash
Chromium for 64-bit macOS
Reference: Google Chrome 135.0.7049.114/115 • Tuesday, 22 Apr 2025Archive
Info:
134.0.6998.116 (1415337) • Tuesday, 18 Mar 2025
Info:
- sha1: 0e54f979dce9535aaa9ed15c1df08e2ba1fb560a
.(virus?) - Chromium.app.ungoogled-134.0.6998.116.tar.xz - Use #updaters-on-mac
- List of changes
- Previous versions (ungoogled)
- Source: Github repository
Archive
Info
137.0.7148.0 (1452326) • Sunday, 27 Apr 2025
Info
- md5: 23fb8e7d060b531449a7725cfb9eb0a8
.(virus?) - chrome-mac.zip - Install an #older-version
- List of changes
- Source: Google repository
Chromium for 64-bit macOS on Arm
Reference: Google Chrome 135.0.7049.114/115 • Tuesday, 22 Apr 2025Archive
Info
137.0.7148.0 (1452331) • Sunday, 27 Apr 2025
Info
- md5: 3994dd00de98bdf97bb0ef5ba4d1a746
.(virus?) - chrome-mac.zip - Install an #older-version
- List of changes
- Source: Google repository
Chromium for 32-bit macOS
Since version 39, Chromium and Google Chrome are not available in 32-bit version for macOS.
Linux
How to install, update and remove Chromium, on Linux distributions?
In most cases, Chromium is directly available in the official repository of each Linux distribution. So it is easy to install, update and remove it via the integrated software/package manager or in command-lines.
There are other ways like:
- chromium snap-package (Snap)
- chromium flatpak-package (Flatpak)
- For more, check a list of software package management systems.
Chromium for 64-bit Linux
Reference: Google Chrome 135.0.7049.114 • Tuesday, 22 Apr 2025Archive
Tested under Ubuntu 18+
Info:
134.0.6998.116 (1415337) • Tuesday, 18 Mar 2025
Tested under Ubuntu 18+
Info:
- sha1: 54806421f020e2d8253128fef327fd2a14460f39
.(virus?) - ungoogled-chromium_134.0.6998.116_1.vaapi_linux.tar.xz - Previous versions (ungoogled)
- Source: Github repository
Binaries →
If you prefer, you can install the Flatpak package of Ungoogled Chromium.
Info:
Available in different repositories
If you prefer, you can install the Flatpak package of Ungoogled Chromium.
Info:
- Website: ungoogled-chromium
- FAQ: ungoogled-chromium-wiki/faq
- Extensions: chromium-web-store
Package
Info:
137.0.7129.0 (1447845) • Wednesday, 16 Apr 2025
Info:
- sha1: ed4de40e9292030650ef79cfe7d273c5f4879f37
.(virus?) - chromium-browser-unstable_137.0.7129.0-1_amd64.deb - Previous versions (linux64-deb-avx2)
- Source: Github repository
Package
Info:
137.0.7129.0 (1447845) • Wednesday, 16 Apr 2025
Info:
- sha1: ff82eec5327ec739a580afd54d218c53970ca7d2
.(virus?) - chromium-browser-unstable_137.0.7129.0-1_amd64.deb - Previous versions (linux64-deb-avx)
- Source: Github repository
Chromium for 64-bit and 32-bit Linux
Reference: Google Chrome 135.0.7049.114 • Tuesday, 22 Apr 2025Arch Linux
Available in the official repository
sudo pacman -S chromium
If you prefer, you can install the Snap package or Flatpak package of Chromium.
Info:
- Chromium at Arch Linux wiki
- Arch Linux is an independent distribution
CentOS
Available in the official repository
To install the stable Chromium version on CentOS 7+:
$ sudo yum -y update
$ sudo yum install -y epel-release
$ sudo yum install -y chromium
$ - requires given Linux commands to be executed as a regular non-privileged userTo run it:
$ chromium
If you prefer, you can install the Snap package or Flatpak package of Chromium.
Info:
- CentOS is a distribution affiliated with Red Hat (RHEL).
Debian
Available in the official repository
To install the stable Chromium version:
- use the integrated software/package manager
- or use the Snap package (apt://snapd)
- or use the Flatpak package
- or use the gdebi APT tool (apt://gdebi • Deb files)
- or type these commands:
sudo apt update
sudo apt install chromium chromium-l10n
(chromium-l10n is only used for localization and is optional)Info:
- Chromium at Debian wiki and Debian packages
- Debian is an independent distribution
elementary OS
Unavailable in the official repository but you can install it!
Install the Snap package or Flatpak package of Chromium.
Info:
- elementary OS is a distribution based on #ubuntu
Fedora
Available in the official repository (since Chromium v52)
To install the stable Chromium version:
- use the integrated software/package manager
- or alternatively, type these DNF command:
sudo dnf install chromium
If you prefer, you can install the Snap package or Flatpak package of Chromium.
Info:
- Chromium at Fedora package, Fedora rpms, Fedora wiki and Fedora cloud
- Fedora is an independent distribution
Gentoo Linux
Available in the official repository
If you prefer, you can install the Flatpak package of Chromium.
Info:
- Chromium at Gentoo Linux packages
- Gentoo Linux is an independent distribution
Linux Mint
Available in the official repository
To install the stable Chromium version:
- Use the integrated software/package manager
- or type this command (on Linux Mint 20+):
sudo apt install chromium
- or follow this tutorial to install the Snap ("Ubuntu") version of Chromium
- or install the Flatpak package of Chromium.
Info:
- Chromium at Linux Mint Community and Linux Mint's blog
- Linux Mint is a distribution based on #ubuntu and #debian
Mageia
Available in the official repository
Info:
- Chromium at Mageia Application Database
- Mageia is an independent distribution
Manjaro
Available in the official #arch-linux repository
sudo pacman -S chromium
If you prefer, you can install the Snap package or Flatpak package of Chromium.
Info:
- Chromium at Arch Linux wiki
- Manjaro is a distribution based on #arch-linux
openSUSE
Available in the official repository
If you prefer, you can also install the Snap package or Flatpak package of Chromium.
Info:
- Chromium at openSUSE package, openSUSE wiki and RPM resource chromium
- openSUSE is an independent distribution
Puppy Linux
Available in the official repository
Follow the posts at Announcements about LxPup, ScPup, UPups, Chromium, LXQt, Kernels etc.
1) Install it via Menu → Internet → Get Web Browser
2) or download it from the Sourceforge repository
Info:
- Old discussion on the Puppy Linux forum
- Chromium at PuppyLinux wiki
- Puppy Linux is an independent distribution
Solus
Unavailable in the official repository but you can install it!
Install Snappy on Solus (if not installed). Then type this command:
sudo snap install chromium
If you prefer, you can install the Flatpak package of Chromium.
Info:
Ubuntu
Unavailable in the official repository (since Ubuntu 19.10+) but you can install it!
To install the stable Chromium version, there are different ways.
The Snap version
- For Ubuntu 19.10+, use the snap package (Deb to snap transition article).
snap install chromium
snap run chromium
chromium::snap-package- or type these commands about the Olivier Tilloy's PPA:
sudo add-apt-repository ppa:canonical-chromium-builds/stage
sudo apt-get update
sudo apt-get install chromium-browser
The "Debian package" version
Type these commands about the Rob Savoury's PPA:
sudo add-apt-repository ppa:savoury1/ffmpeg4
sudo add-apt-repository ppa:savoury1/chromium
sudo apt-get update
sudo apt-get install chromium-browser
To add language packages:
sudo apt-get install chromium-browser-l10n
To add only the patent-free (ogg, vorbis, theora and av1) codecs:
sudo apt-get install chromium-codecs-ffmpeg
To add the patent-free codecs + mp3, aac, ac3, mpeg4 (audio/h264), mov:
sudo apt-get install chromium-codecs-ffmpeg-extra
If you prefer, you can install the Flatpak package of Chromium.
Info:
- Chromium at Ubuntu packages and Launchpad
- Ubuntu is a distribution based on #debian
Chromium OS
Info
Chromium OS is the open-source OS designed by Google that primarily runs web applications. Based on Gentoo, it exists since 2009. Chromium is its default web browser. Google Chrome OS (closed-source) is based on Chromium OS.
Free and open-source releases:
- ArnoldTheBats' builds (Builds compiled by Tony Ditchfield)
- Alex313031's builds (Builds compiled by Alexander David Frick)
- Linux Chromium OS Full (Builds compiled by the official buildbot • Snapshots repository)
BSD
Chromium for 64-bit and 32-bit BSD
Reference: Google Chrome 135.0.7049.114 • Tuesday, 22 Apr 2025FreeBSD
Available in the official repository
Info:
- Chromium at FreeBSD wiki, FreshPorts and FreeBSD source code
- FreeBSD is an independent distribution
OpenBSD
Available in the official repository
Info:
- Chromium at OpenBSD ports and OpenBSD source code
- OpenBSD is an independent distribution
Android 8.0+
Chromium for 64-bit and 32-bit Android
Reference: Google Chrome 135.0.7049.111 • Tuesday, 22 Apr 2025Package
All Bromite patches applied.
Info:
133.0.6943.151 (1402768) • Monday, 3 Mar 2025
All Bromite patches applied.
Info:
- sha1: 5e40effdea54b6924fb0dfcd10e8ffcae144fbfb
.(virus?) - arm64_ChromePublic_HEVC-133.0.6943.151.apk - List of changes
- Previous versions
- Source: Github repository
Archive
This ZIP archive contains these packages:
Info:
137.0.7149.0 (1452332) • Sunday, 27 Apr 2025
This ZIP archive contains these packages:
- ChromePublic.apk (= Chromium code + open-source Google Chrome code • Archive: 1)
- ContentShell.apk (Dev info)
- SystemWebViewShell.apk (Dev info)
Info:
- md5: 39138735dca0c94912ba24351d95aa65
.(virus?) - chrome-android.zip - Source: Google repository
iOS
Reference: Google Chrome 136.0.7103.42 • Wednesday, 23 Apr 2025Chromium on iOS is a big fake!
Check the official blog post and build instructions to understand that Chromium cannot use the existing content/implementation, which is based on V8/Blink. It is just a skin on top of Safari. Go your way!
Notes
Obviously, you know this site is not the Chromium official website. As a regular user (not an expert), I created it in 2013 because there was no easy way to download good and stable releases of Chromium, on Windows. I try to keep it as safe and fast as possible! ;) This is absolutely a non-profit site. Please, read the privacy policy.In short:
- Since the beginning of the Chromium project until today, there is no binary of stable Chromium shared by the official team.
- The official website is development oriented. Users are invited to download Google Chrome.
- The official download page gives to users only ZIP archives of development builds (also known as "snapshot", "nightly", "vanilla" or "raw" builds) which can be very unstable. Users are invited to download Google's Chrome Canary.
- This site gives to users a choice of builds: development (also on its simplest download page), stable and portable builds.
All downloads are only from reliable sources:
- Google Storage → development builds from the official repository (Chromium buildbot)
- GitHub, AWS and SourceForge → other free and open-source builds
1. Project
Chromium exists since 2008. It is the free and open-source project (#features) behind the famous Google Chrome browser. There are many advantages for an enterprise to work on an open-source project. Intrinsically, Chromium is a Google project maintained by many authors (developers, engineers, graphic designers, security researchers...) from Google, Adobe, Amazon, ARM, Brave, Cloudflare, Facebook, Hewlett-Packard, IBM, Igalia, Intel, Logitech, Microsoft, Mozilla, Nvidia, Opera, Samsung, Vivaldi, Xiaomi, Yandex... and external contributors (Official graph).Chromium is not only a web browser. It is a blend of different important open-source projects:
- ANGLE (Graphics engine abstraction layer)
- Blink (Rendering/layout engine)
- Native Client (Sandbox for running native code)
- PDFium (PDF generation and rendering library)
- Sandbox (Security mechanism for separating running programs)
- Skia (Graphics library)
- V8 (JavaScript engine)
- and others...
One or more projects are used in Chromium browser (obviously!) and other software/service like Google Chrome, Googlebot Evergreen, Bingbot Evergreen, Mozilla Firefox (ANGLE, Skia), Opera, Vivaldi, Microsoft Edge (Search "chromium" at Microsoft Third Party Disclosures. Official PDF presentation), Adobe Acrobat, Android WebView, Discord, Bitwarden, Microsoft Visual Studio Code, Minecraft, Signal, Skype, Slack, Spotify, Steam, TeamViewer, Trend Micro, Twitch, Unity3D, Unreal Engine, WhatsApp, Electron, CEF, QtWebEngine...
Chromium is not fully designed by Google! However, as a primary investor, Google gives a consistent guidance and provides all free tools and services related to this project.
2. Stable Chromium version
Officially, Chromium does not have a stable release. The official developers (aka The Chromium Authors) do not release it to end users. So it is continually in development. Google Chrome is the stable release... but is not open-source.Chromium is the project then Google Chrome is the product.
In fact, Chromium has a stable version! ^^
Chromium being open-source (#source-code), anybody can compile it. It is reproductible. You should be a developer to do this. Just get the current stable version (135.0.7049.114) from the official Git repository and compile it!
For example, the current stable version on #linux is 135.0.7049.114. In this version, there are 114 patches which correct many issues (bugs, feature requests, enhancements...).
All stable versions of Chromium on #windows, #mac, #linux... are always made by third-party developers.
The stable version of Chromium is compiled by:
- Google developers (USA) → Google Chrome
- Microsoft developers (USA) → Microsoft Edge
- Opera developers (Norway/China) → Opera
- Samsung developers (South Korea) → Samsung Internet
- Vivaldi developers (Iceland) → Vivaldi
- Yandex developers (Russia) → Yandex browser
- Hibbiki and Marmaduke developers → Chromium, on #windows and #mac
- Some developers → Chromium, on each #linux and #bsd distribution
- Some developers → Chromium-based browsers
- Some developers → other projects like CEF, Electron, Qt WebEngine, Chromely, NW.js, Beaker, JxBrowser ...
3. Development
The development builds (also known as "snapshot", "nightly", "vanilla" or "raw" builds) are built automatically several times a day by the Chromium Buildbot (buildbot console) and made available as binary code releases.Snapshot
Once a snapshot has been built, it is placed in the chromium-browser-snapshots root directory of Google Cloud Storage and is automatically tested. This build is really just development tool for checking whether issues are fixed in the latest Chromium code. It can be buggy and unstable. They are downloadable on the official site, my alternative webpage and this site (Check The Chromium Authors tag).LKGR
If that snapshot build successfully passes the automated tests, it is considered as a good build (known as LKGR meaning "Last Known Good Revision") and can become potentially a stable build. For info, LKGR builds were stored in the chromium-browser-continuous root directory until Friday, 18 Mar 2016. The Chromium team has removed few LKGR builders (407399, 576253 and chromium-dev) but other ones still work (latest commit). Finally, there is no LKGR binary shared by the Chromium team... but any developer can re-compile it! ^^Stable
A stable build is a development build tested by the Buildbot then improved by the Chromium team and all contributors.4. Conclusion
Note this website and the Chromium builds are made and shared by volunteers (devoted developers), freely, in their spare time. There is absolutely no business, no revenue (Privacy policy). We are neither Google nor a corporation. So please, respect our work. Officially, the #stable-chromium-version does not exist at all. We need time to re-compile Chromium. If you cannot wait for the latest version, prefer to use a development version (download page) or compile Chromium yourself (#source-code) or use other #browsers.Jerry (admin)
Features
Chromium vs Google Chrome.Chromium browser has:
- only an open #source-code
- different licences:
- mainly open-source licenses (BSD license, MIT license, LGPL, MS-PL and MPL+GPL+LGPL tri-licensed)
- 1 proprietary licence (but for available source code: UnRAR),
- few unlicensed files.
It is a FOSS project. A full list of software developed by third-parties is viewable within the browser at chrome://credits (similar to this online page) - a trademark according to Google (Search "Chromium™" at Trademarks list)
- a blue-colored logo (Search "Chromium" at Logos list)
- the similar system requirements as Google Chrome
- the similar user interface and settings as Google Chrome
- the similar sandbox as Google Chrome
- the similar support for extensions and themes as Google Chrome
- the similar user agent as Google Chrome
- the similar experiments Field Trials (Finch) (viewable as a list in "Variations" at chrome://version) as Google Chrome (and similar as Mozilla Firefox studies and as Microsoft Edge's ECS)
- the built-in Chrome PDF Viewer (known as PDFium), on Windows
- the built-in Chromoting Viewer (To use it, you need to first install the Chrome Remote Desktop extension)
- the built-in Google Native Client
- the built-in Print preview and print system
- no stable version offered by the official team (aka The Chromium Authors)
- no digital signature
- no auto-update system (Solution: Use #updaters • On #linux, use the integrated software/package manager, even a PPA)
- no Google API keys (Solution: Check #google-api-keys)
- no built-in Flash player (Solution: Check #flash)
- no unwanted software protection (known as Chrome Cleanup and "software_reporter_tool.exe"), on Windows
- no support of proprietary codecs (AAC, H.264/MP4) (Solution: Check #html5-audio-video)
- no user RLZ identifier
- no user metrics (usage statistics) (opt-in option)
- no crash report (opt-in option)
- More details on the official site, focused on Linux.
Why I used the "similar" word, here?
I cannot certify that it is "same/identical" as Google Chome because Chrome is a closed-source software.
Some developers maintain #chromium-forks that offer more features and enhancements. Thanks a lot for developers! ;)
Secure Preferences
Chromium has "Secure Preferences" feature which protect user data against #malware. On Windows, macOS and Linux, the user profile is encrypted based on the machine SID (For info, you can change the SID on Linux). So extensions, certificates and passwords are not portable. It works for Chromium and all #chromium-forks like Google Chrome, Microsoft Edge, Opera, Vivaldi, Brave, ungoogled-chromium... (except Cent Browser which is closed-source and therefore can be easily corrupted)Info relative to this feature:
- PortableApps::Google Chrome portable (Read "App Notes")
- PortableApps::Opera portable (Read "App Notes")
- Portapps::Brave portable (Read "Infos"... or detailed info on Github)
- Copy Chrome extensions from one computer to another
- How to migrate Google Chrome profile (extensions, cookies, etc.) to another Windows installation?
- profile_pref_store_manager.cc (Chromium code source)
- machine_id.cc (Chromium code source)
How to migrate user data from one computer to another?
The simple way to migrate your data is to synchronize them.
For info, you can also use free services like floccus, xBrowserSync.
Also, to export/import data manually:
- Bookmarks: chrome://bookmarks
- Passwords: chrome://flags/#PasswordImport → Enabled (screenshot). Then restart the browser. Then chrome://settings/passwords (screenshot). For info, you can also use the #flag: --enable-features=PasswordImport (screenshot)
- Extensions: Import and export do not exist. But with an extension like Export links of all extensions (Archive: ZIP), it is possible to list, in an HTML file, all browser extensions used.
There are unstable ways too:
using these #command-line-flags: --disable-machine-id --disable-encryption (info)- using an hacking method to bypass "Secure Preferences".
Google API keys
By default, few Google services (Chrome Sync...) are not available on Chromium. They are reserved for Google Chrome users. For example, the Chrome Sync capability in Chromium based browsers allows you to login to Google’s Sync cloud servers and save your passwords, browsing history and bookmarks/favorites to your personal encrypted cloud vault inside Google’s infrastructure. Extremely convenient for people who access the Internet using multiple devices.To use these Google services, Chromium needs Google API keys.
Chromium can display a top message if the Google API keys are needed for Google services (screenshot):
Google API keys are missing. Some functionality of Chromium will be disabled. Learn More
How to just hide the top message "Google API keys are missing..."?
Add the --no-default-browser-check flag at the end of the Chromium shortcut and restart the browser (screenshot)
How to create your own Google API keys?
With your own Google API keys, many Google services (Chrome Sync...) will work.
- Follow the official API Keys page to get them.
- Other info at Github Gist.
- A tutorial video on Youtube (mirror)
Then set three environment variables.
On Windows
Launch Command Prompt (cmd.exe) and enter the following commands: setx GOOGLE_API_KEY yourkey
setx GOOGLE_DEFAULT_CLIENT_ID yourclientid
setx GOOGLE_DEFAULT_CLIENT_SECRET yourclientsecret
(setx = set environment variables permanently)On macOS
This tutorial was written by Aargl on december 7, 2018 (#comment-4078). Thanks to him. There are 2 methods:1. Method with ChromiumSyncEnabler
ChromiumSyncEnabler (Archive: ZIP)- Put Chromium_template and ChromiumSyncEnabler.py at the root of the current user (~/)
- Put Chromium.app in ~/Applications
- In Terminal, type: python /Users/your_user_name/ChromiumSyncEnabler.py
- Enter your API keys
N.B.: if you want to activate for all users, do the same procedure putting the files respectively in / and /Applications (I haven't tried, but I can't see why it wouldn't work...)
2. Method with a plist file
Creation of a ~/Library/LaunchAgents/setenv.ChromiumSync.plist containing: <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd ">
<plist version="1.0">
<dict>
<key>Label</key>
<string>setenv.ChromiumSync</string>
<key>ProgramArguments</key>
<array>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_API_KEY</string>
<string>your_key</string>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_DEFAULT_CLIENT_ID</string>
<string>your_key</string>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_DEFAULT_CLIENT_SECRET</string>
<string>your_key</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
(with "your_key" being the corresponding Google API key)Of course, you can name the LaunchAgent setenv.ChromiumSync or anything you want.
- This is perfectly working in 10.11
- In 10.9, you must create 3 separate LaunchAgent files instead (one for each key)
- I couldn't test more recent OSes, but I think it should work as in 10.11
The choice between method 1 or 2 depends on wether you want to enter your API keys each time or not... ;-)
On Linux
export GOOGLE_API_KEY yourkey
export GOOGLE_DEFAULT_CLIENT_ID yourclientid
export GOOGLE_DEFAULT_CLIENT_SECRET yourclientsecret
How to disable Google API keys?
Without Google API keys, many Google services (Chrome Sync...) will not work.
On Windows
Launch Command Prompt (cmd.exe) and enter the following commands: setx GOOGLE_API_KEY "false"
setx GOOGLE_DEFAULT_CLIENT_ID "false"
setx GOOGLE_DEFAULT_CLIENT_SECRET "false"
(setx = set environment variables permanently)Now launch Chromium.
Widevine plugin
Widevine is a closed-source Google plugin to play DRM content (= protected audio/video files) for web browsers. Companies including Amazon Prime Video, BBC, Hulu, Netflix, Spotify and Disney+ use Widevine to manage the distribution of premium content.Chromium does not support Widevine natively. Note that Chromium developers and most of Chromium users do not use this Google plugin at all. We do not bundle/share it. Other people tried to obtain a licence from Google for an open-source project and finally did not get it (Archive: 1).
On this website, the widevine support is enabled on the stable versions. (These versions are compiled with the GN argument: enable_widevine = true). So you need to install the Widevine CDM plugin yourself to play DRM content.
In Chromium and Google Chrome, you can check the Widevine support at chrome://components → "Widevine Content Decryption Module" → The number must be different than 0.0.0.0 (screenshot)
Websites to freely test Widevine:
- https://bitmovin.com/demos/drm
- https://demo.castlabs.com/ (Choose videos with labeled "DRM")
- https://shaka-player-demo.appspot.com/demo/
How to install the Widevine CDM plugin?
- First of all, make sure you have a Chromium version with the enabled support of:
- the protected content
chrome://settings/content/protectedContent - Widevine and H.264/MP4
Check these tags on this website: widevine all-codecs
- the protected content
- Now, get the Widevine CDM plugin. The latest version is: 4.10.2891.0
For info, this is an automated update via this official TXT file.
2.1 From official links:- 4.10.2891.0-win-x64.zip (64-bit Windows)
- 4.10.2891.0-win-arm64.zip (64-bit Windows on ARM)
- 4.10.2891.0-win-ia32.zip (32-bit Windows)
- 4.10.2891.0-mac-x64.zip (64-bit macOS)
- 4.10.2891.0-mac-arm64.zip (64-bit macOS on ARM)
- 4.10.2891.0-linux-x64.zip (64-bit Linux)
4.10.2891.0-linux-ia32.zip(32-bit Linux)
2.2 Or from offline installers of Google Chrome
Prefer these following websites because you can unzip the executable files (*.exe) and see the whole content. Note these download links of Google Chrome are official.- Chrome offline installers
- [JP] chrome::lutra-fs.me
- [JP] chrome::noki.eu.org
- [JP] chrome::iplaysoft.com
- [JP] chrome::atvnk.com
2.3 Or from the Google Chrome website
In this case, you must to install Google Chrome because you cannot unzip the executable files (*.exe) :/
Official standalone versions:- Google Chrome (64-bit / Windows)
- Google Chrome (32-bit / Windows)
- Google Chrome
- Unzip the content of this Widevine CDM plugin
(This is a 7-zip self-extracting archive) - Copy this Widevine CDM plugin's content to your Chromium "WidevineCdm" folder like this following structure, on Windows:
(screenshot)WidevineCdm
├── LICENSE.txt
├── manifest.json (Note: this file contains the Widevine version or even the file paths ^^)
│
├── _platform_specific
├── win_x64 (Note: if it is for 64-bit Windows, obviously!)
├── widevinecdm.dll
├── widevinecdm.dll.sig - Launch Chromium browser
- Go to the top of this website and check if the "widevine" tag is displayed. (screenshot)
and check chrome://components → "Widevine Content Decryption Module" - End.
Flash plugin
Flash is a deprecated multimedia software platform. Adobe retired Flash on January 1, 2021, on all plateforms. Roadmap for Chromium. Roadmap for Firefox.- Since 2021, the Flash PPAPI plugin (aka PepperFlash) plugin is discontinued. For info, PepperFlash is secure because it works in a sandbox. In short, it executes in its own process, separate from the browser's rendering engine.
- Since 2015, the Flash #npapi plugin is discontinued.
How to quickly install the Flash plugin? (Obsolete content!)
On Windows and macOS, Chomium find PepperFlash itself (= without #command-line-flags)
- Install PepperFlash (PPAPI) from Adobe website.
- Disable the checkbox in the chrome://settings/content/flash page. (screenshot)
- Test if animation works on the Flash Player versions page.
- Enjoy!
How to manually install the Flash plugin? (Obsolete content!)
This is a full manual installation tutorial.
(If Google Chrome is already installed, go directly to "3. Add command-line flags"
1. Get PepperFlash (PPAPI)
This plugin is a non-free (proprietary) software developed by Adobe, and distributed bundled with Google Chrome. So get it from the official sources: Adobe or Google.1.1 From Adobe
Different official ways:- Stable version - Download page: Adobe Flash Player (Other versions) (Choose your OS and the PPAPI version)
- Stable version - Direct link: install_flash_player_ppapi.exe (Windows)
- Stable version - Direct link: install_flash_player_osx_ppapi.dmg (macOS)
- Beta version - From Adobe Labs (Search "PPAPI" and "Chromium" for your platform)
After install, the plugin path will be:
- On a 64-bit #windows:
- C:\Windows\system32\Macromed\Flash\pepflashplayer64_[version].dll (64-bit version)
- C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)
- C:\Windows\system32\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)
1.2 From Google Chrome
Canary channel:- On #windows, get pepflashplayer.dll from Chrome Canary (64-bit) if you use 64-bit Chromium
- On #windows, get pepflashplayer.dll from Chrome Canary (32-bit) if you use 32-bit Chromium
- On #mac, get PepperFlashPlayer.plugin from Chrome Canary (64-bit)
1.3 From an unofficial source
(Use an online service to prevent #malware)- Search "PepperFlash" or "PPAPI" at [RU] effect8.ru or patheticcockroach.com
- Download and open the .7z archive
- Get "pepflashplayer.dll" (rename it, if needed) and "manifest.json" files.
Optionally, get the Flash version number:
(If you want to see the correct version number on Chromium internal pages)
- On all platforms, open the manifest.json text file in the PepperFlash folder.
- On Windows, you can do a right-click → Properties → Details, on the .dll file
2. Change the plugin directory
If you want, prefer a short path for the plugin. It will be easier for the next step. ^^Example on Windows: Put this .dll file in a path like C:\PepperFlash\ (Create the directory if needed)
3. Add command-line flags
Use these #command-line-flags:- --ppapi-flash-path=[plugin path]
- --ppapi-flash-version=[plugin version]
- And optionally --allow-outdated-plugins to disable browser notifications about outdated plugins
On #windows, create a Chromium shortcut. Then go to its properties and edit the target field:
--ppapi-flash-path="C:\PepperFlash\pepflashplayer.dll" --ppapi-flash-version="32.0.0.465" --allow-outdated-plugins
On #mac, you will need to launch it from the command-line (in the Terminal):
/Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=32.0.0.465&
The "&" at the end is not a typo. It is there to make sure Chromium is launched in a separate thread. Without the "&", Chromium would exit as soon as you quit the Terminal. Moreover, to simplify the Chromium launch, check How to create simple Mac apps from shell scripts (Archive: 1). Also see the #comment-566 and #comment-344. 4. Restart the browser
Relaunch it to apply changes.5. Check the installation
- Type chrome://settings/content/flash to manage it.
- For update, check the Flash Player version on the official page.
- For security information, see the security bulletins and advisories
6. Enjoy!
Now, even after browser updates, Chromium uses PepperFlash. ^^NPAPI plugin
NPAPI is a deprecated API that allows browser extensions to be developed. Chromium 45.0.2416.0 (331982) is the last version which still has NPAPI plugin support enabled via chrome://flags or group policy registry. (source • NPAPI deprecation)How to still use a NPAPI plugin?
Few ways:
- Switch to other browsers still supporting NPAPI plugins (like Waterfox browser).
- or install an older Chromium version (Ex: 331982, 331959, 331938, 331935...)
- or install the IE Tab addon which allows users to view pages using the IE layout engine
More info on site archives:
- chromium::wayback.machine (Sunday, 26 Jul 2015)
- chromium::archive.is (Friday, 17 Jul 2015)
HTML5 audio/video
By default, Chromium does not support proprietary codecs (AAC, H.264/MP4) in the HTML <audio> and <video> elements.How to use Chromium with all audio/video codecs?
Few ways:
- On #windows and #mac, use builds with all-codecs or all-codecs+
- or compile Chromium from #source-code with proprietary codecs, yourself.
- or install an older version having ffmpegsumo file (Ex: 333350, 333334, 333283, 333258...)
- or choose other #browsers
- On #linux, you can use Chromium with proprietary codecs (ex: FFmpeg under Ubuntu)
Before 4 June 2015, we used an alternative with the Google Chrome ffmpegsumo file and our Patch HTML5 Media extension. More info on site archives:
- chromium::wayback.machine (Monday, 8 Jun 2015)
- chromium::archive.is (Friday, 5 Jun 2015)
Note about the H.265/HEVC video codec
Chromium does (and will) not natively support the H.265/HEVC codec. (official source)
- The licence of H.265/HEVC is non-free. It is currently mainly supported by Apple. (Support of H.265/HEVC in web browsers)
- The Chromium team prefers to focus on the open-source AV1 codec. This one is supported by major companies (Alliance for Open Media) like Google, Microsoft, Intel, Samsung... (Support of AV1 in web browsers).
Check HTML5 audio/video support at https://tools.woolyss.com/html5-audio-video-tester/
If there is a video issue, disable hardware acceleration (see #browser-crash).
Advanced
1. Internal pages
To access to all internal pages, use chrome://about. Copy and paste this special URL directly into the address bar (omnibox). Obviously, this special URL works only in Chromium and Google Chrome. Note: About configuration settings, there is nothing similar to Firefox's about:config in Chromium.Few internal pages:
- chrome://components (Show and update info about available components like Widevine...)
- chrome://conflicts (List all modules loaded into the browser)
- chrome://credits (View all licensing info • Similar to this online page)
- chrome://flags (View all experimental features • You can set each feature)
- chrome://gpu (Show info about GPU)
- chrome://net-export (Get all networking related info)
- chrome://omnibox (Test and follow responses of the searches via the omnibox/address bar)
- chrome://policy (Manage Chromium, for administrators • Policy list)
- chrome://predictors (List autocomplete action predictors and resource prefetch predictors based on user recent search and browsing history)
- chrome://quota-internals (Show info about disk space and storage usage)
- chrome://settings/content/all (List the number of cookies each site has set)
- chrome://sync-internals (Show info about the Chromium sync feature)
- chrome://translate-internals (View all supported internal languages)
- chrome://version (Show details of Chromium version)
About browser plugins
Since version 57, the chrome://plugins page no longer exists. (official source)
Info:
- Manage PDF viewer and Flash plugins: chrome://settings/content
- Update components (like Widevine): chrome://components
2. Keyboard shortcuts
To use keyboard shortcuts (on Windows, Mac and Linux), check this full list of official shortcuts... and this one if you are developer. Most of the shortcuts are similar to IE, Firefox or any other browser.3. Command-line flags
There are command-line flags (or "switches") that Chromium accept in order to enable particular features or modify otherwise default functionality. Note flags often contain experimental or obsolete code, so they tend not to stick around for long.- Run Chromium with flags
- List of Chromium command-line switches (Auto-updated list provided by Peter Beverloo)
How to start Chromium directly in incognito (or private) mode, on Windows?
Add the "--incognito" flag at the end of the Chromium shortcut and restart the browser. (screenshot)
"C:\{...}\Chromium\Application\chrome.exe" --incognito
4. User data directory
About your profile (history, bookmarks...), it is important to know where is stored your user data.How to change the user data directory?
Add the "--user-data-dir" flag at the end of the Chromium shortcut and restart the browser. (screenshot)
"C:\{...}\Chromium\Application\chrome.exe" --user-data-dir=..\my-profile-path
5. External extension installation
How to install an external browser add-on?
If you wish to install extensions directly instead of just downloading the .crx source file, you must:
- Change the flag chrome://flags/#extension-mime-request-handling to "Always prompt for install".
- Click on the link of the .crx file you want to install
Download the .crx source file of any extension directly from the Chrome Web Store via Get CRX or via a site like Chrome Extension Downloader, CRX Extractor, Crx4Chrome. (For info, you can see the source code before to download the extension: CRX Viewer)
- Go to chrome://extensions
- Drag and drop the .crx file on chrome://extensions
If it does not work...
- Add the "--enable-easy-off-store-extension-install" flag at the end of the Chromium shortcut and restart the browser. (screenshot)
- Go to chrome://extensions
- Drag and drop the .crx file on chrome://extensions
If it still does not work...
- Unzip the .crx file
- Go to chrome://extensions
- Drag and drop the unzipped folder on the page... or click on Developer mode (Toggle in top right) then Load unpacked extension... (screenshot)
About updates:
- You have to update manually
- You can update when you want! ^^
- If ever a new version sucks, just re-install the previous one
6. Source code
Before all, check the official guide for developers.Official links to easily get or see the full Chromium source code:
- Google Git chromium/src
- The official GitHub mirror of the Chromium source
- Chromium Code Search or chromium/src (Old pages: Code search or chromium/src/)
- - Source tarballs and its mirror ("-lite" is for building desktop Chromium).
- Also, there is the official Github mirror. - Chromium source code of the latest stable version: chromium-135.0.7049.114.tar.xz (mirror • File checksums)
ViewVC(Obsolete since the version 39.0.2132.2, on August 2014)
Interesting info:
- [video] Building Chromium from source (by Aphrx • 2021 • mirror)
- Building ungoogled-chromium (by Eloston • 2020)
- How to build chromium on Windows (by Intel • 2019)
- How to build chromium on macOS (by Intel • 2019)
- How to build chromium for Android (by Intel • 2019)
- How to build chromium for Linux (by Intel • 2019)
- Building Chromium on Windows from source (by Jeremy Sinclair • 2019 • Archive: 1)
- How to compile Chromium with audio/video codecs for Windows (by Nik • 2018 • Archive: ZIP)
- How to build Chromium with proprietary codecs (OS X) (by No encoding • 2018 • Archive: 1)
- Bash script to build and install latest stable Chromium from source on OS X (by Bobo • 2017 • Archive: ZIP)
- [UA] Компіляція браузера Chromium для Ubuntu (x265, HEVC) (by D.Bilous • 2016 • Archive: 1)
How to compile Chromium for Mac(by sbagmeijer • 2015 • Original site is down!)Contributing to Chromium: an illustrated guide(2015 • Archives: 1 or PDF)
7. Older version
Never update your browser with a very old version. It even does not start.To downgrade Chromium installed with the Installer (.exe):
- Open Chromium and check its actual version at chrome://version
- Close Chromium.
- Uninstall Chromium WITHOUT to delete your #user-data-directory. It is an option of its uninstaller. (screenshot)
- Get the Installer (.exe) of an older version (from the → download/ page or Snapshots repository about "official" builds)
- Execute it to install Chromium.
- Open Chromium and check the new installed version at chrome://version
8. Browser crash
You have encountered a browser crash or issue :/Few ways to help you:
- To disable hardware acceleration: chrome://flags/#disable-accelerated-video-decode or chrome://settings → [Advanced] → System
- To disable/enable a browser feature: chrome://flags
- To check for conflicting software: chrome://conflicts
- To disable extensions/add-ons: chrome://extensions
Also you can use #command-line-flags: --disable-gpu, --disable-accelerated-video-decode...
8. Browser benchmark
To test performances of the browser, do differents benchmarks.Except as otherwise noted, for the result, a higher number is better.
Free websites without registration:
- ARES-6 (Various tests using the newest web standards and features)
- Basemark (Various tests using the newest web standards and features)
- JetStream (JavaScript benchmark developed by Apple)
- Kraken (JavaScript benchmark developed by Mozilla • Result: A lower number is better)
- MotionMark (Graphics benchmark developed by the WebKit team)
- Octane (JavaScript benchmark developed by Google)
- Speedometer (Performance benchmark that repeats the same actions using DOM APIs)
- WebXPRT (HTML5 and JavaScript test developed by benchmark maker Principled Technologies)
API
This is a free and simple API for developers to update Chromium to the latest good build via a bash (shell) script, a browser extension... Read my #notes. Please, do not use this API to build other websites. To prevent abuse, the site can audit each API request.API details
GET request parameters:
- os → (required) windows or mac or android
- bit → (optional • 64 by default) 64 or 32
- out → (optional • json by default) json or string or revision
Response:
chromium → windows or mac or android →
- architecture → (string) 64-bit or 32-bit
- timestamp → (integer) Unix time of this release built on the Chromium Buildbot server
- editor → (string) The Chromium Authors
- channel → (string) dev
- repository → (string) snapshots
- version → (string) (like xx.x.xxxx.x)
- revision → (integer) Git revision's commit position
- commit → (string) Git revision's commit hash
Examples:
Links
Except the Wikipedia's Chromium page, these links are official and point only to the Google sites.Focused on Chromium:
- Chromium Blog
- Chromium Browser Snapshots
- Chromium Dash
- Chromium Discussion (on Google Groups)
- Chromium Gerrit (Code review)
- Chromium Main Console (Buildbot console)
- Download Chromium (ZIP archives)
- Chromium Issue Tracker
- Monorail (The issue tracking tool for chromium-related projects)
- The Chromium Projects (The main Chromium website)
- Wikipedia's Chromium page
Focused on Google Chrome:
- Chrome Platform Status
- Chrome Release Channels
- Chrome Web Store (Extensions and themes 100% compatible with Chromium)
- Google Chrome Help (100% compatible with Chromium)
- Release updates from the Google Chrome team (Google blog)
Browsers
1. Chromium forks
In simple words, a fork of Chromium means Chromium engine is used to create another web browser.Proprietary browsers:
(developed by official contributors of the Chromium #project)
- Google Chrome (USA)
- Microsoft Edge (USA)
- Opera (Norway/China • Opera (company), Otello Corporation, Golden Brick Capital/Qihoo 360)
- Samsung Internet (South Korea)
- Vivaldi (Iceland • Chromium's modified code is still open source)
- Yandex Browser (Russia)
I do not recommend:
- 360 Secure Browser (Proprietary)
- Comodo Dragon (Proprietary • Famous company but its Chromium is ever outdated compared to the #stable-chromium-version)
- Epic (Proprietary • Reviews)
- Slimjet (SlimBrowser) (Proprietary • Reviews - Archive: 1)
- SRWare Iron (Proprietary • Versioning system is not clear: no source code of the latest version available since 2011 - Archive: 1)
- or other proprietary browser with "better privacy" than Google Chrome.
Why not recommended?
Because all of these browsers are closed-source, outdated, based on Chromium like Google Chrome... and most of the features they remove don't even exist in Chromium, in the first place. Control your personal info and #privacy yourself ^^
Colin (InsanityBit) explains this very well at "SRWare Iron Browser – A private alternative to Chrome?" (2012 • Archives: 1, 2)
Note if a new browser with "better privacy" than Google Chrome is based on Chromium and is fully open-source, it should be ok for me. But... Google is famous. Its privacy policy and marketing strategy are well known. So you have to ask you some questions. Do you trust in an unknown team more than Google? Is an outdated Chromium fork?
- Google engineer finds holes in three 'secure' browsers (2016 • Archive: 1)
- Google calls out Comodo's Chromodo Chrome-knockoff as insecure crapware (2016 • Archive: 1)
- Google warns! (2015 • Archive: 1)
Few free and open-source Chromium-based browsers:
- Brave (Block website trackers and remove intrusive internet advertisements • code differences with Chromium )
- Bromite (Patches for Chromium with adblocking features and enhanced privacy)
- Dooble
- Falkon (Formerly QupZilla)
- Iridium (tarball, git, github, code differences with Chromium • Reviews)
- Kiwi Browser (Browser with extensions support, ads & cryptojacking protection...)
- Otter Browser
- qutebrowser (A minimalist browser)
- Thorium (Chromium fork with patches for speed, privacy and usability)
- ungoogled-chromium (A set of patches for removing Google integration • 2016 reviews, 2018 reviews, 2020 reviews)
Aviator(Discontinued project since 2016 • Reviews)Inox(A set of patches applied on the Arch Linux chromium package • Arch Linux website)Superbird(Based on a development version • No source code since 2016 - Archive: 1)
2. Other open-source "non-Chromium-based" browsers
- Basilisk (Firefox-based using an old Firefox core version)
- Firefox
- LibreWolf (Firefox-based)
GNU IceCat(Outdated since 2019)- Midori (Webkit-based)
- NetSurf (Works on any OS)
- Pale Moon (Firefox-based using an old Firefox core version)
- Tor Browser (Firefox-based using Tor, an anonymity network)
- Waterfox (Firefox-based using an old Firefox core version • Acquired by System1, an advertising company)
- and other open-source browsers.
Privacy
For a better privacy protection, use open-source #browsers like Chromium, Firefox. Do not forget: It is open-source does not mean it is secure and respects user privacy. Moreover, security ≠ privacy ≠ anonymity. If your browser is fully "open-source", it means that somebody with the capability can review the #source-code. It is easier for developers to find malicious code with versioning tools like Git or SVN. (Ex: Chromium downloads a Chrome extension as a binary without source code → corrected 7 days after the report). Only an open-source code allows such defense. This is better for secure browsing and user privacy. The security of Chromium is very solid. While I recommend ungoogled-chromium, Bromite and Firefox (cf. about:config/user.js settings, containers system, better content-filtering, easier way to stop browser automatic connections, support of a self-hosted Firefox Sync server) as the most reliable browsers for privacy enthusiasts in a standard web browsing, Chromium is probably a reasonable alternative for everyday web browsing.My way for a standard web-browsing (but do as you like ^^):
- Modify your #hosts-file to stop "natively" domains who serve ads, spyware and malware
- Use a VPN with strong encryption for your whole OS or router to bypass many restrictions on Internet. Note you are not anonymous behind a VPN service (cf. Browser fingerprint, Server-side tagging...) (It is better than browser VPN/proxy #extensions)
- Use an up-to-date web browser
- Change few #browser-settings
- Install few #extensions
How to really be anonymous on the Web?
The anonymization solutions are especially necessary for the exercise of freedoms (ex: for journalist, political opponent in certain countries, researcher, whistleblower...). These solutions are obviously very used by hackers too. Personally, I think most people cannot be anonymous on the Web even using a VPN, proxy or TOR network. It is a myth that you cannot be tracked online. If you exist, you are findable, especially if you use multiple devices and websites. There are a lot of technologies to identify a user and get its data. Check the #guides and #tests for more information.
But it is possible to really be anonymous on the Web if your respect all security rules. The book "The Art of Invisibility" written in 2017 by Kevin D. Mitnick will convince you. In a few words, do not trust proprietary software/services, third-party VPN service providers (VPN Leaks, 'no log' VPN providers..., Another VPN leak..., VPN hacked...) and the cryptocurrency (like Bitcoin).
- Buy a new computer (like a used computer) with cash, from an unknown person.
- Then remove the internal HDD (or format it). You will not use it. Prefer an external USB flash/SSD drive.
- Use Tails, Whonix, Qubes OS or a similar live Linux distribution. These ones uses the Tor network (Note Tor is often attacked).
- Change the MAC address.
- Connect to a public WiFi connection.
- Do not change settings or add extensions on Tor Browser. It will prevent your Browser fingerprint.
- Never login to a site/service for which you are already known.
- SearX and .onion addresses are welcome.
- Here we go!
Do you know...
Sure you can protect your privacy against tracking and profiling tools but it is really painful because these tracking tools are everywhere today: on Internet (website, app...), at home (computer, phone, router, smart TV, smart home speaker, smart bulb, smart grid...), in your car (GPS system, connected car...), in the street (video surveillance camera...), at your ISP and elsewhere. You can find them in hardware (firmware) and software (operating system, app, website, extension...).
Do you know in all computers (excepted RISC-V and Libreboot) there is an exploit-friendly firmware that user has no access?
Ex: in Intel processors, in AMD processors, in Raspberry Pi (proprietary Broadcom processor).
Do you know you are readily recognizable if you install browser extensions like an ad-blocker? It means, if you install browser extensions, your Browser fingerprint is unique. So you are unique on the Web.
Ex: browserleaks::proxy, Browser Fingerprint
Do you know there are probably untrusted certificates on your computer?
Ex: Apple, Google, Microsoft and Mozilla..., Dell..., Google..., Microsoft..., Lenovo..., Surveillance firm...
Do you know it is possible to follow a user behind Tor browser?
Ex: Advanced Tor browser fingerprinting, Browser Fingerprinting, Tor and its discontents, with CSS (noscript-tracking.go, CrookedStyleSheets), with extension fingerprinting or with a zero-day exploit!...
About the "No log" mention of a VPN, do you know the jurisdiction of the country where the VPN server is located has authority on the jurisdiction of the country where the VPN provider is located?
Ex: Choose a VPN provider from United Kingdom and connect to a French VPN server. There are no log in United Kingdom. Ok, but this is not the problem! The VPN server is in France and there will be logs in France. This is the law. [FR] Minimal logs lifetime in France: 360 days (Source: "Article 3"). [FR] Minimal logs lifetime in Europe: 14 days. So be careful when your VPN provider and its VPN server are located in countries from the Five Eyes, Nine Eyes or Fourteen Eyes.
Do you know Linux (like Windows and Mac) devices have a unique identifier?
Ex: Linux devices have a unique identifier called machine-id. Here is how to change it.
1. Browser update
The reason for updating to the latest version is security. As security threats are found, they are fixed. Using an old version expose user to a number of security holes and privacy issues. Browsers are far more subject to hacking than other software.2. Browser settings
Adjust all settings and advanced settings in chrome://settings:- Do not log in with a Google account in the browser (screenshot • Do not sync your data!)
- Do not save passwords in the browser (Prefer a free and open-source password manager like Bitwarden, KeePass, LessPass or Password Safe)
- Enable the incognito (or private) mode (Ctrl+Shift+N shortcut • Use a #flag to start Chromium in this mode)
- Disable all options in the "Privacy and security" section (chrome://settings/privacy) because most of them use an external Google service. (Ex: "Safe Browsing" option uses Google Safe Browsing • More info about privacy settings)
- Block third-party cookies (chrome://settings/content/cookies)
- Block the #flash plugin (chrome://settings/content/flash)
- Do not share your location (chrome://settings/content/location)
- Prevent canvas fingerprinting (Use the --disable-reading-from-canvas #flag)
3. Hosts file
Modify your hosts file to prevent your OS from connecting to domains who serve ads, spyware and malware. This will increase your OS security and save bandwidth.- Dan Pollock's list
- MVPS HOSTS
- Peter Lowe's list
- Malware Domain List
- Unified hosts file with base extensions
- No more ads, tracking and other virtual garbage
Note:
- Few #extensions like uBlock Origin can also use these lists in their settings.
- Few tools like Pi-hole and AdAway can also use these lists in their settings.
- Free and open-source auto-updating Hosts managers: hostsmgr, HostsFileEditor (on Windows), Gas Mask (on macOS)
4. DNS services
By default you are using the DNS servers of your ISP but you do not have to stick with them. Before to choose one, compare DNS performance. Free alternative Internet DNS services for personal use:- Adguard DNS
- Cloudflare DNS resolver (by Cloudflare • 1.1.1.1 for Families)
- Comodo Secure DNS (by Comodo)
- DynDNS (by Dyn)
- Google Public DNS
- Nextdns
- OpenDNS (by Cisco)
- OpenNIC
- Quad9 DNS
- Yandex.DNS (by Yandex • Technical details - IPv4 and IPv6)
Note:
- The DNS over HTTPS (aka DoH) page on the official Chromium website.
- You can also use a DNS over HTTPS client (screenshot of Firefox 62+). Check Publicly available servers.
- You can also use a DNSCrypt client (Ex: Encrypt your DNS traffic with Simple DNSCrypt for Windows)
- You can also use your own DNS resolver with Unbound or other software.
5. Web search engines
Note: Few #dns-services and #extensions exist to protect user privacy on search engines.Search engines
Search engines index the content of web pages by running an algorithm on a web crawler.Metasearch engine
Metasearch engines use another search engine's data to produce its own results from the Internet. Search engine map.- Disconnect Search (by Disconnect.me • Uses Bing, Yahoo... results)
- DuckDuckGo (uses its own crawler + Bing, Yahoo, Yandex, Wikipedia... results, on Amazon servers (AWS) • Review at an 8ch page archive • To search without JS, choose the html or lite version)
- Ecosia (uses Bing results)
- Fireball (uses Bing results)
- Oscobo
- Private.sh (by Private Internet Access • Uses Gigablast results)
- Qwant (uses its own crawler but is partner with Microsoft for Bing results, Bing Ads and Microsoft Azure • Its lite version)
- Startpage (uses Google results • Owned by System1, an advertising company)
- Swisscows (uses its own crawler + Bing results with enabled parental filter)
- YaCy (A peer-to-peer search engine)
If you are a web developer, develop your own metasearch engine yourself ^^
- Searx (uses many search engines • Source code in Python • Author: Adam Tauber, @Searx_engine • Searx instances)
- MetaGer (uses Yahoo... results • Source code in PHP)
- Whoogle Search (uses Google results • Source code in Python • Author: Ben Busby)
- Googol (uses Google results • Source code in PHP • Author: Bronco)
6. Extensions
Note:- With the use of extensions, you become more easily identifiable (cf. Browser fingerprint, Server-side tagging...)
- Extensions hosted on the Chrome Web Store are updated via the Chrome update mechanism (cf. Chromium source code) which developers and users do not control. For a manual installation, read the #external-extension-installation part.
- Here, priority to open-source (and non-obfuscated code) extensions for Chromium and Firefox:
Block ads, trackers, scripts and popups
uBlock Origin- Download: store, amo
- Alternatives: Privacy Badger, Adblock Plus, AdBlock, Disconnect, Ghostery, Adguard AdBlocker, Fair AdBlocker, Forget Me Not, NoScript
- Info: Add filters to your ad-blocker via FilterLists (an open-source website)
- My advice: By default, block third-party scripts and frames (uBlock Origin medium mode • screenshot). Also, about Adblock Plus or AdBlock, disable "Acceptable Ads" option (screenshot).
Stop link redirection in Google, DuckDuckGo and Yandex search pages
Don't track me Google- Download: store, amo
- Alternatives: Redirect Blocker, Redirect Bypasser
Clean URLs to remove tracking elements from URLs
ClearURLsControl the HTTP Referer on a per-site basis
Referer Control- Download: store, amo
- Alternatives: Smart Referer, Web Developer
- Info on wikipedia
Prevent canvas fingerprint
Canvas Blocker (Fingerprint protect)- Download: store, amo
- Alternatives: Canvas Defender, Canvas Fingerprint Defender
- Info on wikipedia, browserleaks, ghacks
Emule locally CDN
Decentraleyes- Download: store, amo
- Alternatives: LocalCDN
- Info on wikipedia, decentraleyes test page, localcdn test page
Prevent WebRTC IP leak
WebRTC Leak Shield- Download: store, amo
- Alternatives: WebRTC Control,
WebRTC Network Limiter,WebRTC Leak Prevent - Info: An extension can only block the leak of your IP address. It does not block WebRTC in the "core" of Chromium. uBlock Origin can protect against the WebRTC IP leak. You can do some #tests.
Prevent CSS Exfil attack
CSS Exfil Protection- Download: store, amo
- Info on BleepingComputer, Github and mike-gualtieri.com
Unblock websites with a browser VPN/proxy
Browsec- Download: store, amo
- Alternatives: anonymoX, HidemanVPN, TunnelloVPN, TouchVPN, Hotspot Shield
- My advice: Prefer to pay for a safe and secure VPN provider protecting your whole OS ; or use a free VPN service without registration. Do not use Hola!, ZenMate or Betternet in their free version. Hola! is a botnet. Betternet shares/sells user data to third-parties. In its free version, ZenMate needs a registration.
Display sites quality
WOT (Web of Trust)- Download: store, amo
- Alternatives: DuckDuckGo Privacy Essentials, Terms of Service; Didn’t Read
- My advice for the WOT addon: Do not share your data. (WOT settings → Real-time protection → Set to off)
7. Tools
- Firewall
- Freenet
- I2P (Invisible Internet Project)
- Proxy
- VPN (Virtual private network)
- Tor (Anonymity network)
8. Guides
- Technical analysis of client identification mechanisms (Chromium)
- Privacy tools (2021 • Source code)
- PRISM break (2021 • Source code)
- Privacy Respecting (2021)
- [FR] Google Tag Manager (Server-Side Tagging), la nouvelle arme anti adblock?
(2020 • Google Tag Manager (Server-Side Tagging), the new anti-adblock weapon: [Translated EN] HTML, [Translated EN] PDF) - Web browser privacy: What do browsers say when they phone home? (2020 • Archive: PDF)
- Who left open the cookie jar? (2018 • Archives: 1, PDF)
- Online tracking: A 1-million-site measurement and analysis (2017 • Archive: PDF)
- Are VPN providers more trustworthy than your ISP? (2017 • Archive: 1)
- Don't use VPN services (2015 • Archive: 1)
- Category: Internet privacy (Wikipedia)
- Chromium privacy
9. Tests
Reputable and reliable sites to show or prevent user data tracking:- Am I Unique (Device fingerprinting)
- AudioContext fingerprint test page
- Browser Leaks (WebRTC IP leak, System fonts, HTML5 Canvas fingerprinting...)
- BrowserSpy (It shows how much information can be retrieved from web browser)
- Browsing experience security check (Secure DNS, DNSSEC, TLS 1.3, Encrypted SNI)
- Device Info (Web browser security/privacy testing)
- VPN & Torrent IP Leak Test (IP, DNS and WebRTC leaks)
- DNS leak test
- EFF Cover Your Track (Device fingerprinting)
- Evercookie (Persistent cookies)
- IP Leak (IP, DNS and WebRTC leaks)
- IP Leak privacy test (IP address, DNS, WebRTC...)
- Permission.site (To test the interaction of web APIs and browser permissions)
- TorZillaPrint (Advanced scripts for Firefox and Tor browsers • Test site, Mirror)
- Toolz (Ad Block Test • Test site)
- Webpage tracking only using CSS (and no JS)
Malware
Your antivirus has detected a malicious software in Chromium files.False positive?
You have downloaded Chromium from a reliable source (#notes) and maybe also used open-source #updaters. In this case, it is surely a false positive. The detection is generic (heuristic). There is absolutely no backdoor or other malware inside Chromium. Remember that the full #source-code is available. You will get a similar result if you compile Chromium yourself.Note a specific thing about Chromium browser:
- Chromium has no digital signature (unlike Google Chrome). It is not signed because is open source and not "owned" per se by any one particular developer or organization. Moreover, a certificate is not free for developers (Apple Developer Program).
- Antivirus use generic detection and database of malware signatures.
- VirusTotal which aggregates many antivirus is a Google service using its Trusted Source project to limit false positives for software like Google Chrome (because it is digitally signed), not for Chromium.
- So, unsigned Chromium + any antivirus or VirusTotal service = More chance to get an antivirus alert.
False positive reports known for few years ago:
- False positive - chromium 79 (2019 • Broadcom • Archive: 1)
- Chromium 32bit download has a virus? (2018 • Avast antivirus • Archive: 1)
- IDP.Generic reported for chromium executable (2018 • Avast antivirus • Archive: 1)
- False positive on Chromium executable (2016 • Avast antivirus • Archive: 1)
- False positive with Chromium (2015 • Panda Internet Security • Archive: 1)
- False Positive on latest Chromium Nightly? (2014 • Avast antivirus • Archive: 1)
- AntiVirus detected Malware while syncing using gclient (2014 • Chromium Issue Tracker • Archive: 1)
- pepflashplayer.dll tagged as malware and removed by F-Secure (2012 • Chromium Issue Tracker • Archive: 1)
- Kaspersky detects Chrome as Trojan (2010 • Chromium Issue Tracker • Archive: 1)
- Avast! Anti-Virus reports Google Chrome as Trojan (2008 • Chromium Issue Tracker • Archive: 1)
Authentic malware?
Yes. Obviously, it is also possible.- The common entry methods for Chromium virus are freeware downloads as bundled software (bundleware) and spam e-mails. It means Chromium has been silently installed via another software. Do not forget Chromium is free and open-source. So malware writers use Chromium to push malicious code on to your system. Remove this "fake" or suspicious Chromium web browser (like BeagleBrowser, BoBrowser, BrowserAir, Chedot, eFast Browser, Fusion Browser, Mustang Browser, MyBrowser, Olcinium Browser, Palikan, Qword Browser, Torch, Tortuga Browser...).
- The other way is about a compromised Chromium repository on a reliable source (#notes).
Free tools to scan your system
Anti-malware:- AdwCleaner and Malwarebytes (by Malwarebytes)
- Kaspersky Virus Removal Tool (by Kaspersky)
- Kaspersky Rescue Disk (by Kaspersky • Bootable ISO file)
- Emsisoft Emergency Kit (by Emsisoft)
- Norton Power Eraser (by Symantec)
Antivirus:
(Independent tests and distinctions: AV-Test, Virus Bulletin, AV-Comparatives, Gartner)
- Windows Defender (on Windows 10)
- Avast (Prefer the offline installer. Then choose the advanced installation)
- Kaspersky Security Cloud
- Bitdefender
- Avira
- ClamAV and Immunet (Open-source • Developed by Cisco)
Anti-ransomware:
Free online services to scan your files
(no registration required)- Jotti
- VirusTotal (by Google • Its lite version)
- MetaDefender (by OPSWAT)
- virSCAN
- Hybrid Analysis (by Payload Security)
If you find an issue:
- Contact your anti-virus or anti-malware support
- Report it on the official Chromium supports. For links, see my #comment-1 below.
Chromium updaters
To update Chromium automatically.As always, never install a closed-source software especially if you have never heard it before! GitHub and its Gist service are good places to find good stuff. So, try these free and open-source Chromium updaters:
Updaters on Windows
- For info, in the #windows section, each "Portable" version uses chrlauncher which can install, update and launch Chromium automatically. You can change its settings in the chrlauncher.ini file.
- chrlauncher
(by Henry++ • 2022 • C • Compatible with all Windows releases of this website) - Chocolatey
(by the Chocolatey team • 2023 • In command-line • Compatible with the Hibbiki's releases and The Chromium authors' releases of this website • Package core) - Scoop
(by the Scoop team • 2023 • In command-line • Compatible with the Hibbiki's releases and the Ungoogled releases of this website) - ungoogled-updater
(by NeverDecaf • 2023 • Python • Compatible with the Ungoogled releases of this website) - ChromiumForWindows
(by Ilyó Kovács Levente • 2022 • C# • Compatible with all Windows releases of this website) - Simple Chromium Updater (chrupd.cmd)
(by mkorthof • 2023 • Batchfile • Compatible with all Windows releases of this website) - ChromiumUpdathe (by Hristo Bogdanov • 2021 • C#)
- chromium for windows installer (by Lusito • 2020 • Javascript)
- cr-updater (by pwlin • 2018 • Batchfile, PHP)
- Chromium_Updater (by Programming4life • 2018 • Rust)
- ChrUpdWin.cmd (by Michael Kharitonov • 2018 • Batchfile)
- A web installer for Chromium (by LonelyCannibal • 2017 • AutoIt • Archive: ZIP)
- Chromium Downloader (by stsy • 2016 • C#)
Updaters on macOS
- Homebrew Tap for the Marmaduke Chromium builds
(by Charl P. Botha, then Matthew Salazar • 2023 • Ruby • Compatible with all Marmaduke releases of this website) - chromiumUpdater.js
(by TayIorRobinson • 2021 • NodeJS • Compatible with the stable Chromium version of Marmaduke) - chromium-updater-mac (by wangxufire • 2018 • Python)
- chromium-downloader-script (by Matteo Loporchio • 2017 • Shell)
- chromium-downloader (by Matteo Loporchio • 2017 • C)
- update_chromium_osx (by Klemens Gordon • 2016 • Shell)
- chromium-on-mac (by NicoLargo • 2015 • Shell)
Discontinued updaters
Chromium Update Notifications(by Christian Mund • 2022 • Compatible with all releases of this website • Archive: CRX)Chromium Auto Updater [Root](by Federico Dossena • 2019 • Java)Chromium Updater(by the FreeSMUG team • 2018 • Chrome Web Store • Archive: ZIPgetChromium(by Andrew Wright • 2018 • Java)Chromium Updater (crupdater)(by Muhammer Ayes aka Zychopat • 2016 • Batchfile, AutoIt)chromium-nightly-updater(by Vikrant Chaudhary • 2016 • Java)Chromium updater script for OS X(by Alan Grosskurth • 2016 • Shell)Chromium-Download-Manager(by xinhugo • 2015 • Batchfile)chromium-update(by William Alexander • 2015 • PowerShell)Chromium Upgrader for Mac OS X(by mozamimy • 2015 • Shell)Chromium Updater(by Daniel Huhn • 2014 • Javascript)Chromatic(by Mr Gecko • 2014 • App • Source code)extension.chromium-updater(by Jackson Tan aka Hallbin • 2014 • Javascript, CSS)Chromium-updater(by Das Schwert • 2010 • AutoIt)chromium updater.py(by Curt Micol aka asenchi • 2009 • Python)
Thanks a lot for all developers!
I do not support these tools. Please, contact the developers for thanks, issue, help...
10337 comments
Quick access: #read the latest commentNow, you can post anonymously remarks and suggestions about this site. Do not hesitate! ;)
Please, DO NOT report bugs by a review. Use the official issue tracker or dev topics:
• https://bugs.chromium.org/p/chromium/issues/list
• https://groups.google.com/a/chromium.org/g/chromium-discuss/about → Conversations
• https://groups.google.com/a/chromium.org/g/chromium-dev/about → Conversations
• https://groups.google.com/a/chromium.org/g/embedder-dev/about → Conversations
Also, I prefer direct links. You are not on Twitter ;)
I recommend reading the Chromium Code of Conduct.
https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md
Thank you for your attention!
@3: Thank you very much!
Google Chrome release: 64-bit support for Mac
https://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html
----------------------
[EDIT: 12 Sep 2014 by Jerry]
Google Chrome 64-bit for Mac and Windows
https://gsuiteupdates.googleblog.com/2014/09/google-chrome-64-bit-for-mac-and-windows.html
----------------------
[EDIT: 26 Aug 2014 by Jerry]
64 bits of awesome: 64-bit Windows Support, now in Stable! (Google Chrome)
https://blog.chromium.org/2014/08/64-bits-of-awesome-64-bit-windows_26.html
----------------------
[EDIT: 3 Jun 2014 by Jerry]
Try out the new 64-bit Windows Canary and Dev channels (Google Chrome)
https://blog.chromium.org/2014/06/try-out-new-64-bit-windows-canary-and.html
----------------------
[EDIT: 28 Feb 2014 by Jerry]
Yes @5! Thanks, it is a good idea! But... 64-bit Chromium on Windows and Mac are still experimental.
Officially, 64-bit Google Chrome on Windows and Mac do not exist too!
Check the development channels : https://www.chromium.org/getting-involved/dev-channel
Google team wrote:
"Neither Chromium nor V8 has a 64-bit version on the Windows platform right now. However, Chrome does run on 64-bit Windows as a 32-bit application. V8 should only need a small number of changes to build on the Windows platform."
https://www.chromium.org/developers/design-documents/64-bit-support (Content edited by the Google team in February 2014, but there is a copy at https://archive.is/mT07)
...here:
"The problem: Chrome runs as a 32-bit process on 64-bit Windows systems. [...] The plugins are still 32-bit libraries."
www.chromium.org/nativeclient/design-documents/native-client-in-chrome-on-64-bit-windows (Content deleted by the Google team in February 2014, but this issue talk about that: https://bugs.chromium.org/p/chromium/issues/detail?id=28176)
So, there will be many bugs with plugins (PepperFlash/Adobe Flash player) and extensions (from the Chrome Web Store) because plugins and extensions are mainly in 32-bit.
...and there:
On Windows... "The sandbox is designed for 32-bit processes"
https://chromium.googlesource.com/chromium/src/+/master/docs/design/sandbox.md
Officially, only Linux versions are available in 64-bit. The PepperFlash/Adobe Flash player for Linux exists in 64-bit.
About Windows... (revision 211418):
• 64-bit: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/211418/
• 32-bit: prefix=Win/211418/
In the Win_x64 repository, Chromium's executable is in 64-bit. But most internal processes are in 32-bit.
Work is underway. To follow progress of 64-bit Chromium:
• Windows: https://bugs.chromium.org/p/chromium/issues/detail?id=8606
• Mac OS X: detail?id=18323
• ARM64 (AArch64): detail?id=334368
• Android ARM64: detail?id=354405
• Android x86_64: detail?id=346626
----------------------
Why there is no 64-bit Google Chrome on Windows and Mac actually?
You know, I am not a specialist. The Google team works on 64-bit Chromium for Windows, Mac... since 2009 (Just check the links above!). I think that Google waits for the moment to offer its own browser (Google Chrome) in 64-bit. It will depend on its strategy with Chrome OS. When Google will need more than 4GB RAM for its products (Chrome OS especially), Google Chrome (and Chromium obviously) will go 64-bit with little debate. Note that a 64-bit version will lead to a significant increase in memory usage. Speed is improved, especially in graphics and multimedia content, where there is an average 25% improvement in performance.
If you have got a better idea, please tell me here! ;)
And... Google Chrome use this release, too.
You can compare your version with the Google's official releases on https://dev.chromium.org/developers/calendar
Check: os→mac, channel→stable, current_version→28.0.1500.71, branch_revision→209842.
Actually, you are using the stable version.
About your bookmarks, it is probably a bug! :/
Did you try to restore your bookmarks?
• https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md
• https://superuser.com/questions/190160/where-to-find-my-favorites-in-google-chrome
@10: Really? See my #comment-6 above.
Just a recommendation, you could build up a .BAT file which will update Chromium to the next stable release if it exists on this page.
Here's one that updates through the snapshot trunk(?)
Just like this one, give it a try to understand its behaviour: https://www.google.com/search?q=chromium+auto+updater (first 2 results are reliable, original website of it disappeared).
In this case it works as a Scheduled Task under Windows.
This recommendation is the only thing could make even better this project of yours.
Thank you a lot :)
Chromium download page at https://download-chromium.appspot.com/ reads "This is the raw build of Chromium for Windows, right off the trunk. It may be tremendously buggy. Consider Chrome Canary or Dev Channel for a build that regularly auto-updates to latest."
@13: I check your interesting solution. Thanks a lot.
@14: "good build" means that it is the less buggy version of Chromium. "Chrome Canary" and "Dev Channel" concern only Google Chrome (which is not open-source), not Chromium !
@17: Links from Continuous builds concern mainly Windows. And no, I do not know more stable version than this. :/ For other platforms like Mac and Linux, there are really stable builds done by external developers. These Chromium versions are the same as Google Chrome versions.
Officially, Google Chrome is the stable version. Read my #notes
I should note that the x64 builds are actually 64-bit. I checked Process Explorer and the Chrome executable was identified as 64-bit in that column.
Actually, do not use 64-bit Chromium on Windows. It can be less stable than the 32-bit version. But if you really want it, you can! I added 64-bit Chromium on Windows! ^^
Would it be possible to get an RSS feed of the latest Chromium stable release (sort of a simple update method)?
@24: Ok! Check my RSS feeds! ^^ Moreover, a simple #api is available too! ;)
Once a Firefox User, but with Mozilla's attempt to make a cheap Chrome clone I am glad for such a site like yours where I can find the actual stable version of the one and only valid original :D
Just to know, will you share ever (or never) your API/website code? Just to know, just to make scripts for Windows Chromium auto-updating or else ;)
@26: I will not offer a list of the best releases without bug. But, you can get the latest non buggy Chromium version from my other page: http://chromium.woolyss.com/download/ Hope you like it! ;)
@27: Sincerely, I have never done an extension for Chromium/Google Chrome. But sure, if someone does it, it will be nice!
@SaphirJD, Thank you very much for your feedback.
@29: Yes, I can get the best build for Android (.zip archive from Continuous repository) like others. But, I know nothing about the stable version. I need to check that. Good suggestion!
@Giovanni Santini, Code, no. My API is available for everybody. So, you can use it freely in your add-on script... but obviously not to create another website like mine. Note that my main website (woolyss.com) exists since 2007. Do not worry, this site will still exist in several years! ^^
For me, a good Chromium Updater add-on should offer:
- Download latest Snapshot build (may unstable) • by your own way
- Download latest Continuous "success" build (more stable) • via my API
- Download latest Continuous "non buggy" build (more and more stable) • via my API
Do you agree with me that this is a good idea? Rather than the latest Chromium, we have the Chromium which is the same as the current Chrome? (or as similar as possible)
Thanks so much for your work!
@GG: You wrote: "we should always be able to download Chromium "Y" instead."
You cannot. Google does not share the Chromium binaries equivalent to Chrome versions. The only way is to build your own Chromium version based on the same Google Chrome version. Check the #source-code and #notes for more.
Moreover, xx.x.xxxx.66 in this version means that 66 patches were made by Google developers (for Chrome browser). The shared Chromium binary has NOT got these patches. So on Windows, Chromium will be always less stable than Chrome for sure. In conclusion, I recommend to use the latest Chromium releases... or the stable Chromium releases built by developers (like on #linux and #mac).
If you are developer, you can re-build it. Good luck! ;)
https://chromium.googlesource.com/chromium/src/+/30.0.1599.66/DEPS
@34, Thanks for your feedback on WinXP x64. I have never tested. 64-bit Chromium on Windows is very experimental. Google does not use it. I encourage you to read my #comment-6 above. ;)
I find these random Chromium builds very unstable and buggy, so I must regretfully use IronPortable instead :(
Thank you for your work :)
How you can know if the build have no bugs?
• 32.0.1666.0 (227671): build.chromium.org/p/chromium.lkgr/builders/Win/builds/6734
• 32.0.1669.0 (228339): build.chromium.org/p/chromium.lkgr/builders/Win/builds/6761
These pages look identical. So how I can find out if there is any bug?
@GG: I think that Chromium should not be used in production if it is not stable. On Windows, it is always buggy! I try to offer the best builds on Windows. The Google team says: use them as your own risk!
About FreeSMUG, the main developer chooses the same Chromium version as Google Chrome version and re-build it. Check #notes to understand. He improves it, corrects few bugs, add its own updater... And, no sorry, I have never built Chromium. I prefer web development! ;)
@37: "Build successful" is not enough. Make sure that your revision has no bug. "BUG=none" does not mean "stable"! A stable version is a version tested by many humans and automated tests.
Example:
Latest build without bug: 32.0.1666.0 (227671)
https://src.chromium.org/viewvc/chrome?revision=227671&view=revision
Latest build: 32.0.1669.0 (228339)
https://src.chromium.org/viewvc/chrome?revision=228339&view=revision
@Bucur, I am not an expert! ;) I need only a good version of Chromium in my development environnement. So, I created this website for that.
How to automatically hide Chromium's download bar?
There is no option in Chromium. Use this excellent add-on:
https://chrome.google.com/webstore/detail/always-clear-downloads/cpbmgiffkljiglnpdbljhlenaikojapc
1) Why does the .exe version installs a slightly different fileset (or maybe the same fileset, but differently organized) than the .zip version?
2) Will the .exe version ever has the option to choose the destination folder?
Best regards
1) The .exe and .zip use significantly the same fileset. It is normal to have a difference because an .exe is a compiled version. And because all is open-source, the difference is not very important!
2) I think the Google team will not add an option to choose the destination folder in Chromium. Since then, Google Chrome has not got this option. :/
Check this Google official topic: https://productforums.google.com/forum/#!topic/chrome/R-wESj1EIk8
@MadHatter: I know this issue. I hope that you read my #comment-6 above. I repeat: For Windows, all internal processes in the 64-bit version are in 32-bit. So, it is normal to have conflicts. This is the choice of Google, not mine. :/ Do not use the 64-bit version in production. Use it only for test! Google does not use the 64-bit version to build its own browser (Google Chrome).
[EDIT: 18 Nov 2013 by Jerry]
Thanks in advance,
Willams.
@Willams Carvalho, I am really sorry but this site is not for development's bugs. So, I will delete your post. See my #comment-1 above.
Sincerely sorry Williams! I cannot handle your trouble. :/
Just one thing: The first line in your debug logs is very important: "org.openqa.selenium.WebDriverException: Could not find Chrome binary at...".
Error in your URI. ^^
Thank you very much for this great site!
I see you recently added a link to "Chromium Portable" project, I tested this version on Win XP and found it very unstable and buggy:
1) Every time I close v. 32.0.1700.6, it always crashes with the launcher popup message "Whoa! Chromium has crashed. Relaunch now?"
2) The browser uses the English language in the UI, even in Spanish Windows version
3) If I try to change the language to Spanish (or any other than English), it does not change when I restart the browser (the same happens in earlier versions of Chromium portable that doesn't crash on exit as 32.0.1700.6 does it)
4) An error about "missing Google API keys" is always shown at startup
I've tested other portable versions of Chromium such as:
a) Google Chrome (portableapps.com version)
b) Superbird (not 100% portable: it writes 2 'superbird' registry keys)
c) X-Chromium (winpenpack)
d) SrWare Iron
All those versions works fine, no one fails as chromium-portable.
I think a good option for those who needs a stable portable version is WinPenPack's:
https://sourceforge.net/projects/winpenpack/files/X-Chromium/releases/
It can be easily updated with Chromium zip builds you offer here
1) This is a new issue. :/ Chromium Portable (PortableApps.com) 31.0.1650.8 has not got this trouble.
2 and 3) Yes. Issues known: https://groups.google.com/forum/#!topic/crportable/hUU6b8LTdJo
4) This issue is known for few months now: https://groups.google.com/forum/#!topic/crportable/A6MDtGTJZO0 Too bad! :/
About X-Chromium (WinPenPack), I tested it on WinXP. It works very well and it is fully open-source. I like it! I will had it tomorrow on this website. Very thank you for your help.
Superbird browser is good but is not open-source! :/
@55, Did you resolve your problem? Which Chromium portable version do you use?
@mihau, Thanks. I try to maintain an interesting resource for users (like me! ^^). On Windows, I recommend to use Chromium as your secondary web browser because it can be unstable (Flash plugin issue or other). Otherwise, before to update it, do a copy of your user data (profile, bookmarks...).
https://github.com/gorhill/httpswitchboard
It blocks scripts/trackers... I am the author, so I obviously will appeared biased, but I did some objective detailed tests, and I dare to say it does better job and gives more control to users than other privacy-enhancing applications available on Chromium.
@gorhill, Very good news! Your extension is excellent and very powerful. I tested it. Now, your add-on is on the top of my list in #privacy section. ;) Thank you very much for your work.
Finally, after having tried everything I found the solution: go on YouTube, open a video and do the right mouse button: select "Settings" and then in the window that opens remove the check mark from "Hardware acceleration". With "Hardware acceleration" off...component "Shockwave Flash" of Chromium no longer crashes! Please....correct this bug!
About YouTube, you can use the HTML5 Video Player: https://www.youtube.com/html5 (No Flash required)
https://build.chromium.org/p/chromium.fyi/builders/ → Chromium Mac 10.8 x64 (experimental)
@66, Your link is wrong ;) Check https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/
I am running at Windows 8.1. Is it possible to change wallpaper in Windows 8 mode? If I good remember, this feature were available in Chrome OS. That grey color is strange for me :)
Have a nice day, regards!
@blogger templates: I do not know why it did not work for you :/ Retry with the last version!
@Raul: Sorry! Chromium 32.0.1700.107 corresponds to the revision 248368
• Google Chrome: https://googlechromereleases.blogspot.com/2014/02/stable-channel-update.html
• Chromium: https://src.chromium.org/viewvc/chrome?revision=248368&view=revision
Google deletes its Chromium packages when the same version of Google Chrome is released. Check yourself:
• Continuous repo: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/248368/ → Empty :/
• Snapshots repo: https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/248368/ → Empty :/
...but it is available. You must to re-build it.
• https://chromium.googlesource.com/chromium/src/+/32.0.1700.107/DEPS
• https://gsdview.appspot.com/chromium-browser-official/chromium-32.0.1700.107.tar.xz (169 MB)
Did you check the official help about wallpaper in Chrome OS?
https://support.google.com/chromebook/answer/1251809
...or this post of the Chromium Evangelist at Google?
https://plus.google.com/+FrancoisBeaufort/posts/ct35DeqXwoV
Check this issue too: https://bugs.chromium.org/p/chromium/issues/detail?id=334593 (Start Chrome in Metro mode)
BEX Indicates a buffer overflow (/GS) or DEP exception (BEX64 indicates a buffer overflow (/GS) or DEP exception on 64-bit versions of Windows).
Often no images are shown or they disappear after some seconds. This is on all websites.
Can someone reproduce it and create a bug report?
I have no Google-account and don't want one.
So I tried to install an older version, but it's still this buggy version. Now, Chromium even does not start...
@Jerry, What can I do to get a working browser?
I have all my bookmarks in Chromium and Firefox has lots of small things why I don't like it.
This is the second time I get a build here that is not usable. First was on Mac OS X 10.6.8
@82: Chromium is continually in development. And because it can be unstable, do not use it as your primary browser! Prefer a stable browser like Firefox, Opera, Google Chrome...
Never update Chromium with an #older-version Try to get your bookmarks. Check links in #comment-8 for help. And update Chromium browser or import your bookmarks in another browser like Opera. Good luck!
Note: This page is a blend of official resources about Chromium browser. I am absolutely not a developer of that browser. This page exists only to help you... and me!
If it works, I keep it, else I delete all data and restore working program.
C:\Users\xyz\AppData\Local\Chromium\User Data
C:\Users\xyz\AppData\Local\Chromium\Application
This seems to be the only possibility to have always a working browser.
One question/remark: Is there a specific need for all these "version-buildnumer.manifest" files or could we actually do without all but the last one?
https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm
Now I downloaded a recent mini_installer (35.0.1868.0), and found 87 .manifest files:
86 are [version].manifest and one mksnapshot.ia32.exe.assert.manifest
The zip package has 622 .manifest files with different names
Thank you. This website is useful.
@mauro: Thank you. Do not forget that Chromium on Windows can be unstable. Use it as your secondary browser.
For general interest, I have found a rather easy way to enable some excluded features:
1. PDF Reader and Print Preview - Copy the file 'pdf.dll' from an existing Chrome install directory to your Chromium install directory. The PDF reader will work without further config. To enable print preview simply add ' --enable-print-preview' to the end of your shortcut path.
2. PepperFlash - Copy the file 'pepflashplayer.dll' from an existing Chrome install directory to your Chromium install directory. To enable the plugin, simply add ' --ppapi-flash-path=pepflashplayer.dll' to the end of your shortcut path. You can also tell Chromium what version with ' --ppapi-flash-version=13.0.0.133'.
Hopefully this helps someone out there just as you have done for me Jerry ;)
Keep up with the great work and thank you once again!
@Haris: Please read my #comment-76 and #comment-18
I will be very interested to read and share your tutorial as well.
To add PepperFlash to X-Chromium Portable (WinPenPack):
1. Be sure X-Chromium is not running
2. Copy PepperFlash folder (with the 2 files pepflashplayer.dll & manifest.json) from a Google Chrome installation or portable version and paste it into X-Chromium's: X-Chromium\Bin\Chrome
3. Edit the file X-Chromium.ini (in same location as X-Chromium.exe), and modify it under [FileToRun] section like this...
[FileToRun]
PathToExe=$Bin$\$AppName$\$AppName$.exe
Parameters= --user-data-dir="%Profile%" --disk-cache-dir="$Cache$" --ppapi-flash-path=$Bin$\$AppName$\PepperFlash\pepflashplayer.dll --ppapi-flash-version=12.0.0.77
... and save changes.
As you see, I've added 2 command line switches:
--ppapi-flash-path=$Bin$\$AppName$\PepperFlash\pepflashplayer.dll --ppapi-flash-version=12.0.0.77
Previous is valid for pepper-flash v. 12.0.0.77
4. Run X-Chromium.exe, type chrome://plugins and select which flash plugin you want yo enable, ppapi (pepper-flash) or npapi (netscape type plugin)
Screenshots:
To add PDF viewer look the #comment-97
Remember you can keep X-Chromium up to day with Chromium zip packages, just unzip files under X-Chromium\Bin\Chrome and remove some useless files such as *.manifest, except [latestversion].manifest
@102: Did you test these add-ons to get the old New Tab Page?
• https://chrome.google.com/webstore/detail/new-tab-redirect/icpgjfneehieebagbmdbhnlpiopdcmna
• https://github.com/wjywbs/chrome-newtab-reloaded
Thank you very much for this site, it is extremely useful! If I want to build the "Chromium Portable (winPenPack build)" by myself, how can I do that? Do you have build instructions and/or build scripts available to share?
Thanks and regards, Fabian
Otherwise, build instructions are on https://www.chromium.org/developers/how-tos Good luck! ;)
@Shawn: It is surely a false positive. Please, read the #malware part.
@Shawn, I've experienced same problem as you with Chromium 35.0.1888.0.
While Chromium was running avast autoupdated to vps 140314-0 and after a warning, without asking confirmation, chrome.exe was deleted by avast, not quarantained because of a wrong default configuration.
Obviously, it was a false positive (it was fixed later with vps 140314-1)
@Jerry, I've quickly tested new Chromium Portable 35.0.1881.0, and it has same bugs and failures as previous old version (#comment-52) It also brings a new bug, because it creates and leaves three registry keys behind after first run
Regshot log:
----------------------------------
Keys added:3
----------------------------------
HKU\...\Software\Google
HKU\...\Software\Google\Chrome
HKU\...\Software\Google\Chrome\BLBeacon
As we know, a good portable app must delete any created registry keys and temp files on exit.
The author of this Chromium Portable, Aluísio Augusto Silva Gonçalves, says in the forum that he doesn't know how to fix the crash on exit problem.
A forum user gives a workaround: Close Chromium Portable with CTRL + SHIFT + Q
https://groups.google.com/forum/#!topic/crportable/SW3I-hzn1es
X-Chromium Portable (winPenPack) doesn't have this problem, the launcher deletes all registry keys and temp files created on exit.
@Marcelo.ar: BIG thanks. It is true! You are a master! ^^ I updated the #windows-64-bit-aluisioasg part.
Chromium Archive • chrome-win32.zip • Version: 35.0.1898.0 (257592)
And since you marked portableapps.com version as buggy, I don't want to use it at all!
I have installed Chromium Installer mini_installer.exe • Version: 35.0.1904.0 (258717) on Windows 7 (32-bit).
If I want to start Chromium with chrome.exe I get:
Name der fehlerhaften Anwendung: chrome.exe, Version: 35.0.1904.0, Zeitstempel: 0x532d4ad8
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x6ad1c989
ID des fehlerhaften Prozesses: 0xb24
Startzeit der fehlerhaften Anwendung: 0x01cf475a57e712f0
Pfad der fehlerhaften Anwendung: C:\Users\A\AppData\Local\Chromium\Application\chrome.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 964ee5c0-b34d-11e3-8489-000e7bb09a00
If I click the chrome.exe a second time Chromium starts.
So I have to click the button always to times. What is wrong? Please help.
So, it is probably a bug on Win7 (32-bit). I do not know. Retry with the newest version when it will be possible. If you do not want to wait, delete your current version and try with an older version.
What do you mean? Better take:
- Comodo Dragon (best speed on my PC, DNS Option, Referer Suppress without plugin) but, geez! Version 31.1!!
- or Superbird, only nearly latest Version? A "botched job"?
- or take a "too new one" like 35 (now)
For browsing and having buying transactions?
would be nice you send a short comment. thank you.
Can be unstable means the risk of crashes? or risks of vulnerable, security issues?
I was very happy to find your site because I tried several Chromium forks and thought getting something stable, (mostly) secure-safe with the "good build".
And, without wanting to spam you with stupid questions and steeling your time,
If I open this site: chrome://net-internals/#dns after 5 - to 10 seconds the site shows me:
dblzwbd UNSPECIFIED error: -105 (ERR_NAME_NOT_RESOLVED) 2014-03-27 16:33:33.206 [Expired]
fgvgglqpzigvhss UNSPECIFIED error: -105 (ERR_NAME_NOT_RESOLVED) 2014-03-27 16:33:33.207 [Expired]
sdswyxp UNSPECIFIED error: -105 (ERR_NAME_NOT_RESOLVED) 2014-03-27 16:33:33.206 [Expired]
My startpage is chrome://newtab
The letters a always different if I test the ...#dns site again.
Please, are you able to give me answer?
@Ben: Yes, Chromium can be unstable, like on #comment-7 and about your DNS issues, I have got the same results like you if I enable phishing and malware protection. To change it, check your privacy settings and uncheck the corresponding option.
If I search at https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/
(like comment "in resume": Continuous builds: Tested and more stable versions. Me, I prefer this repository for Windows and Mac. ^^)
for (257193), is this the same version like Google Chrome 33.0.1750.154?
I use http://chromium.woolyss.com/download/ for trying. Best choice, I think.
You wrote: "And about your DNS issues, I have got the same results like you if I enable phishing and malware protection. To change it, check your privacy settings and uncheck the corresponding option".
There is no different between enable/disable phishing and malware protection. I tried with/without addons, with HTTP Switchboard, incognito mode. Always these 3 results. Any idea?
HKU\...\Software\Google\Chrome
HKU\...\Software\Google\Chrome\BLBeacon"
I did not know that the Chromium engine still had Google in it and thought that Chrome added all the Google bit & bobs at an higher level
Thanks so much for providing these Windows builds for Chromium - I was getting very frustrated with Iron...... I have one small request if possible: you replied to Derek's #comment-90 above regarding H.264 support in Chromium and that it wasn't supported.
According to this post https://plus.google.com/u/0/+FrancoisBeaufort/posts/NHYa95SZphm and https://dev.chromium.org/audio-video it *is* now supported by Chromium. Is there any chance you could include this functionality in some future builds please?
Thank you so much Jerry and keep up the excellent work!
@Passing By, Behind its open-source side, Chromium is a Google project.
@Joe, I disagree with you. Chromium does not support MP3 and H.264.
"When building Google Chrome, the following codecs/containers are also included:
- MP3 audio codec
- AAC audio codec (Main only, not AAC-LC, AAC-SSR, HE-AAC)
- H.264 video codec
- MP4 container format"
Source: https://dev.chromium.org/audio-video
By default, Google Chrome has got these non-free codecs because Google pays the respective licenses for its own stable browser... but NOT for Chromium.
Unless I'm mistaken, and please correct me if I am wrong, Chromium uses the open-source FFMPEG code to implement H.264 support. Google may well pay license fees to include support for these codecs in their proprietary browser however the Chromium based FFMPEG source code is included in the open-source Chromium code (see https://src.chromium.org/viewvc/chrome/trunk/deps/third_party/ffmpeg/) which means H.264 and MP3 support *is* now possible. Also, the post by François Beaufort https://plus.google.com/u/0/+FrancoisBeaufort/posts/NHYa95SZphm, who works at Google, would suggest that it is possible also. See this post too https://plus.google.com/111991826926222544385/posts/VGWkJeH3Dsh
Why not give it a whirl? :)
Ok, I understood. You are right! ^^
Yes, I know that it is possible. All is possible! ;) Chromium forks (like Opera browser) do that... but you forgot the Google strategy!
- Chromium is the Google open-source web browser project → for developers.
- Google Chrome is the stable release → for all users.
In resume, yes it is possible! But the Google team (aka The Chromium Authors) decide all. Google prefers to curb Chromium browser and force users to use Google Chrome.
If you are developer (like François Beaufort ^^), you can build your own Chromium browser with MP3, H.264 codecs and other features. About me, sorry, I have no time to maintain and share modified Chromium versions.
Kind regards,
Very good news about Chromium Portable (PortableApps format)!
Two bugs (see #comment-52 and #comment-109) has been fixed since version 35.0.1916.27, April 10, 2014:
http://crportable.sourceforge.net/
1) The bug about registry keys leaved behind is fixed.
I reported this issue in the official forum
https://groups.google.com/forum/#!topic/crportable/j3Qj4Z-C2LM
I posted as "F.M." :)
2) The crash on exit issue is also fixed.
I've tried to report this in the forum since November 2013 but my message was never published (crportable mailing list is moderated). Anyway it was reported by other users.
3) I found a workaround for the "change language" issue:
After first run, close ChromiumPortable, make sure it is not running, and edit "ChromiumPortableSettings.ini" file (located at "<install-folder>\ChromiumPortable\Data\settings") and change the line "Language=en-US" to desired language and save it, for example, Spanish Latin America is 'Language=es-419' (you can find all language strings inside 'Locales' folder).
Now launch ChromiumPortable: browser should display UI in selected language.
Ok, I try with other words:
I don't want to test every "latest and best release" if HTTP Switchboard is running on it without probs or not.
Maybe there is somewhere to read about, if this addon is really ready for which version.
Sorry for my bad English.
Regards,
Thank you for your feedback. I understood your trouble but I can do nothing! Sorry. If you have issue with HTTP Switchboard, contact gorhill (Raymond Hill). He is the developer. Or use another add-on about #privacy
I developed an app that keeps Chromium automatically up to date. The app uses your API to get the latest builds. I published the code on GitHub, you can find it here:
sourceforge.net/projects/chromiumme/
ChromiumMe is made for Windows and Mac. Right now it runs only on Windows, because I haven't got the resources (yet) to test and compile it on a Mac OS. If anyone finds bugs, don't hesitate to report them to me on GitHub. Or better yet, send me a pull request! :)
Hope you like it. ;)
Chromium is also excellent! ;)
I'm sorry for the delay. I was on holiday the last weeks.
@and: My RSS feeds are valid. Check at https://validator.w3.org/feed/. So, I do not know how to improve them. Also, I tested them in add-ons: Slick RSS (on Chromium), Smart RSS (on Opera). All is ok.
@Ryu: On Windows you need to install a #flash plugin.
@HitomiTenshi: Nice work! I contact you in private. ;)
@Leo: You can use incognito mode by default. See #command-line-flags or like @philo said, use an add-on like Click&Clean.
Does anyone else have the same problem?
Anyway, thank you Jerry!
Thanks,
Ivan.
Anyway, thank you again and keep up the good work.
At first I was fairly comfortable that these were false positives, but it is starting to worry me that is it fairly consistent, in that in order to run the program I have to override NIS and undelete chrome.exe which as a general practice is not something one should do. FYI, I routinely scan my systems and they are clean and these Chrome builds are the ONLY ones that raise alerts, period.
@Ivan: I understand your issue but I do not use Win8+. Sorry!
@156: Check the #malware part. I tested on chrome-win32.zip (32-bit) • Version: 37.0.2023.0 (273845). All is ok.
Kind regards,
@160, Same question as @hariskar. But it is always possible to get an #older-version of Chromium.
Chromium - spyware?
@165: Chromium is not a spyware... and has no spyware. The full #source-code is freely available for anyone. However, this project uses services delivered by Google (like on Firefox, Opera or other browser). Protect your #privacy ;) You know, Chromium connects to Google server in order to update add-ons (cf. clients2.google.com). All web browsers do that. Personally, I prefer to use a VPN provider and keep few opened services.
@167: Waoooow, difficult in one line. I could write a long article ;)
I recommend VPN providers:
• using OpenVPN (free and open source software)
• near your country (speed is better, but this is relative!)
• offering offshore server locations (Netherlands, Panama, Costa Rica, Seychelles, Hong Kong, Switzerland...)
• professional and renowned (HideMyAss, IPVanish, PureVPN...). Good overview at http://www.bestvpnservice.com/ and https://www.privacytools.io/
• using IPv6 support (if your IPv6 address is enabled)
• using torrent support (if you use a client torrent like BitTorrent)
I forget the "No logging" mention because I cannot verify that myself.
• https://www.wipeyourdata.com/other-data-erasing/no-logs-earthvpn-user-arrested-after-police-finds-logs/
• https://freedomhacker.net/is-hide-my-ass-vpn-secure-in-2014/
About free VPN providers (like Hotspot Shield, CyberGhost, IAPS Intl-alliance, SpotFlux..), you are not protected on sites using a secure connection (https://) and/or if your IPv6 address is enabled. Moreover, all free VPN providers keep user logs.
What about https://freevpn.me/ and https://www.privatetunnel.com/?referral=OPENVPN ?
(ref: #comment-150)
https://portableappz.blogspot.com/search?q=google-chrome
On-line Installer downloads latest Chromium "mini_installer.exe", extract files, and creates a good Portable Chromium.
I quickly tested 32 bit version and it works fine; it cleans all registry keys on exit and doesn't give errors about missing keys or when moving portable to another location as http://crportable.sourceforge.net/ does.
@cyberrufus: I do not use 64-bit Chromium on Windows. Did you check the official help?
• https://forums.adobe.com/message/6337584#6337584
• https://helpx.adobe.com/shockwave/kb/shockwave-player-64-bit-windows.html
@172: Good news! I do not know if it will be permanent. ;)
@Marcelo.ar: Thanks a lot for your help but I cannot promote this version because it is a warez site. Read http://portableapps.com/node/15938 for a quick explanation.
It's only a debug version and only for Windows for now, but it does the job.
I'm running Chromium x64 on a Windows 8.1 system and got flash working by adding this to the shortcut: ' --ppapi-flash-path=C:\Windows\System32\Macromed\Flash\pepflashplayer64_14_0_0_126.dll --ppapi-flash-version=14.0.0.126'
Flash Player Beta: http://labs.adobe.com/downloads/flashplayer.html
@Marcelo.ar, Yes, it works! Sure, this is a Chromium modified version. But, where are the modified/full source code and the release notes? The link to download it is unofficial. Sorry Marcelo, all is too obscure for me. Use it at your own risk! ;)
@martin levy, There is no option to disable images in Google Chrome Android version. Did you test Opera Mini? It is based on Chromium like Google Chrome but it has got this option. https://www.opera.com/help/mini/other
@178, If you use a good VPN, your Internet Provider (ISP) cannot see what sort of traffic is inside the data stream.
@179, On Windows, I do not use updater. I prefer to update Chromium manually once or twice a month. For help, try an #updater
What is the difference between Git and non-Git versions of Chromium?
When I compare the LAST_CHANGE files, sometimes it is the same Git revision! But, I see that the directory without Git suffix is often updated.
• https://storage.googleapis.com/chromium-browser-snapshots/Mac/LAST_CHANGE
• https://storage.googleapis.com/chromium-browser-snapshots/MacGit/LAST_CHANGE
Ask to François at https://plus.google.com/+FrancoisBeaufort/
The Snapshots builds might be very unstable. I prefer the Continuous repository (which otherwise has only one directory for each OS version).
The last good revision is 279255, released in 24 June 2014. This is the official Buildbot result.
• https://storage.googleapis.com/chromium-browser-continuous/Win/LAST_CHANGE (32-bit Windows)
• continuous/Win_x64/LAST_CHANGE (64-bit Windows)
• continuous/index.html (All directories)
I do not know if this trouble is temporary, intentional or not? But, it is strange! Only Windows builds are concerned.
Otherwise, the Snapshots repository is always updated but there is nothing for 64-bit Windows .
• https://storage.googleapis.com/chromium-browser-snapshots/Win/LAST_CHANGE (32-bit Windows)
• snapshots/index.html (All directories)
• https://www.chromium.org/getting-involved/download-chromium (Download nightly builds)
Note that Google released the new 64-bit Windows Canary and Dev channels this month (3 June 2014).
https://blog.chromium.org/2014/06/try-out-new-64-bit-windows-canary-and.html
https://bugs.chromium.org/p/chromium/issues/detail?id=390771
@187: Now, all should be ok. Sorry for the inconvenience.
Regards
There's what's been going on with the x64 builds.
There's the last continuous build from July 3.
Version: 38.0.2081.0 (281129) / Thursday, 3 July 2014, has One Bug.
If you look at build.chromium.org/p/chromium.lkgr/builders/Win?numbuilds=200 you'll understand why there is no recent version with or without bug (lot of Failed compile)
@marc: Thank you.
About Windows, the Continuous repository is not updated because it is broken. This is due to the switch from SVN revision numbers to Git hashes.
https://bugs.chromium.org/p/chromium/issues/detail?id=384681
In chrome://plugins I have the system's Adobe Flash disabled but the PepperFlash one enabled.
--ppapi-flash-path=pepflashplayer.dll --ppapi-flash-version=14.0.0.145 are my launch arguments.
@Mike: Yes, it is correct! Thank you. I updated the #features part.
@obious: I have got also this issue on Win7 x64.
@Sérgio Marques: Good feedback! ;) For links, check the #malware part.
Info: FYI official builds has moved to Google storage hence the folder structure is different. It means that at the moment the #mac-64-bit-package is not updated (Source: https://bugs.chromium.org/p/chromium/issues/detail?id=384681#c14)
Here you have version: 37.0.1987.0 (Rev:269701) for Windows:
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/269701/
Try changing revision number in link until you find desired 37.0.x.0 version
@RazielCuts: Bad news! I do not use Win8+. Thank you for your feedback.
@Anon: Which OS do you use?
If you use 32-bit Windows, the revision 278951 (version 37.0.2063.0) is the last 37 version.
• Download here: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/278951/
• To get older revisions (version 37.x.xxxx.x), check the revision number between 269696 and 278951, in this repository.
@Mr: Marc, Thank you too! ;)
Well done. Keep it up. Thank you :)
Linux Ubuntu 14.04
https://bugs.chromium.org/p/chromium/issues/detail?id=384681
About Java on Chromium (and Google Chrome) on Linux:
http://news.softpedia.com/news/Java-Doesn-t-Work-on-Linux-Google-Chrome-35-Downgrade-Required-444127.shtml
@TheAslan, I tested today. It works perfectly on Chromium x86 (WinXP) and x64 (Win7). JavaScript must be enabled.
• Go to http://mycroftproject.com/
• Choose a search engine and type your wanted keyword (Example: https://i.imgur.com/UPAQJNa.png)
• In the address bar, type the search engine keyword (yt, in my example), press Space, type a search term, and press Enter.
It works!
@Tim, I added the #flash part.
@224, My RSS feeds are automatically updated and valid. Check at https://validator.w3.org/feed/ So, I do not know how to improve them. I use Slick RSS and all is updated. Please, tell me more about your RSS reader.
Another thing is that with every update there are two separate articles (one for the .exe and the other for the .zip). There should be only one per update with the two links in it, in my opinion.
For your information Pale Moon browser is available for Linux and is now available for Android. I use it on Linux. It is excellent. I will be trying it on Android later.
Thank you for this site. It is my 'must go to' for updating Chromium.
@John and @msz, I know this issue but I do not understand. Today, I made a RSS test file [EDIT: link deleted by Jerry] Test it in your RSS reader. Force to refresh the feed. And please, tell me if it works well for you.
In the #flash part you should mention that the version-flag is absolutely optional, and only needed if you want to see the correct version number on Chromium internal pages.
@cyberrufus, Where? I see only .exe and .dmg files about the PPAPI...debugger!!!
http://labs.adobe.com/downloads/flashplayer.html
@msz, Happy to see that! My other RSS feeds work like the test feed and should be updated correctly. Each RSS feed is cached during 5 minutes by the server. And about "each update version adds a new item", it is just an observation. Nothing important. All works normally ;)
So, I updated the #flash part. This site become very substantial and heavy. I do not know if I split it. Personally, I like the "all-in-one" concept and its easiest maintenance. What do you think?
As for the site I basically like it this way, and as long as it's fast enough you don't need to split it. The download/ link should be more emphasized (main place, a big icon maybe), though.
@msz: You know my RSS feeds are all valid and automatically updated. I tested with Slick RSS on Opera 23 (using Download Chrome Extension), on 32-bit Chromium, and natively on Firefox 31. All works correctly.
You probably use Smart RSS on Opera, don't you?
This issue is known by its developer: http://blog.martinkadlec.eu/post/501-smart-rss-final-v10
When you force to refresh my RSS feeds, they are not updated. :/
Today, I rewritten all my RSS feeds. Now, they use no server cache and different XML GUID.
Please, tell me if updates work in your RSS reader.
Regards,
Can you be more clear about builds on http://chromium.woolyss.com/download/? What are the difference between "best" and not "best"?
You haven't mentioned in privacy policy why do you need cookies and local storage.
@237: It is a legit question. ;)
1) SSL/TLS
Before all, using an SSL/TLS certificate with wildcard support is not free, for my wallet I mean. SSL/TLS is already bound to the cluster and my primary domain:
• https://www.ssllabs.com/ssltest/analyze.html?d=ssl10.ovh.net
• https://www.ssllabs.com/ssltest/analyze.html?d=woolyss.com
I am a simple user and do absolutely no profit. This site is a showcase website stored on a shared hosting service. The most important thing is about executable files. The site does not store any executable files. So, for privacy and security, it is better to download them from secure sites like Google repositories. For sure, it would be nice to use SSL/TLS on sub-domains too.
2) http://chromium.woolyss.com/download/
• This is a simple and short page for quick download. Same Chromium releases as here.
• "best" = continuous builds ; "not best" = snapshots builds. Check my #notes for more.
3) Cookies and local storage
Neither local nor session storage are used. JavaScript and cookie are only used by the comment form to avoid spambots. Without them, you cannot send your review.
https://stackoverflow.com/questions/5398604/local-storage-session-storage-web-storage-web-database-and-cookies-in-html5
Cookies:
• 60gp and 60gpBAK are delivered by my web service provider because this site is a sub-domain and use a specific cluster. These session cookies are used for load balancing: https://en.wikipedia.org/wiki/Load_balancing_(computing) I cannot delete them. :/
• vv00iu55 is the session cookie for the comment form.
So, if you use NoScript addon (or equivalent) and do not use cookie, the site is fully functional... but sending a new comment is not allowed.
2) Look at this Chromium updater for Windows: https://gist.github.com/mikhaelkh/12dec36d4a1c4136628b
@239, I added your #updater ;)
@TheAslan, This issue is known: https://bugs.chromium.org/p/chromium/issues/detail?id=401878
Chromium 38.0.2118.0 (288412) x64.
In version 37 and in Google Chrome there was not the problem.
(Sorry for my bad english)
Here are some screenshots:
This one is 271393 and everything is fine:
And this one is 290523 with the fully same settings:
Looks like the whole browser changed scale, but options suggest only web sites scaling. Totally same thing sadly happens with x64 (otherwise I'd switched to it already). Tried to turn DirectWrite off - the issue persists.
Could you please help me?
Unistall the following updates (August 2014) and the font issue should be resolved:
KB2970228, KB2975331, KB2975719, KB2982791
For further information consult your preferred search engine and search for the above KB's
Unfortunately these updates were not installed at my PC, but I've found out this bug
https://bugs.chromium.org/p/chromium/issues/detail?id=395425
which contains also a workaround for that: command line/shortcut options
--high-dpi-support=1 --force-device-scale-factor=1
fixed that and now I'm on 64-bit one! :)
Class not registered (I'm unable to launch Chromium via desktop icon on Windows 8, launching Chromium via explorer works).
I'm using portable Chromium x64.
• On Ubuntu (Linux), you need chromium-codecs-ffmpeg-extra.
• On Windows, I do not know. I tried to drag and drop ffmpegsumo.dll from Google Chrome to Chromium (32-bit versions), enabled "Disable hardware-accelerated video decode" in the chrome://flags page and tested few #command-line-flags but nothing works. H.264 is still not available on https://www.youtube.com/html5
@TheAslan: Which portable Chromium x64 do you use? Have you got the same issue with Chromium Installer or Package (ref. this page), 32-bit and 64-bit version?
https://chrome.google.com/webstore/detail/disable-youtube-html5-pla/enmofgaijnbjpblfljopnpdogpldapoc
PS: When I used Chromium Installer, it fixed Chromium launch problems.
I want to a little help community for http://chromium.woolyss.com/download/fr/
Bienvenue sur ce site mis à jour automatiquement. Il permet de télécharger la dernière et meilleure version depuis les dépôts officiels de Chromium. Plus d'informations (Anglais)
-> Bienvenue sur ce site [update]de mise[/update] à jour automatiquement. Il permet de télécharger la dernière et meilleure version depuis les dépôts officiels de Chromium. Plus d'informations (Anglais)
Version de Chromium utilisée dans ce navigateur: 39.X -> Version de Chromium utilisée [update]par[/update] ce navigateur: 39.X
More specific, you need to compile it with the flags described at https://www.chromium.org/audio-video#TOC-GYP-GN-Flags, which boils down to executing 'export GYP_DEFINES=" ffmpeg_branding=Chrome proprietary_codecs=1" ' followed by 'gclient sync' after you fetched the source code of Chromium but before you start building.
After you finished building it you need to navigate to chrome://flags and enable "disable-accelerated-video-decode", as if you don't some videos will keep loading forever.
Be aware that in some countries that implement software patents (like the USA), this could be violate patent laws see https://en.wikipedia.org/wiki/FFmpeg#Legal_aspects
@Jerry, It may be good to add this information to this site.
http://chromium.woolyss.com/f/7B4F40C0.txt
@Tharre: Very interesting too! But, you know, this solution is for developers. My page is very long. Sorry, I cannot add it.
@Chef: Nice work!
@267: This is not a Chromium issue because this problem exists on Google Chrome too. Verify your connection, your version... Good luck! https://forums.adobe.com/thread/704895 (started in 2010)
@Marc: Good news! I added it on #windows-64-bit
https://bugs.chromium.org/p/chromium/issues/detail?id=413535
I don't have any of those above bugs in version 39.0.2157.0.
Here's the article: http://www.omgchrome.com/run-android-apps-on-windows-mac-linux-archon/
Here is a screenshot of my Chromium setup running an android app:
https://bugs.chromium.org/p/chromium/issues/detail?id=415863
@StillBrilliant: Awesome! Thanks for this news... but this is not official. ;)
@Garik: Retry with a new version.
Especially thanks for linking to my Sourceforge project "Chromium Updater", but I've another suggestion for ya.
I'm also distributing portable version of Chromium for Windows platforms in a 2-in-1 package. Each major release you will find as new portable version, currently Version 40.
Have fun! :)
Download Chromium Portable:
https://sourceforge.net/projects/crupdater/files/Portable/
@284: I do not know if it is possible. Sorry! :/
So my request: You already have a "Reference" that shows the latest stable build, but if you could also include information for the latest beta/dev/canary builds (from the dev calendar), I think it would be really helpful in particular for Windows users. Additionally, maybe something that shows the last build with "bugs=none" would be nice (Although that might give a false impression of stability).
Regardless though, huge thanks for this site, it's very useful!
@288: Thank you too!
1) "...to find a "stable" version of Chromium for Windows. This clearly isn't possible"
There is a #stable-chromium-version on Windows. You need to compile it yourself.
2) About the Google Canary channel for Windows
Chromium version numbers consist of 4 parts: MAJOR.MINOR.BUILD.PATCH. The Google Canary build is based on the Chromium build (Continuous repository). Its version changes only when the BUILD number changes. Today, this number is 2194. After, it will be 2195, 2196... It does not mean that it is more stable than Chromium! ^^ It is only a development convention. Sometimes, the Canary build is patched too.
• https://www.chromium.org/developers/calendar
• https://www.chromium.org/developers/version-numbers
And about other Google dev/beta channels, you will not find the Chromium equivalent because the Google dev/beta builds are patched (cf. PATCH number). The Chromium builds are never patched.
3) "bugs=none"
You said that it might give a false impression of stability. I completely agree with you. I used it. But I removed it this year. Check [REMOVED] on the #news-for-this-site
Regards,
WOT uses ratings from users... and other sources like PhishTank.
• https://www.mywot.com/en/faq/website/rating-websites#userinput
• https://www.mywot.com/wiki/Trusted_Sources
Webutation uses different renowned tools.
• http://www.webutation.net/go/about
Tools used:
• Google Safe Browsing - https://en.wikipedia.org/wiki/Google_Safe_Browsing
• WOT - https://en.wikipedia.org/wiki/WOT_Services
• Norton Safe Web - https://en.wikipedia.org/wiki/Norton_Safe_Web
• PhishTank - https://en.wikipedia.org/wiki/PhishTank
• Links count of Wikipedia pages
The social media ratings are only there to "get an idea about the public opinion", not to improve the trust in the site.
If you know other add-ons like Webutation, please tell me! Trustwave SecureBrowsing is the best add-on I know but it is not updated for few years. Sometimes, I use the URL scan of VirusTotal: https://en.wikipedia.org/wiki/VirusTotal
https://bugs.chromium.org/p/chromium/issues/detail?id=418174
Look for the PPAPI download for Chromium.
In January 2011, Google pledged to drop H.264 support from Chrome, saying at the time in a blog post, "Though H.264 plays an important role in video, as our goal is to enable open innovation, support for the codec will be removed and our resources directed towards completely open codec technologies."
https://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html
The Chromium team has removed the H.264 support. But today, Google Chrome still supports H.264. Grrrrrr!
Excellent discussion about that on https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/5q-vejBTnTY
Anyway on YouTube, you can use the HTML5 version (https://www.youtube.com/html5) to watch videos in HD 1080p. But for sure, it is not as good as H.264 and MSE codecs... and it is only 30fps.
"%windir%\System32\Macromed\Flash\pepflashplayer64_VERSION.dll"
for the 64-bit version of the plugin and the same in SysWow64 for the 32-bit version.
Actually it seems that you must use the 64-bit version of the plugin when you use the 64-bit version of Chromium, else it might crash.
> @TheAslan: The problem is Google!
No, the problem isn't Google. The problem is that the h.264 codec is protected by software patents. And even though this is irrelevant in most countries, it's problematic for distributors like Google, as they either have to pay the fees or risk getting sued. Not distributing h.264 codecs with Chromium anymore (if it ever has been distributed with them) is a unfortunate, but quite reasonable decision.
> The Chromium team has removed the H.264 support.
Support for h.264 has never been removed, it's just not included in the distributed versions of Chromium anymore. As simple as setting a flag during compilation to enable it again (see my comment earlier for howto do this exactly).
Hope this clears up any confusion about this topic.
@Tharre: Thanks for your explanation.
Related to this, when you open https://chromium.woolyss.com/ the modern browsers report:
"The security certificate presented by this website was issued for a different website's address.
Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server."
Not sure if you're interested in listing it, but I spent some time today developing a Windows program in C# that can automatically fetch and install the latest good Chromium build. It sits in the system tray and fetches the revision, build, and HTTPS links directly from the Chromium repo (bypasses your site) and does away with the security implications of visiting a 3rd party site. I do not yet have a website set up for providing a download of it, however.
A potential idea I have for a future version of my software is to have it run through the tests on the build server to test for flakiness (how goofed up a build is) and allow end-users to set a metric (slider maybe) to determine what level of flakiness they're okay with. Then only download builds that pass this requirement.
Also, it'd be cool to present a window with a 5-star rating every time it grabs a new build to let the users vote on the previous build and how good they felt it was with an option to leave a comment. Then, provide users with a way to restrict their downloads to only files rated above a certain number of stars by the collective of users; e.g. I decide I'm okay with builds that are 4-star and up that have already had at least 50 votes. This would require a server with a database to store anonymous IDs and their votes. It would really help vet the quality of the latest builds for users who want a little more stability.
Of course, all those options would be optional. There are a lot of really cool things that could be done. Anyways, shoot me an email on your thoughts.
I created this simple page to easily download each Chromium release directly from the source. Please read my #notes for more.
My site exists only to help users. All is free, without ads and bad things. The links are direct and mainly in SSL/TLS (https://).
(Note that SourceForge and Adobe do not use secure connection on its sub-domains, like on woolyss.com. A wildcard SSL certificate is required: https://ssl.comodo.com/wildcard-ssl-certificates.php).
Moreover, you are not on Softonic, Cnet, Softpedia or other crap site with its fucking "Download Manager" and modified packages! ^^
If you prefer, you can use directly the:
• Buildbot waterfall
• Continuous repository
• Official download page (Snapshots repository)
Except the last one, my site uses these secure sources and show direct links. Nothing is hidden.
You are free to make an other site, an other software and develop marketing plan about Chromium. Google, Opera, Yandex, Comodo and other companies do that.
> I spent some time today developing a Windows program in C#
Good news! You know, I list other software like yours in the #updater part. I am "opened"! ;)
> It [..] fetches the revision, build, and HTTPS links directly from the Chromium repo
My site does it too. ^^
> [..] and does away with the security implications of visiting a 3rd party site.
Your software will be the same thing as my site. ^^ It will be a 3rd-party tool. The users must trust in it... and in your case, they need to download and install it.
Note a Chromium #updater exists and it is a clean tool. Muhammer Ayes, the developer, creates Chromium portable versions too. His software are free and open-source.
Good luck in your all projects!
Friendly,
https://bugs.chromium.org/p/chromium/issues/detail?id=439806
Sorry, the "useless download-manager" is not useless because it works for different OS, web browsers and NPAPI/PPAPI versions. ^^
Thanks maintaining this great site! Just what I was looking for. From now on it's goodbye to Chrome and hello to Chromium.
A tip for anyone who wants to install for all users on Windows: mini_installer.exe --system-level
This installs in C:\Program Files (x86). The 64-bit version goes there as well oddly enough, but it still is tidier than running software from the user profile imho.
Is there a way to link the revision number to the version number? I'm asking because I would like to run Chromium in the same version as the latest Chrome stable instead of the latest continuous.
@Pieter, Thank you for your interesting tip. ;)
> I would like to run Chromium in the same version as the latest Chrome stable.
Please, check my explanation on the #comment-305
Keep up the good work!
Thank you and greetings from Germany.
https://chromium.googlesource.com/chromium/src/+/master/docs/design/sandbox.md
When I use the NPAPI Flash Player in Chromium is this a safety disadvantage to Chrome's PepperFlash Plugin (both are on the same version level)?
Thank you again.
In Chromium:
• NPAPI is NOT sandboxed
• PPAPI is sandboxed (obviously! like in Google Chrome)
In Mozilla Firefox:
• NPAPI is sandboxed: https://blogs.adobe.com/security/2012/06/inside-flash-player-protected-mode-for-firefox.html
• PPAPI does not exist
More on the #flash part.
@branwerks: Thanks a lot. Sorry, I do not the way to disable them. I think it is not possible in Chromium/Google Chrome :/
https://productforums.google.com/forum/#!topic/chrome/CxJ1VkDSqxc
Official reason: "Chromium builds do not auto-update, and do not have symbols. This makes them most useful for checking whether a claimed fix actually works."
https://www.chromium.org/getting-involved/download-chromium
Google's branded Chrome browser can auto-update because it is built with additional specific info for the Google Chrome update servers which are maintained by Google. So, Google Chrome and other #stable-chromium-version have an auto-update system. For example, the FreeSMUG build (#mac-64-bit-freesmug) on Mac OS X has got it because the developer adds it on this build.
Finally, if you want an auto-update system, add yours in your own build... or use an #updater
Am I to understand that both flavours are required? Is that normal behaviour, or is there a mistake somewhere in the builds? It seems to beat the advantage of PPAPI as a more secure version of plugins, even if one disables plugins in FF and Safari, hence my surprise and my question.
Thanks in advance for your information, and thanks for the great job done here.
YAZ
Best regards (sorry for my English)
> Am I to understand that both flavours are required?
No. If the NPAPI plugin is installed, PepperFlash (PPAPI) will be the default plugin. In the chrome://plugins page, you can enable/disable each plugin. So, you needn't to uninstall the disabled plugin.
PPAPI is more secure. Please, check my #comment-327 too.
@acore, Hello! Sure, they are official. Please, read my #notes and #comment-312. For a simplest page, go to http://chromium.woolyss.com/download/ ;)
Yes, I read the #flash part and couldn't find an answer to my questions there, hence my message.
> No. If the NPAPI plugin is installed, PepperFlash (PPAPI) will be the default plugin
I understand that, and if you read my message, that's not the point of my question.
What you're saying is "if NPAPI is installed", which implies but doesn't state that one *must* install NPAPI, am I right (and that's really my main question, the rest if more information to you about my trials than anything else)? Thus my question is:
- is it normal/expected that Chromium can't seem to use the standalone PPAPI (this is from my actual experience, as in actually doing the installs/uninstalls and checking every time)…
… because it's kind of counterintuitive, and weird to me. And like I said, it means one has to disable Flash in FF and Safari (am I right?), and also from what you say, in Chromium for the NPAPI flavour.
Also since I've read your message I've tried deactivating NPAPI in Chrome; I went to chrome://plugins, and there… I couldn't find a trace of PPAPI, *only* the NPAPI version… And when I deactivate this one, Flash doesn't work at all anymore! And when I go to https://www.adobe.com/software/flash/about/, the version reported is 16.0.0.235, which is the NPAPI version number whereas the PPAPI version is 16.0.0.240 :(
FYI I've also tried with the Canary version of PPAPI.
I'm telling you, my head hurts…
You use Chromium on a 64-bit Mac OS X, isn't it?
By default, Chromium cannot read the Flash content (videos, games...).
So, you must install ONE Flash Player plugin. You have the choice: NPAPI or PPAPI.
- NPAPI is NOT sandboxed. It naturally works with Firefox and Safari too.
- PPAPI is sandboxed. It works ONLY with all Chromium-based browsers (Chromium, Chrome, Opera...)
- If you install NPAPI, you needn't to install PPAPI.
- If you install PPAPI, you needn't to install NPAPI.
- If you install both plugins, PPAPI will be the default plugin used.
Check the install on chrome://plugins and enable/disable what you want. See the screenshot:
If you don't see PPAPI, it means that it is not installed.
To see the Flash content on Firefox and Safari, NPAPI is required (obviously!). PPAPI doesn't work on these browsers.
> PPAPI version is 16.0.0.240
This is the Flash Player beta version downloaded from the Adobe Labs. Good! ^^
https://forums.adobe.com/thread/1655584
NPAPI version is 16.0.0.235. This is the Flash Player stable version. Good! ^^
https://www.adobe.com/software/flash/about/
@YAZombie: I know nothing about Mac, but in Windows you have to "point" Chrome(ium) to PPAPI flash via command line, the program has no way of knowing it exists (by default).
All the explanations below are for public interest. i'll send you a copy with screenshot so you can see for yourself. And yes, sorry, I saw your email, just read the beginning and thought it was just a mention of the answer here so didn't go further. My apologies.
> You use Chromium on a 64-bit Mac OS X, isn't it?
Yes, I do
> By default, Chromium cannot read the Flash content (videos, games...).
Perfectly understood, that's why I'm trying to install it. To make things clearer here, I'd say i'm an advanced user - not more than that (no specialist, no developper), but no less than that either ;)
> So, you must install ONE Flash Player plugin. You have the choice: NPAPI or PPAPI.
> - NPAPI is NOT sandboxed. It naturally works with Firefox and Safari too.
> - PPAPI is sandboxed. It works ONLY with all Chromium-based browsers (Chromium, Chrome, Opera...)
Perfectly understood the basic technological differences, how one works on Blink-powered browser vs the rest, no problem here.
Except… I tried it, and no, it just doesn't work that way. Explanations below.
> - If you install PPAPI, you needn't install NPAPI.
No. I tried. It just doesn't work that way. If you install only PPAPI, Chromium doesn't see it. Plain and simple, it doesn't.
> - If you install NPAPI, you needn't to install PPAPI.
Clear here, as I found out "by accident" when Flash (I ONLY had PPAPI at the time) asked for an update and installed (without asking me…) NPAPI.
> - If you install both plugins, PPAPI will be the default plugin used.
Hum, that's where it gets tricky. Like I said, there's no mention of PPAPI in chrome://plugins (no, not even in the detailed view).
> Check the install on chrome://plugins and enable/disable what you want. See the screenshot:
Nope, don't see PPAPI there. I'll send you screenshot, you'll see for yourself.
> If you don't see PPAPI, it means that it is not installed.
And yet, System Preferences > Flash Player mentions versions 16.0.0.235 of NPAPI and 16.0.0.240 of PPAPI (you'll see screenshots here too).
> To see the Flash content on Firefox and Safari, NPAPI is required (obviously!). PPAPI doesn't work on these browsers.
Sure. I'd rather disable it there, which I did.
Is it clearer now? See why I'm scratching my head? :-D
Is it possible versions 16 of the Flash Player are playing tricks that didn't previously exist?
Can't wait to see what you think of this!
Best,
YAZ
https://bugs.chromium.org/p/chromium/issues/detail?id=443706
So, let's assume you have Chromium in the Application folder (it's "normal" location), and you've installed the PPAPI plugin, you must launch Chromium with this command in the Terminal:
/Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=16.0.0.235
You can copy this command in an Alfred workflow to make it simpler, but it will open the Terminal, which is annoying imo.
You can also make a small script in Script Editor.
In Script Editor copy/paste the following command
do shell script "/Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=16.0.0.235 &
killall ChromiumLauncher.app"
then save this script as an application with the name ChromiumLauncher (otherwise it won't work). You can now use this script to launch Chromium with PPAPI. There's an annoying issue, which is that errors are reported when closing Chromium, if anyone has an idea how to disable this, they're welcome to explain.
Hope that clears this issue for others. Though this is obviously not normal behaviour since plugins have a very narrow list of install locations on the Mac (four, if I'm not mistaken), and there must be something off in the build scripts. I expect this will be corrected in the future (it's more or less a question, I haven't understood who builds this binaries actually!).
Thanks again to Jerry and _M_ for your help.
Without this great site, Jerry, I would have abandoned Chromium a long time ago as there's no other Chromium resource on the web.
Oh, and one more tip as far as when you can/should update Chromium; check this page every so often for the security update announcements - as you all know, Google Chrome is the offspring of Chromium, so... https://googlechromereleases.blogspot.com/search/label/Stable+updates
I forgot to talk about #command-line-flags Excuse me! So I updated the #flash part with the helpful link of the YAZombie comment. Check the step 3. ;)
I have some kind of a weird issue regarding YouTube's videos. Most of the time they aren't recognized correctly. I can only see them in 360p quality, even when they are in 1080p.
I'm using Opera to look at them with a "stable" browser, Chromium is 64-bit with PPAPI Flash (64-bit too, of course)
I've tried to update this morning (41.0.2262.0) but still the same issue.
ps: Not every videos have this issue, but most of them witch is kind of annoying.
Don't be fooled by thinking it is *better* because it is x64. My 2¢.
https://helpx.adobe.com/flash-player/kb/flash-player-google-chrome.html
It's included, too and is in the same directory, it's just called "NPSWF$ARCH_$version.dll". On my system it's version v15.0.0.246, whereas the would-be integrated one is already v16.0.0.235.
Just wanted to tell you that.
@tournier: Did you test the PepperFlash 32-bit version?
Video test: https://www.youtube.com/watch?v=6v2L2UGZJAM It works in 1080p with the 32-bit PepperFlash and the HTML5 version.
@LeonardK: I agree with you. But you talk about the NPAPI plugin (cf. "NPSWF$ARCH_$version.dll"). ^^
My site explains how to install the PPAPI plugin (PepperFlash), not the NPAPI plugin.
• NPAPI: https://get.adobe.com/flashplayer/ → NPSWF***.dll
• PPAPI: #flash → pepflashplayer***.dll
When the 2 Flash plugins are installed:
https://sourceforge.net/projects/crupdater/
/Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=16.0.0.235 > /dev/null 2>&1 &
Thanks for your post. Actually since then I've indeed found that solution somewhere (couldn't tell where, don't remember). Except it seems you can drop the " > /dev/null 2>&1 &" and just write:
/Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=16.0.0.235&
In the end I stuck with an Alfred workflow, which I find more handy since I used Alfred so much I could almost say it's a 50% replacement to the Finder :)
Thanks again for the hint.
Cheers.
YAZ
Mozilla added OpenH264 plugin (https://en.wikipedia.org/wiki/OpenH264) in Firefox 33 to support the H.264 videos in HTML5.
On Chromium, I did not find anything like that. :/
Actually, I do not know the way to play H.264 in HTML5... but you can use the #flash player.
For H.264 online testers, check the #html5-audio-video part.
--disk-cache-size didn't work properly.
Did you read this excellent ghacks' article?
http://www.ghacks.net/2010/10/19/how-to-change-google-chromes-cache-location-and-size/
For info, there is also --media-cache-size to force the maximum disk space to be used by the media cache, in bytes.
Moreover, you can use the --incognito mode to clean automatically the cache on closing Chromium. Few add-ons like Click&Clean do that too.
Old thread deleted by Google... but archived:
https://web.archive.org/web/20120215211642/www.google.com/support/forum/p/Chrome/thread?tid=098d42a41aacdc6d&hl=en
Thanks, finally I can use Chromium browser. I used Comodo Dragon before.
Many thanks
Did you test to install a theme on a portable 64-bit version?
Yes (windows 7 64-bit). I always use only portable versions (SRWare Iron and Comodo Dragon's portable versions work fine with themes).
Thanks
> ...corresponds to releases from the Chrome stable channel?
Yes, it is possible. Check the #stable-chromium-version section. Also read my #comment-305 (because this is a recurring question ^^).
> ...treated as equally critical as a 0-day in a stable channel release?
Honestly, I do not know. Ask to François Beaufort at https://plus.google.com/+FrancoisBeaufort/
I see your issue is known:
• https://bugs.chromium.org/p/chromium/issues/detail?id=432802 (Since Nov 2014)
• detail?id=450604 (Since Jan 2015)
• detail?id=451056 (Since Jan 2015)
1) Make sure your Flash plugin is enabled: chrome://plugins
2) If PPAPI, do not forget the command line flags ( --ppapi-flash-path)
3) If NPAPI, nothing to do! If it works in other web browsers, it will works in Chromium
To force Flash on YouTube, install "Disable Youtube™ HTML5 Player":
https://chrome.google.com/webstore/detail/disable-youtube-html5-pla/enmofgaijnbjpblfljopnpdogpldapoc
> extremely irritating having to switch between browsers
Yes I agree.
• On Windows, I recommend to have 2 web #browsers because actually there is no #stable-chromium-version. It is important for your data to use a STABLE browser like Firefox, Opera, Google Chrome... Also note that you can build your own stable version.
• On Mac, Linux and BSD distros, there is a stable version! ^^
The plugin is installed, BUT it doesn't show in the plugins pages on Chromium o_O
:(
Thx
Did Flash work before? Is this your first time using Chromium? Did you write a proper command line for Flash player? We need more info.
@Psygno: Finally, this is a not a bug but a new feature. NPAPI plugins are disabled by default.
Enable the option on chrome://flags/#enable-npapi
More about NPAPI plugins: https://www.chromium.org/developers/npapi-deprecation
Just one question: is there any way in Chromium to change the user agent from mobile to desktop? In Chrome it is possible by flagging one setting, but I don't know it does and how to apply it on Chromium too. Any suggestion will be appreciated ;)
1) with an add-on:
http://www.techgainer.com/change-android-chrome-user-agent-string-to-another-browser-or-os/ (Archive: https://archive.is/lFM8G)
2) with a flag:
• Check https://www.chromium.org/developers/how-tos/run-chromium-with-flags
• Choose a flag: --user-agent or --use-mobile-user-agent
• Remember to quit the app completely and restart for flags to take effect.
Example: --user-agent="Mozilla/5.0 (Windows NT 6.3; rv:36.0) Gecko/20100101 Firefox/36.0"
I'm not so practical with adb commands ;)
In chrome://version I found --use-mobile-user-agent 3 times. How can I change/delete all of them?
I just have to type: adb shell 'echo "chrome < --user-agent="Mozilla/5.0 (Linux; Android 4.4.4;) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2289.0 Safari/537.36">" > /data/local/tmp/android-webview-command-line' ?
• Method 1 (with an add-on): "Chrome User Agent" or "Chrome User Agent Switcher" recognize just Chrome's installation, so their changes will not affect Chromium.
• Method 2 (with a flag): to try when I will be more confident with adb ;)
Thanks again Jerry!
Please see this video https://www.youtube.com/watch?v=cwgo1Naf0Zg and its relative topic https://archive.is/llFSU
For info, method 1 should work because Google Chrome and Chomium have the same user-agent and similar UI.
but unfortunately not for Chromium (ChromeShell):
@Djobi: It is boring! :/ Big thanks for your screenshots.
But I still think it is possible on Chromium. Rrrrr! You are near perfection! x_x
I'm experiencing scrollbars absence at 313437 (x64). They do present in chrome://settings, but are absent at any other pages, so I cannot understand how long the page is and where I am. Could anyone please check and/or share any workaround?
After a browser update, it should be ok!
I downloaded the Chromium 64-bit package for my Windows 7, unzipped it and it's working well but there are no java plugins. Any ideas how do I solve this?
Thank you in advance
1 - make sure you installed the 64-bit Java-Version, to be found somewhere on the java.com website.
2 - Chromium is gradually phasing-out support for NPAPI-Plugins. If you still want to use plugins based on NPAPI (such as Java), you need to enable it manually. Type in address bar chrome://flags, search for "enable NPAPI", enable it. Greetings
1) Download the good Java version on https://www.java.com/en/download/manual.jsp (Prefer offline installer!)
2) By default, all NPAPI plugins are disabled. So enable the option on chrome://flags/#enable-npapi
Actually, there is no PPAPI version of Java plugin. In 2015, if Oracle does not release a PPAPI version, I recommend on Windows to install the "IE Tab" extension which works always with NPAPI plugins:
• https://en.wikipedia.org/wiki/IE_Tab
• https://chrome.google.com/webstore/detail/ie-tab/hehijbfgiekmjfkfjpbkbammjbdenadd
... or use another browser supporting NPAPI plugins. For example, Firefox has not so far announced any plans to completely remove support for NPAPI plugins.
Because this is the end of NPAPI plugins:
• https://www.chromium.org/developers/npapi-deprecation
• https://www.firebreath.org/display/documentation/FireBreath+2.0:+Browser+Plugins+in+a+post-NPAPI+world
Just copying the new .dll works and enables me to decode mp3. But still on https://www.youtube.com/html5 it said that neither h.264 nor h.264+MSE would work.
Using the self-made extension atleast made a tick in the h.264 box whilst h.264+MSE didn't work, though MSE+VP9 does. Maybe that's because of DRM? There are also to other .dll's "missing": libpeerconnection (probably WebRTC, I guess) and widevinecdmadapter, which is a DRM module. Just copying it into the folder of Chromium didn't work, there's probably more work to do :/
Do you have any ideas?
This script use Woolyss API to find good Chromium build, Adobe servers to discover latest Flash version, Chrome Canary builds to obtain fresh PepperFlash and can update itself too.
Feel free to try it from https://github.com/JustOff/cpf-update-win
@JustOff: Waoooow! Give me few days to test your nice work! Thanks for sharing! ;)
@greg: Cheers!
What I additionally noticed is that when font hinting is disabled in the Windows performance options Chrome will still force hinting, while Chromium won't. I actually would like to have font-hinting application based, that is: On Chromium (almost) only. Do you know how that works?
• chrome://flags/#disable-direct-write
• #command-line-flags: --disable-direct-write --disable-directwrite-for-ui --enable-font-antialiasing
@Gerry: Please, show me a screenshot of your chrome://plugins page. Also see my #comment-371
In both systems some YouTube Videos just play in 360p others in 1080p. With Chrome its just fine. https://www.youtube.com/html5 makes a red cross at "MSE + H.264" all other crosses are green.
Someone got the same problem or an idea to fix this? Even some MP4/H.264 Videos on Websites don't work (example: http://www.quirksmode.org/html5/tests/video.html first video isn't working)
I'm on Windows 8.1 64-bit, however, the mini installer doesn't work (neither as admin nor normal)
No desktop icon, no process in the task manager.
Anyone uses Flickr? Flickr doesn't load properly with Chromium 42 on me, same report with some people using Chrome 40. Strangely, not all Chrome users got this problem. I don't know why. Flickr loads normally with Firefox/Waterfox.
Thanks
314621 doesn't work, everything keeps crashing, I can't even open chrome://crashes (irony)
Can I at least downgrade and have something to browse with?
Yes, 42.0.2296.0 (314621) is very buggy. I updated the site.
Tested: 32-bit Chromium on WinXP (32-bit) and Win7 (64-bit)
If you have installed this buggy version:
• Choose an #older-version from the Continuous repo.
• Choose a newer version from the Snapshots repo: https://www.chromium.org/getting-involved/download-chromium (can be unstable!)
• Prefer ZIP package than installer.
• Choose temporarily another version/browser.
chrome://plugins NEVER displays the last Adobe Flash Player 17.0.0.93 PPAPI however installed on the PC.
So, how to activate flashplayer? At the moment any internet video can be played!
With IE11 absolutely none problem!
I've made the screenshots from my workplace 5 minutes ago, both after browser cold start. The results speaks for themselves, isn't it? Also, try to Google Search for "chrome 64 bit plugin compatibility" and don't be surprised - even Google Voice and Google Earth besides many other plugins are not supported in 64-bit Chrome. Of course we can discuss the theoretical advantages of 64-bit for speed and security, but in real life you will hardly notice the difference.
I want to find a answer with MP3 issue.
If I install Flash without problem (#flash), MP3 doesn't work.
I copy ffmpegsumo.dll from Chrome Canary 42.0.2298 (64-bit) to Chromium 42.0.2295 (64-bit).
https://hpr.dogphilosophy.net/test/ says "Does Not Support" but it can play MP3 on this only website and doesn't work on https://podcloud.fr/ and others places .
Same issue with and without mp3 extension.
That aside, my computer is good enough to handle whatever 2~8GB RAM browsers are eating nowadays, so 64-bit awesomeness can come at me anytime, no matter the cost.
By the way, I've been using the "buggy" 42.0.2296.0 (314621) version and I still haven't seen it crash or steal my bike. That said, 42.0.2293.0 (314050) crashes right away when I try to access the History page.
And: Modern PCs can handle that amount of RAM being used. And afaik Chromium just takes much memory when there's much memory available, ie. when you're running short, Chromium will try not to allocate so much - but if you have plenty: Why don't use it? I even put my browser cache into the RAM... .
And yes, 64bit on browsers can make sense as Chromium isn't just used as a browser but also for games etc. Then 64bit can be really nice. Additionally:
There are still programs that wouldn't *need* 32bit, which would completely run on 16bit as well. But: This ain't supported anymore. What I mean is, you really might want to go 64bit know, when you have time to do so.
Flash seems to be working for everything now, except 'The Daily Mail' online!
When I try to view a video, I get a black-screen (Right-click reveals "Movie not loaded" message) (Flash version...16,0,0,305)
Have I missed something? Could the videos on their website be incompatible somehow?
Please forgive me, but the vids' work ok on Chrome....
Thanks in advance man!
Johnicus
Does any of you have a workaround to make Netflix working on Chromium (Win7 64bits, Chromium 42.0.2303 32bits)?
As of right now i've tried several workaround found on internet but none of them worked, and a lot of the remaining ones are for Linux..
Right now the only way i can watch netflix is by using either Firefox or Chrome.
I have tried to reinstall Java, Silverlight, import silverlight's DLL into Chromium (no success, maybe because of my way to do it).
If any of you have an ideas, that'd be great.
Thanks.
Java have been a source of issues for some people with the usage of silverlight from what i've found, and it cost nothing to try so i tried ^^
Hope that ppl will stop using crappy silverlight, even MS did so (and they invented it...).
Sorry for delay but after 2 days of development I present to you a new page to test #html5-audio-video elements.
https://tools.woolyss.com/html5-audio-video-tester/
Hope it will be helpful ^^
@Johnicus: > When I try to view a video, I get a black-screen
Me too. It does not work! :/
But the MP4 file works perfectly in HTML5 on 32-bit Chromium. (It works only if you have changed the ffmpegsumo.dll file):
https://tools.woolyss.com/html5-audio-video-tester/?u=video.dailymail.co.uk/video/1418450360/2015/02/1418450360_4056782948001_nerdist--1424015378606.mp4
@tournier, _M_, LeonardK, Rrrrrrr! Plugins!
Did you check my #comment-388?
@_M_ and LeonardK, Not yet but soon! ;)
https://www.chromium.org/developers/npapi-deprecation
> Not yet but soon! ;) v42.0.2286.0 Chromium no longer accepts NPAPI flash player. Only PPAPI plug-ins:
I discovered the main issue about HTML audio/video elements is bad MIME on websites.
@_M_, I disagree with you. ;) Tested: Chromium on 32-bit WinXP (in Oracle VirtualBox on Zorin OS):
NPAPI works! ^^
Do not forget to enable #npapi plugins.
Running the latest version of Chromium x64 version offered on this page at the time of writing. And naturally, got the .dll from x64 version of Chrome Canary.
Also, when I go to youtube.com/html5, I see red exclamation marks on H.264 and MSE + H.264.
When I use the unpacked extension method, only the H.264 has a blue check mark, but not MSE + H.264. Even when I have the example extension enabled, I get the same problem on the video test page.
When testing with Chrome Canary, everything works fine and the YT html5 page shows blue exclamation marks on every option.
Please advice.
The entire point of using Chromium is to avoid the Spyware browser Google Chrome.
What am I missing? Someone please enlighten me, I'm confused.
In any case, if you downloaded the archive from the Google repository it's perfectly safe.
I followed the instructions above regarding installing the PepperFlash plug-in to the letter, added the command line to the shortcut, and flash still won't work.
When I open chrome://flash in the browser, it sees the plug-in. When I go to chrome://plugins, the flash plug-in is now there, and it's enabled.
However, when I try to play any flash content, all I see is a puzzle piece, and a grey error message with a puzzle piece that says: "Couldn't load plug-in"
I simply cannot figure this out. No amount of re-installing, re-starting, or re-tooling has helped. Google seems to only offer solutions for ubuntu and linux...no windows solutions to be found.
I do not want to switch to Google Chrome. There has to be some solution out there for this...I'm not an expert, but I'm not a noob either. Self-taught. Any help is greatly appreciated.
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/317493/
This version with the suffix 11.0 had the same version number as the latest Chrome Canary build, so I attempted to switch out ffmpegsumo.dll from Chrome Canary, and guess what? IT DID NOT WORK. Would you please stop assuming that switching out the dlls work? Obviously Google doesn't want people to use Chromium, and would rather have them use chrome, so considering the reputation of the company, they're obviously smart enough to ensure that simply switching out dlls would not work, and guess what, it does not. The only way this situation will be fixed is if someone literally builds Chromium with H.264 support, etc. on windows.
I have another machine which has a different version of both Chromium and Flash working seamlessly. So, the only way I got it to work, was to install that combination on this machine, Chromium 41.0.2227.0 Dev build, and Flash 16.0.0.235.
This works without issue. Problem now is that firefox doesn't like that version of Flash, and keeps trying to update it. I use FF as well, but mainly for work stuff.
@Justoff: I'll give that a try, thank you. The flash was definitely the 64-bit version, although I tested the 32-bit as well just to see if I could make it work. But, of course, it didn't.
I love Chromium as a browser, and cringe at the thought of installing Google Chrome or any other bloated version just for the sake of continuity. Even if it means taking a few extra steps listed above.
But over the years I can't think of another program causing more issues or headaches for me than Flash.
I use Flash player beta http://labs.adobe.com/downloads/flashplayer.html and it works flawlessly. Can you post your complete Chromium target shortcut command line? I have found that when I started using Chromium the Flash player problems were always linked to an incorrect command line.
Second you are using the Adobe Flash Player. Spyware #2.
If you want privacy, install Slackware or Gentoo with hardened Linux-Kernel (or even FreeBSD or similar...). Only communicate via PGP and use completely OpenSource products. No proprietary firmware or drivers.
This will do much more than just using Chromium instead of Chrome.
@mihau: Done! ^^
Your OS (Windows or Mac) and architecture (64-bit or 32-bit) is dynamically highlighted if detected.
I also tested your Otter Updater. Nice shell scripts! ;)
@Nyx and Pörö:
Tested with Chromium 43.0.2320.0 (318624):
• WinXP (32-bit) + Chromium + PepperFlash + ffmpegsumo.dll
→ Flash and video H.264/MP4 work well if all is in 32-bit version.
• Win7 (64-bit) + Chromium + PepperFlash + ffmpegsumo.dll
→ Flash and video H.264/MP4 work well if all is in 64-bit version.
→ Flash and video H.264/MP4 work well if all is in 32-bit version on this 64-bit OS.
• WinVista and Win8 & 8.1
→ Sorry, I do not use these OS. Few testers tell me that it works like on Win7
If there is a video issue, disable hardware acceleration (Check #browser-crash)
I can fix the problem by deleting the registry value:
[HKEY_CLASSES_ROOT\ChromiumHTM.<<A_LONG_STRING>>\shell\open\command\]
"DelegateExecute"="{<<ANOTHER_LONG_STRING>>}"
Why does this keep happening? And is there a more permanent fix?
@twiz: Thanks for your feedback but I do not see how to fix this :/
https://bugs.chromium.org/p/chromium/issues/detail?id=133688&q=TeamSpeak
@446: Did you check official packages? ^^
https://packages.ubuntu.com/search?keywords=chromium-browser (Ubuntu, Linux Mint, elementary OS...)
https://packages.debian.org/search?keywords=chromium-l10n (Debian, Linux Mint...)
@Nyx: I edited my previous post. All works perfectly with .exe and .zip Chromium versions. I extract libraries (ffmpegsumo.dll and PepperFlash) from Canary in general... but for PPAPI it also works with Adobe's Flash installers!
• If 32-bit Chromium used, get all libraries in 32-bit version, even If your OS is in 64-bit.
• If 64-bit Chromium used, get all libraries in 64-bit version.
Note 32-bit version of libraries is more stable than 64-bit.
Since yesterday Chromium (Profiles) are broken. The message "Chromium didn't shutdown correctly.." appears - even if I establish a new profile. What has happened?
@Uwe Mueller: What OS and version do you use?
Please read last posts on https://forums.techguy.org/threads/solved-google-chrome-didnt-shut-down-correctly-error-restore-session-bug-please-he.1118647/ and tell me if it works for you.
My OS is Windows 8.1 64-bit. The Chromium version is 43.0.2325.0 (64-bit). Chrome Canary (64-bit), which is also installed, does not cause any problems. Even if i delete the chromium profile, so Chromium is creating an new profile without any add-on, the message "Chromium didn't..." appears on every start of the program. Since Version 43.0.2324 this problem is there.
Tested with 43.0.2325.0 (32-bit). That's really good news !
Do you compile these builds yourself or just link them? why don't you make a version in which you compile with the ffmpeg flags turned on?
@Nyx:
> Do you compile these builds yourself or just link them?
These builds are not compiled by me. I explain that on my #notes. ;)
The secret of all is the official Chromium Buildbot! ^^
> ...with the ffmpeg flags turned on?
I use my own updater which download, extract and install Chromium + Flash + ffmpegsumo + write flags automatically.
So I need not to re-compile Chromium.
I am a simple user like you. This site is only to help us.
When I use the unpacked extension method, only the H.264 has a blue check mark, but not MSE + H.264.
So is there any way to fix the MSE + H.264? :(
Problems:
• 319 series no longer provides 'permissions' info (only cookies and site data) on left click on url icon in address bar.
• Plug-ins are no longer 'click to play' - they are now 'right click to play'. So, unless I choose to 'always run plugin', I am forced to now click my mouse buttons twice.
Anyone else?
By "write flags", I mean that when I used PepperFlash (get from Chrome), my app automatically wrote its required command line flags. Is it clearer?
Codecs work well if all is correctly installed: #comment-443
@_M_:
About Origin Info Bubble (OIB), it is not a bug.
• https://bugs.chromium.org/p/chromium/issues/detail?id=444244
• https://www.chromium.org/Home/chromium-security/enamel/goals-for-the-origin-info-bubble
Yes, right-click-to-play is less simple than click-to-play :/
• https://bugs.chromium.org/p/chromium/issues/detail?id=91182#c15
Both of these are VERY BAD implementations and to me are totally unacceptable. What are these people thinking? *SIGH* Ridiculous.
https://www.quirksmode.org/html5/tests/video.html
First video for example won't play and alot of YouTube videos that are in x264 will just show 360p or 720p whereas it should show 1080@60fps
@Art: Agree, if you could do that it would be great.
@Art: > if you just uploaded the proper extracted ffmpegsumo.dll from the proper Chrome version
Sorry, I cannot because this file is licenced under Google terms. It is not free.
But sure you can use the stable version! ;)
And target string to fix it does not work either...
Version 43.0.2346.0 (32-bit) on Win8.1 fully functional. Didn't test the 64-bit Chromium version
star bug: https://bugs.chromium.org/p/chromium/issues/detail?id=471569
is there a way to extract ffmpegsumo.dll from googlechromestandaloneenterprise.msi without having to install it?
@Jerry: You mentioned you have a script that does that, is there a chance you could publish it?
@Jerry: Thanks, it's not quite as sophisticated as Muhammer Ayes/Zychopat's updater or as informative as your site, but it does the trick
Actually, my script works only with 32-bit Chromium. Because there are more issues on 64-bit Chromium, I do not use the 64-bit version. My script get version of PPAPI Flash and ffmpegsumo.dll from stable Google Chrome or Canary (without install it ^^). Yes, it is possible to publish it. I prepare a nice GUI to launch/manage Chromium on Windows. So one day, under a free and open-source licence... ;)
Do you use a 64-bit version of Chromium?
Images loaded in the browser look even smaller than this.
thank you :-)
It seems version 44.0.2370.0 has some issues with some sites. That's why you should keep the last working version (zipped installer) in a backup folder before updating.
I'm almost positive it didn't do this on Chromium 44.x, but I had to revert because some playback was choppy.
Yes, use --allow-outdated-plugins in this case.
My advice: I see most of issues are on 64-bit Chromium. If you need more than 4GB of RAM for Chromium, use the 64-bit version. Else prefer the much more stable 32-bit version.
I have noticed that the recent versions of Chromium takes quite a long time to clear history when you select the "beginning of time" option.
In the previous versions, this only took seconds despite the cache size.
Kindly submit to you information.
"There are a few GYP flags which can alter the behaviour of Chromium's HTML5 audio/video implementation.
ffmpeg_branding
Overrides which version of FFmpeg to use
Default: $(branding)
Values:
Chrome - includes additional proprietary codecs (MP3, etc..) for use with Google Chrome
Chromium - builds default set of codecs
proprietary_codecs
Alters the list of codecs Chromium claims to support, which affects <source> and canPlayType() behaviour
Default: 0
Values:
0 - <source> and canPlayType() assume the default set of codecs
1 - <source> and canPlayType() assume they support additional proprietary codecs
use_system_ffmpeg
Will build Chromium using the host system's version of FFmpeg
Default: 0
Values:
0 - Build Chromium using the copy of FFmpeg included with Chromium
1 - Build Chromium using the host system's version of FFmpeg"
Thanks.
@494: Older builds for 64-bit Windows from at least a week ago:
• #510: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/328288/
• #500: prefix=Win_x64/328120
• #490: prefix=Win_x64/328078
• #480: prefix=Win_x64/328063
Hope it is ok for you! ;)
About the text highlighting error, the Chromium team knows this issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=491531
Examples about the 64-bit version:
45.0.2409.0: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/330998/ or prefix=Win_x64/331027/
45.0.2410.0: prefix=Win_x64/331101/ or prefix=Win_x64/331218/
Just install the ChromePublic.apk and be happy :D
This what it does then I have to x out and F8 debugging mode. Then it will work for a while then the same thing.
Highlight your text. Then try:
• Shortcuts (CTRL+P) → The print page is now opened → [More settings] → Options → Selection only
• "Print Selection" add-on https://chrome.google.com/webstore/detail/print-selection/gbkdpdnociibpkkpjgmcmdlnjlebpajk
But I also use 32-bit Chromium on 64-bit Win7. I see no print issue on 32-bit Chromium (332091) in the ZIP version. I never use EXE version.
Doesn't seem to be exactly what you're describing, but it might work.
[EDIT: 4 Jun 2015 by Jerry]
Warez site + closed-source and packed installer.
https://www.virustotal.com/fr/file/a4a4c39c9eb6b4edb5c7a296f67b170fd3e715ef69fb9355604c9d1d559e703a/analysis/1433354787/
https://chromium.googlesource.com/chromium/src.git/+/41c1b31dc7983a1dca627f9e00ee3977b75e5b6f
https://chromium.googlesource.com/chromium/src.git/+/0ef24d4197503e228606a4523022d9e9f918202f
LoL, as if that would be so much when we are talking about chrome ...
> Eliminates a large number of windows crashes hit while loading the DLL (see bugs)
Windows...
> Simplifying media library initialization (Remove bool-ness, it just works)
Ok, that might be a reason.
But I hate statically linking the whole world like the Chromium devs currently do it. I hope this won't kill Chromium on Linux, too. I really need to look out for alternatives soon.
They actually reverted all this here:
https://chromium.googlesource.com/chromium/src/+/a31b9ad7e78a1e6174fd218a78b0909079e0afd5
but seems to be only temporary.
目前最后一个支持上述方法的 Chromium 版本为 45.0.2423.0 (开发者内部版本) (32 位)Revision:332890。
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/332890/
@mihau, Please, check the #npapi news.
NPAPI plug-in support will still work with the latest version of Chrome (as I post this) so long as Chrome.exe is launched with the " --enable-npapi-for-testing" switch. However, the switch and underlying NPAPI functionality are still supposed to be removed in the future. So, in case I miss when Google completely removes NPAPI support from Chromium, please keep an eye out for that change.
My main use of NPAPI support is for the Unity game engine plug-in. The Unity web plug-in is still quite popular on many websites with online games.
Also, how we determine whether or not we have digital signature?
I mean, is exist the build 43.0.2357.125 in google storage there https://storage.googleapis.com/chromium-browser-continuous/index.html ?
Don't replace that file. First, because it won't work since the continuous builds are newer than the Canary builds. You can't mix versions or the DLL will crash. Second, even if it did work, you don't work to use the DLL from Chrome because it IS Chrome not Chromium. That DLL is more than just the missing multimedia library.
The only way to get around this problem is to compile Chromium from source code using the add_flag_chrome directives. Google is not going to do that for us.
@vadik, Please check my #comment-35, I have already given the answer! ;)
@JD, I completely agree with you. After tests, I updated the #html5-audio-video part. Yes @549 and @Neh, that sucks! :/
I have few questions:
1 - Those 124 patches made only by Google, yes?
2 - Which Chromium build Google took for Chrome? 43.0.2357.0 (#323865 in google storage)?
3 - The latest "osxportableapps" version has same name "43.0.2357.124" - why? And this 124 patches made only by Chromium builders, yes? But why Chrome and Chromium always have same number?
Sorry for the very detail, i just hope one can understand better what my indirect question is targeting.
Thanks for your interest.
P.s.: A main reason for asking is the cross-platform availability, so if my question can not be answered an alternative would be for example a version tracker (e.g.: RSS / ATOM) that only shows the versions that are identical and available and considered very stable for the Windows and Linux and Android Platform.
http://thewilderness.bplaced.net/chromium_installation.bat (Direct download)
@558, Thanks for your Chromium updater. ;)
@Pai, The last version is 333350. Next version (333471) has not ffmpegsumo.dll.
Matt Giuca (mgiuca@chromium.org) is the official developer.
https://bugs.chromium.org/p/chromium/issues/detail?id=500922#c31
Even after enabling the command-line flags as per #flash, and making sure to update the last flag.
https://get.adobe.com/flashplayer/?fpchrome
I finally found a solution (https://forums.adobe.com/thread/1819231) which basically requires you to close Chromium, edit the manifest.json (/Library/Internet Plug-Ins/PepperFlashPlayer) by changing "x-ppapi-arch" "mac" to "x-ppapi-arch": "x64", save file, restart Chromium.
After doing this, chrome://flash/ finally showed "Flash plugin: 18.0.0.194 /Library/Internet Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin" (instead of "Not Installed") and chrome://plugins/ also showed "Adobe Flash Player - Version: 18.0.0.194" as enabled (instead of not showing up at all).
I hope this helps some folks if they are having the same issue.
Cheers,
It might be a bad virus definition update from Avast because I was using it for awhile, left it open and when I came back home, my shortcut wasn't working anymore. Avast deleted the chrome.exe. And when I tried to unzip it, Avast would delete it.
It also detected something in a .xul file (in AppData - forgot to note it)
Although I could have put an exclusion, I went back to 44.0.2383.0 to see if more info gets out about it.
I just tried to unzip it again and Avast didn't say anything. I'm writing this with 45.0.2442.0
So like I said, it is probably a bad virus definition update and it got fixed afterward.
Cheers!
@public.user: Very interesting! Thanks for sharing. I will update this site in few days.
@568: Check the #malware part. This is certainly a false positive.
I use this uber-simple bookmarklet to download the videos instead (in fact it's mp4 files)
javascript:location.href=document.getElementsByTagName("video")[0].src
Your issue is actually our current problem with h.264 on Chromium opensource, as Firefox has no built flash yet.
I'm actually living from a google chrome dev portable build (no installation, no update), fear the closedsource part..
People, Chromium build 46 as well as Chrome Dev, both on Android, blinks a red border everytime you press something on the interface. Wish they don't deploy this current build from dev channel to the Beta one.
> Ublock Origin has that setting, it doesn't actually work
Yes it works.
The purpose of the setting is not to hide your ISP address, it is to prevent your ISP address from being visible *when behind a VPN*.
Your ISP address will always be visible, WebRTC or not. A remote server does not need WebRTC to find out your ISP address if you are not behind a VPN, it can be seen immediately upon you connecting to the site. The proper thing to test is whether your ISP address can be seen when behind a VPN. With uBlock Origin setting checked, it can't.
So for right now just leave that at DEFAULT setting until this is fixed.
I have the last version of chromium for mac (43.0.2357.130) but the embedded pepper flash plugin is now obsolete and blocked by chromium (high security issue). I tried to download and set up the last version of Pepper Flash plugin but Chromium doesn't detect it. Has anyone got a solution please?
Thanks
Max
@JD: Your project is interesting! Good work.
@gorhill & @JC Denton: Thank you very much for your feedback about WebRTC and bug (graphical glitches on websites).
@Max: Have you seen #comment-566?
@Andre & @Radu Tanasescu: Sorry, I do not send email about new releases. You can use my RSS feeds, #api or a Chromium #updater
> While Ublock Origin has that setting, it doesn't actually work because Ublock Origin is just an extension
Additionally to block worked fully, need block port 3478 for outgoing.
Chromium only detect embedded pepper flash but not the system one (fresh install)
So until the next freesmug build with embedded pepperflash updated, as a workaround i enabled npapi flash version through the flag settings.
I installed flash for safari (which is a npapi version) and disabled the ppapi one through chrome://plugins
I've looked though the 'old versions' link but it is difficult to know what version is what. It is so confusing :(
If nothing else, it would also be nice to make a note on the page saying that v46 has the GPU Rasterization bug and to stick with v45 until the issue is fixed.
• 32-bit: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/338390/
• 64-bit: prefix=Win_x64/338390/
Details:
338432 → 46.0.2455.0
338390 → 45.0.2454.0 (Last version 45)
338361 → 45.0.2454.0
...
334220 → 45.0.2431.0
330269 → 44.0.2403.0
I'm thinking of going back to Comodo Dragon, but that's based on Chromium too, so I have no clue what will happen down the road.
Also, it seems I have to post things twice for them to show up...
https://blog.chromium.org/2015/07/chrome-45-beta-new-es2015-features.html
Why do I use Chromium?
It is fast! Even than Chrome. Why is it faster? Because Chromium has raw power! I don't understand Google how to -and why- make it slower.
Don't angry with me but Microsoft Edge browser faster than Chrome.
http://www.businessinsider.com/microsoft-edge-windows-10-faster-than-google-chrome-2015-7
and It will support Chrome extensions.
If Google enforce us to leave Chromium, we can move to Edge. (as Windows users)
2) FFMpegSumo was likely removed due to licensing issues. That sucks but it is better for everyone if we don't use patent-encumbered codecs.
3) If you honestly think a closed-source web browser is suitable for your needs, you are more than welcome to do so. When the browser it tightly-integrated into the OS, there is no proper sandboxing and anything that corrupts the browser is easily able to escape and mess up your OS. I would rather use Chromium because of the built-in sandboxing that protects me from this crap.
4) I need to know exactly what the 'mini installer' does. I have two new mysterious 'Google Update' services in my 'services.msc' on Win7 SP1 x64 system. I don't have built-in update on Chromium so why were they installed? I may have to end up just doing portable/manual installs from now on if the mini installer cannot be trusted.
Chromium version used by this browser: 42.0.2311.135 (64-bit)
Does that mean it is that actually Chromium based? Or is it a misidentification?
@600: Use the browser you like. I do not promote Chromium at all. My site has only one intention: give us an easy way to download this browser!
@JC Denton, Thanks
RE: 1) Agree with you. On Windows, Chromium is NOT stable... except if you build it yourself.
RE: 4) 'mini_installer.exe' is a 7-zip self-extracting executable. I do not know why you have 'Google Update' services launched. Maybe you use another Chromium application (like a browser, Chromium Embedded Framework...) or Google product. I do not know.
For info, Google Update is based on Omaha, an open-source software.
https://github.com/google/omaha
@604: I updated the site. This issue is not really an issue because Microsoft's Edge (Spartan) browser uses the Chrome/ium UA string (but it is absolutely not Chromium-based).
https://msdn.microsoft.com/en-us/library/hh869301(v=vs.85).aspx
I think it is intentional because according to The Verge, Edge will have support for extensions that can also be used on Chrome (and Firefox).
http://www.theverge.com/2015/4/29/8515771/microsofts-edge-browser-supports-chrome-and-firefox-extensions
On Windows, my favorite browser is Firefox because it is open-source, stable, really powerful to configure (about:config) and personalize, and now in 64-bit version. But Google's decisions already decide Firefox's direction anyway. I dislike the UI and features by default on Firefox. I often disagree with Mozilla choices... like Google choices about Chromium. Rrrrrrr! Like you "I just very upset about Google", Apple, Microsoft, Opera, Mozilla... ;)
Example: https://bugzilla.mozilla.org/show_bug.cgi?id=1174462 (Read comments. This is edifying!)
" --enable-npapi-for-testing also has been removed after 46.0.2459.0 (339215) build."
Thanks for the notice, QQ. The latest dev build of Chrome (46.0.2467.2) which I just installed also has removed that command-line switch. At least the latest SlimJet browser still supports NPAPI.
Why current LKGR build is 341287: https://chromium-status.appspot.com/revisions
While current continuous build is 340078?
• https://build.chromium.org/p/chromium.lkgr/one_line_per_build
• https://build.chromium.org/p/chromium.lkgr/console
I did not find any report in the issue tracker.
• https://bugs.chromium.org/p/chromium/issues/list?q=label:Infra
And via your link, there is no way to download the release 341287. Also check the LAST_CHANGE file in this repository.
• https://storage.googleapis.com/chromium-browser-continuous/index.html
So where are the new LKGR binaries?
If you absolutely need a new Chromium version, use the Snapshots repository. Be careful! These builds are not tested by the buildbot and can be very unstable.
• https://storage.googleapis.com/chromium-browser-snapshots/index.html
• https://www.chromium.org/getting-involved/download-chromium
• https://chromium-build.appspot.com/p/chromium/console
• https://build.chromium.org/p/chromium/one_line_per_build
@615: I tested Iridium browser in its last version (v43.8). There is no support of proprietary codecs in HTML5 tags :/
I need older version of Chromium for testing Chrome extension.
How can I determine which builds in Continuous directories is used for official Chrome releases. There are so much builds in there.
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/
Thank you very much.
Thanks.
https://support.1password.com/code-signature/
@620: There is absolutely no Avira extension pre-installed in Chromium build. In short, the Avira's extension "SafeSearch Plus" (replacing "Browser Safety") is already included when you install Avira Free Antivirus, NOT Chromium.
During the Avira Free Antivirus setup phase you were asked to install SafeSearch Plus. This is Avira’s browser extension designed to block access to malicious web sites. If you have not declined the offer, Avira automatically added this extension to your Chrome/ium user data folder.
https://www.avira.com/en/avira-safesearch-plus
https://support.1password.com/code-signature/
This was done a long time ago. On 44.0.2462.0 works. And since 44.0.2472.0 not working.
can some one pls let me know which version was the LAST UPDATE THAT CAN USE JAVA
or enable user to MANUALLY activate Enable NPAPI
if someone can provide link to download would be greatly appreciated
or if anyone can advise how to use Java with the latest update?
unfortunately I still have a website that use Java and I don't really want to switch to other browser
Thanks many in advance and thanks for the great and generous work Jerry!
Java does not have a PPAPI plugin available. Only the NPAPI plugin exists.
Chromium version 45 and higher do not have a NPAPI plugin support.
I know 2 solutions:
1) Using an old Chromium version
Please check the #npapi part for download an old Chromium version. By default the NPAPI plugin support is disabled. So enable the option on chrome://flags/#enable-npapi then click the "Relaunch" button that now appears at the page bottom.
2) Using a new Chromium version
Install Java plugin for IE then use the "IE Tab" Chrome extension. You can set up Auto URLs to automatically open certain urls using "IE Tab", providing a seamless experience, as if Java support never went away.
https://chrome.google.com/webstore/detail/ie-tab/hehijbfgiekmjfkfjpbkbammjbdenadd
For info, Oracle’s official documentation recommends Firefox or Internet Explorer if you need the Java plugin.
https://java.com/en/download/faq/chrome.xml
Since you are admin,
kindly please advice is version 44.0.2403.130 build (330231) is the last copy of version 44? or is there a later copy?
I tired install and uninstall a few and is quite a bit of guess work
since the files in depository does not tell which version it is just by the build no.
Can you help? I don't want to waste your time
but if you can easily let me know which one is the last update for version 44 I would be grateful.
I like to update to the closest copy possible
with most possible bug fix in the last version 44 copy as possible.
And thanks for the solution will try them later.
> with most possible bug fix in the last version 44 copy as possible.
On Windows, you cannot find a Chromium binary equivalent to Google Chrome because no developer or team share it. Please read my #comment-35
> 44.0.2403.130 build (330231)
So you talk about the #stable-chromium-version (because this build has 130 patches). If you really need it, you must to re-build it. Otherwise use Google Chrome:
https://googlechromereleases.blogspot.com/2015/08/stable-channel-update.html (44.0.2403.130)
For info, the last Chromium build with NPAPI support is:
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/331982/ (45.0.2416.0)
Sorry for all to read such novice post of a regular simple user.
I decided to follow your solution one using older version
but wanted to get as "updated" as possible to a version that still enable me to use NPAPI.
At the moment I like to stick around with you wonderful people or peeps than switch to Firefox or others.
Great work again and heartfelt thank you for all the unseen effort you and all the developers pour into benefiting the internet community as a whole worldwide.
This is indeed great work for simple user like me at a time of increasing challenges from all the unfriendly parties.
I put my trust in you and chromium here.
There you can see the different channels of Chrome and the branch_base_position of each version. These can be used to download a Chromium-Version from here: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/
But be aware as Jerry had pointed out several times, the Google Chrome Version is only based on Chromium, but then patched by them. For example, the current Google Chrome Version in the Beta-Channel is 45.0.2454.26 and based on branch position 338390. That equals Chromium 45.0.2454.0, but Google patched that version with 26 patches that are not in chromium at that branch position. I don't really know, but feature-wise i never noticed a difference. But these patches can be simple bugfixes or security patches. And these security patches are not in that chromium version, but most likely in a later branch position.
"Chromium 45" can also use NPAPI-Plugins up to the latest version (Branch Position 338390/Chromium 45.0.2454.0), but ONLY if you append " --enable-npapi-for-testing" at each start of Chromium!
About the " --enable-npapi-for-testing" flag, check #comment-596 ^^
Previously, I used to be able to copy entire Chrome User Profile\Default from OS to OS and PC to PC.
C:\Users\\AppData\Local\Google\Chrome\User Data\Default
It appears chrome has started locking/ securing things down in some way? So I may considering migrating all of those to CHROMIUM.
A) This the current Chrome Version 44.0.2403.155 m I am running.
- What version/ release of Chromium would match/ map it the most? (Best migration compatible)
- Where/ how can I download it?
B) If you could point to a place where I can understand the pieces (files) better so that I can migrate some of them.
https://superuser.com/questions/951095/
Your folder should be correct... The Mini Installer uses this folder: C:\Users\<USERNAME>\AppData\Local\Chromium
I don't see why copying the User Data folder between Chrome/Chromium, I think I've done that before. I did run into issues changing from newer profiles to older ones, however I did just "downgrade" from Chromium 46 to 45 (for ffmpegsumo support).
Let's see how my migration of User Profile data goes. Its been a pain as I outlined on the Super User posted Question.
If that doesnt work out, what would be the next stable Chromium release after: Version 44.0.2403.0 ?Please do point me to that as well if you can.
PPS: Do you know any way I can circumvent this issue I am facing with Chrome User Profile migration?
Is there some document that details out the "File + Folder" Structure for User Profile data?
I believe for the most part, the latest builds linked here are as stable as Chromium can be. I did have some issues around the time of 44/45 and a casting site, but its been resolved in 45, and there is the issue of dropped ffmpegsumo (html5/h264 video) DLL support towards the end of 45 and no solution/workaround for playing those videos yet (if ever) in 46.
@Dave: Yes, it should be 64bit even if it says 32.
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/343233/
Here's the bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=521242
Not loading properly: CMD boxes open. Cannot use the browser unless the flag ' --no-sandbox' is added to shortcut.
First look on the CMD application then opens and gives you the option to wait or kill the browser after a few minutes
A bug report has already been filed at https://bugs.chromium.org/p/chromium/issues/detail?id=521148
We don't need warnings.. we can figure it out if Chromium is working.
And when it's not.. we know how to file a proper bug report..
First of all, what kind of trolling that would be? Making people skip a few builds of Chromium that might be glitchy? Wow, what an epic troll!
Secondly, who are "we" in your statements? Are you a representative for a major part of this page users?
My posts were directed at people who do not want to spend their time reinstalling Chromium. That's all. That being said latest builds (2487 and 2488) work for me now.
Confirmed working on Windows 7 x64 perfectly fine!
As a bonus, they fixed GPU Rasterization bugs :)
https://storage.googleapis.com/chromium-browser-continuous/index.html
@mihau: Thank for links.
@eliotime3000: I sent to you an email.
@Xis: Here, you download from Google servers (storage.googleapis.com). Ask Google to improve its bandwidth! :)
HTML5 video should work on that build. I usually don't change builds unless I see some good comments about it.
or, to be a little more serious: did they remove WinXP support as of v 47?
I did search the web but couldn't find a word about this, yet none of 47.x builds seem to work on XP, i.e. Chromium starts but does nothing and even loads its own special pages such as chrome://downloads indefinitely
@mihau: Same issue for me.
Info about WinXP issue/support:
• https://www.reddit.com/r/chrome/comments/3hy025/help_chromium_does_not_load_any_page_on_windows/
• https://chrome.googleblog.com/2015/04/providing-updates-for-chrome-for-xp.html (Google Chrome)
After tests on WinXP SP3, I updated the #windows part.
Issue 521294:Chromium is hanging on Windows XP (SP3)
https://bugs.chromium.org/p/chromium/issues/detail?id=521294
Please, vote for this bug! :)
cassiopesa
cassiopesa is a chrome variant that is designed to display ads and potentially compromiseserdate. it is bundled with other software.
HKCU\Softwre|Microsoft\Windows\CurrentVersion\Uninstall\Chromium
What's up with this?
Thank you
https://en.wikipedia.org/wiki/Browser_hijacking
Remove Cassiopesa:
• https://malwaretips.com/blogs/remove-cassiopesa-com/
I think you downloaded an executable from an Internet download directory website. For example, CNET Download.com install malware:
• https://en.wikipedia.org/wiki/Download.com#Criticism
• https://www.howtogeek.com/198622/heres-what-happens-when-you-install-the-top-10-download.com-apps/
https://storage.googleapis.com/chromium-browser-continuous/index.html
https://build.chromium.org/p/chromium.lkgr/builders → Continuous repository.
This is why I display all official links on each release. Nothing is obscure on this site! ;)
#3 thestig@chromium.org
If you look on the bottom of that webpage, it says "Unaffiliated with The Chromium Authors" - we do not distribute the binaries on that page. Not sure what we can do if they are distributing some kind of malware. Someone else reading this bug may chime in with a better answer.
Cassiopesa is NOT a Chrome variant, it is a browser hijacker!
I've installed the Adobe PPAPI player, but Chromium doesn't recognize it.
According to the flash section on this site the name of the pepperflash dll is pepflashplayer64_[version].dll or pepflashplayer32_[version].dll.
But the Adobe player uses NPSWF64_[version].dll and NPSWF32_[version].dll.
Is that why it's not working?
@Josh S
> Is there a way to find specific older versions of Chromium?
No. There is only the repository. I made my own tool and prepare a new page for that. ;)
First v34: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/242666/ (34.0.1765.0)
Last v34: prefix=Win/252017/ (34.0.1848.0)
So the v34 is beetween 242666 and 252017 in this repository.
NPSWF***.dll is still the #npapi plugin. It doesn't work with Chromium... but works with Firefox.
For Chromium, choose the PPAPI version!
I had to revert to build: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/351025/
Bug Report has been filed: https://bugs.chromium.org/p/chromium/issues/detail?id=537508
Also using allow-outdated... doesnt help. It shows "Plug-in konnte nicht geladen werden". I also tried adding all rights for my current user for the directory and file (and also the default directory in windows/system32)
I'm using Windows Vista. I think i had no trouble before upgrading from 18.0.0.209 (or some newer 19.0... version), but i thought updating would solve the (well-known) duolingo audio output problem. Now no flash works anymore.
I'd rather put it in manually.
It's used for deployment and seems that chromium ignores master_preferences at all
master_preferences seems to not be used because it's a First Run action (disabled by default).
@mihau: I didn't have the same experience as you (or it wouldn't have been released). More details would be nice, though I'm not sure how useful it'd be at this point.
It is reproducable with the mentioned setup file on WinXP SP3, installation directory "C:\Documents and Settings\Administrator\Local Settings\Application Data\ChromiumP" in my case - all contents of "App\Chromium\32\Data\Profiles" is being wiped upon installation.
The next v48 (NOT v47 which I have already built) release will include code to preserve data even in the App directory, though.
anyway i was using Version 48.0.2533.0 (64-bit) on win7 for all these while
and suddenly yesterday when I boot everything up and open a blank page
chrome advice me it disconnect extension was installed on it...
of which I did not do it or rather I tried and install and then uninstall it 10 in after and it was not there for months...
and then seemingly it install it self yesterday... I remove it... security breach?
also I notice the presentation of the page like tab seems abit wider
and the history tab has a different icon all without me changing a thing, no up grade no update...
something I should be concern?
or something is suppose to tweak in the background?
any ideas? explanation?
Thanks all and much appreciated
Thanks Jerry for keeping this site in immaculate & help
> The next v48 (NOT v47 which I have already built) release will include code to preserve data even in the App directory, though.
Good news. Thanks a lot for your great work!
@719: Sure you can build codecs with ffmpeg yourself. https://www.chromium.org/developers is for you! ;)
@Java Help: I am sorry. I have no explanation. Did you search info in the issue tracker too?
@721 & @723: Very helpful info. Thanks
@nimitz: As far as I know, if you talk about sum checker, there is a MD5 response from Ajax request, on Continuous repo.
Sorry to trouble you all here...
No unfortunately im not that tech savvy but suspect it may have to do w MS pusing w10
and i manually aggressively remove all the updates re w10 push upgrade via regedit.
i may have overdone it and w7 maybe automatically 'restore' something and it pull an image/backup from somewhere...
windows have self healing power right?! (aka eyes on everything?!) HA :D I used to admire its magical power once b4....
anyway seriously plotting to move to linux or os but 1)im feel quite inexperience (even after wks of research) 2)old computer prevent from dual-boot
anyhow... not sure what the issue re. tracker but ms has lost the plot it seems when serving paying customers (now its like its harvesting for profit and doing it blatantly unashamedly legalized-'criminal'? some say)
Sad :( but as such humanity move on (if they are not render extinct or self-annihilation by miracles)
hv a Gday to you Jerry and all
Peace,
Ideally for this to work I imagine I need to use the same version # ffmpegsumo.dll.. But chrome 45.x does not have that file. Did some research and it appears it was deleted in v44. Not sure what .dll handles the h264 now.
Anyways I tried the one from 43.0.2357.132 as I believe thats the final stable chrome version that has it, plus other good stuff like npapi support (google is being such garbage removing very useful features lately)..
But yea it doesn't work. It does enable mp3 support, and most other audio codecs, but h264 video still refuses to play. Also installed your extension too, it has no chance on your test page.
Really bad thing is youtube. Some/A lot of older version are ONLY available in h264 in hd. With your extension, the audio plays and the video remains blank. Without your extension, they play in horrible 360p and act like there is hd version available, also quite bad. I can fix it by forcing the flash player, but these days the html5 player is actually a little faster and smoother.
Main reason im trying to use chromium is yet another chrome bug, that luckily doesnt exist in chromium:
Chrome CONSTANTLY nags me to update, even thought I have forcibly and properly disabled updates via gpedit.msc. It also auto updates without permission with auto update disabled, frequently. I disabled it by denying access to google update, which comes with its own issues, but ultimately it still nags me to update.
I much prefer manual updates like chromium allows. So would be nice to use it, and have it fully function on youtube.
(Pretty dumb youtube wont work correctly on googles own browser when they own youtube itself.. And I know, they don't have rights to h264 so they are updating youtube to vp8/9, but they still have clearly not finished that, so removing support so early was a very bad call)
https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/333350/ or prefix=Win_x64/333350/
https://github.com/xinhugo/Chromium-Download-Manager
At first it was crashing my browser tab. Figured out the dll available there is only the 32-bit version. So I downloaded the specific revision you linked - 333350, win32. (ps kinda dumb how all releases are labled win32, even the win64 ones)
And used that dll.
Result is the same as when I used unmatching version numbers:
mp3 support becomes available.
h264 continues to not work. Tested 2 sites:
Woolyss tester
Youtube.com HD (This link has tons of videos only available in h264 for hd:
https://www.youtube.com/watch?v=RG3C3KU82VE&list=PLB8fVKhVbgxcXYyouvQz4de4_BH5qIswq
Sadly had to resot back to chrome. Updated and went through more rigirous changes to disable auto updates since they are way too frequent and annoying. Sure enough one came the next day, but luckily this time around the build I managed to snag doesn't seem to ignore my group policy settings. It changes the color of my menu button and notes an update, but doesn't nag me. (yet, hopefully its not a timed thing)
It seems Firefox has/had a similar issue that could be solved by adding "media.mediasource.ignore_codecs" and setting it to true.
http://www.ghacks.net/2014/07/25/enable-mse-h2-64-support-youtube-firefox-right-now/
The closest I could find for Chromium is the "-Dproprietary_codecs=1" option while building, which doesn't really help. A related build option is "-Dffmpeg_branding=Chrome".
I played around with some of the options in the Flags page, namely chrome://flags/#disable-media-source , but it has not helped any.
Now, for something actually useful... You could always try the Disable Youtube HTML5 Player extension:
https://chrome.google.com/webstore/detail/disable-youtube-html5-pla/enmofgaijnbjpblfljopnpdogpldapoc
Using that I was able to watch the videos in the link you provided, in 720p HD, using the Flash version of Youtube.
Using youtube center developer build + tampermonkey is actually a more reliable way of making that work. As it can force the flash player everywhere including embedded sites. The disable html5 extension isn't quite as reliable, as on some newer videos where youtube doesn't really expect the flash player to work, it just breaks or sometimes manages to load both, resulting in audio echo.
Though I actually used to do that for a year+ early on when the html5 youtube player was pretty crap. They did a lot of work on it and nowadays it's actually faster and more reliable than the flash player, on high end systems. Still uses more resources, but eh my systems fast so ill use it.
Namely SPF only works reliable with html5. It's a cool tech that makes youtube ultra fast when switching videos, as it only loads what changed, rather than the whole page.
For now ill have to use chrome on windows and probably use chromium on linux if the codecs keep working.
Will it ever be included again?
Are there any compiled builds available with HTML5? I don't want to use Chrome because I don't feel I should be shoehorned into using something (not to mention being forced to compile Chromium in Windows). It's absurd that open-source software should be so dysfunctional in 2015, when HTML5 video is available in every other browser.
http://www.thumbapps.org/2015/06/Chromium-browser-portable-32-64-bit.html
They mention that Chromium is not intended for daily use, and this is a good example of why.
No... and no, on Windows.
@Lion, Yes, I think it could be possible to add OpenH264 to Chromium.
@736: I agree with you but it concerns only Windows. Developers compile stable Chomium versions on Mac, Linux and BSD. Proprietary codecs are also available.
@Andrew Sung, Check Google groups in my #comment-1 They can help you.
@738: If you build Chromium yourself, compile the #stable-chromium-version and re-build it when there is a new stable release. Follow Google Chrome releases on https://www.chromium.org/developers/calendar to know stable Chromium versions.
You would need to update your source repos, rebuild, and then "reinstall" -- either running the mini installer -IF- it works, or copying the files over.
Can this be confirmed by other users please?
- Web site: http://www.henrypp.org/product/chrlauncher
- GiHub page: https://github.com/henrypp/chrlauncher
License GPLv2 - use it in a specific folder for obtain updates: recognizes 64 bit automatically.
Now you can set the download directory that contains the update for each type of Chromium Portable.
Simply fill in the file 'chrlauncher.ini' the heading 'Chromium binaries directory' the entry 'ChromiumDirectory=\ Bin\Chrome' (if you use winPenPack). Of course you have to take away from 'ChromiumDirectory' the hash character (pound) otherwise it does not work.
@rbon: Big thanks for this news. Great updater!
@tam: I do not see bug like that on 32/64-bit Chromium on 64-bit Win7.
https://bugs.chromium.org/p/chromium/issues/detail?id=564364
@tam: You should! ;)
@V: I think you can... but sorry, in command-line, I use only #windows-64-bit-chocolatey and other shell scripts. So I cannot help you. :/
Ex: https://stackoverflow.com/questions/17536405/cant-set-chrome-as-default-browser-from-powershell
I know I need to manually enable some settings but which was the last version if anyone know or can help find out easily.
Running on Windows MS. Need to access some asian website who are still running the old technology.
Is silverlight generally safe to use? why does many major browser ditch it? If you have some more time to explain a little. Just curious for a non-tech person.
Many Thanks in advance :)
This plugin needs #npapi support. Check in this part to download an old Chromium version. Check info on site archives too.
You must be very proud of your work here
I notice the new download site too AWESOME MAN! Very nice clean look and easy to download.
I have nothing to offer you back for your kindess and great service here but to wish you sincerely all the best!
Hope you and your loved ones have a good Xmas and blessed NY ahead :)
Peace to all your users here too :)
p/s yes jerry nothing is safe with the current world gov trending policy
unless we go back to stoneage or move forward to use telepathy :D Ha
the problem has never been technology but the hearts of man.
So its very very good to see someone like yourself Jerry be a testament of good selfless service
and the universal work towards a more integral free world is still strong and alive. Thanks again.
I am presuming both are portable and upgradeable.
https://www.chromium.org/administrators/policy-list-3
This site is not affiliated with The Chromium Project, so posting it here isn't going to do a whole lot of good since the devs won't read it.
https://www.chromestatus.com/feature/6417796455989248
Longtime leecher here Jerry, big thanks for your work!
What is going on?
Does someone know?
Is there a portable version that allows me to submit command line parameters and change the temp directory?
@780: No, the 64-bit version is not dead. This is only a buildbot issue. However, the other builds are ok.
@Jake: Try http://www.henrypp.org/product/chrlauncher. You can write parameters in the INI file.
This is, however, not related to a bug in the chromium source code. Who are we supposed to tell about this to get it fixed?
https://bugs.chromium.org/p/chromium/issues/detail?id=576253
• Incognito mode (#command-line-flags)
• or chrome://settings/content → Cookies → "Keep local data only until you quit your browser"
@Ernie: Thank you for your help! After checks, I updated the #privacy part.
So the problem is not the source itself, it is something with the automated testing/building/release infrastructure at Google.
I don't know why they do not fix it... But they seem to prefer the 32 bit version for Windows..
Your build: rghost.net/8BjnRLZYz (mini_installer.exe • 64-bit • 50.0.2624.0)
Antivirus results:
• https://virusscan.jotti.org/en-US/filescanjob/7riadl2du1
• https://www.virustotal.com/en/file/c68c9e514881571275ab885a779fc2f5bb560632e3a3b7efb2b71c2c308f4e43/analysis/1453137495/
They marked the bug as "wontFix" because it's already been fixed apparently. But if so, why is the compiler still failing?
I don't get it anymore.
@805: here is my batch file, maybe it'll help you https://pastebin.com/63hciMSh
1. download, install and first run Chromium Portable:
- web site: http://crportable.sourceforge.net/
- direct download latest (49.0.2618.8): https://downloads.sourceforge.net/crportable/ChromiumPortable_49.0.2618.8.paf.exe
2. create two subfolders inside '\ChromiumPortable\Data':
-> \App\PepperFlash\32 and \App\PepperFlash\64
3. download from PCR's notepad https://notepad.patheticcockroach.com/category/software/flash/ the latest archive with 'Flash 20.0.0.267 for portable Firefox/Chrome'.
4. extract from this archive all files contained in the subfolder 'Pepper64': manifest.json, pepper.vch and pepflashplayer64_20_0_0_267.dll and rename this last to pepflashplayer.dll; finally copy these three files inside:
-> \ChomiumPortable\Data\App\PepperFlash\64
5. create a text file with name 'mms.cfg' with one row with DisableSockets=1 and copy these mms.cfg in the same subfolder as above
6. If You use X-Chromium by winPenPack:
-> update with 64 bit version of Chromium with chrlauncher http://www.henrypp.org/product/chrlauncher and then copy the four files as above inside the subfolder \Bin\Chrome\plugins
Does it mean that the x64 project has been abandoned, just now that more and more x64 machines are sold?
Regards.
mini_installer - rghost.net/8M5WW6XXM
only archive - rghost.net/7rKYpdpHb
Compiled with parameters:
target_arch=x64
libyuv_enable_svn=1
proprietary_codecs=1
fastbuild=2
syzygy_optimize=1
remove_webcore_debug_symbols=1
ffmpeg_branding=Chrome
google_api_key='no'
google_default_client_id='no'
google_default_client_secret='no'
Please can you contact me? I would like to give you a suggestion.
@John, jason: No, the x64 project is not abandoned but devs want to clean non-sanitizer configs on this bot.
https://bugs.chromium.org/p/chromium/issues/detail?id=578819
First, thanks for your work !
I'm a windows user, I don't understand the thing about version 50 and x64, it is not official ?
I downloaded v50 x64, but sync doesn't work and I don't what is this api problem mentionned earlier !
Should I stick to v50 x32, or even v49 x64 ? (sync worked then)
Cheers!
mini_installer - rghost.net/8RJGkVjPt
archive - rghost.net/6kfWv5n5y
I've managed to complie (and run) Chromium x64 50.0.2631.2 with the following parameters:
python build\gyp_chromium -Dtarget_arch=x64 -Dbuildtype=Offical -Dbranding=Chromium -Dlibyuv_enable_svn=1 -Dproprietary_codecs=1 -Dfastbuild=2 -Dsyzygy_optimize=1 -Dremove_webcore_debug_symbols=1 -Dffmpeg_branding=Chromium -Dgoogle_api_key='xxx' -Dgoogle_default_client_id='xxx.apps.googleusercontent.com' -Dgoogle_default_client_secret='xxxGBZyOj8sv2CNe_yhBzMa'
For some reason my git build system won't update to v50.0.2632; perhaps because i've patched 'battor_connection_impl.cc': and cannot rebase - I have unstaged changes. Now, I understand why in your batch file you wrote "cd /D J:\tmp\depot_tools\src"
Would you consider writing a tutorial?
For any one thinking of building Chromium x64 from source you need approximately 30GB (not including winsdk and VS2015). The build process takes approximately 5 hours (i7 VM 4GB RAM - 4 virtual CPUs. The build process would take considerably less using a physical machine: with the approriate firewall settings - which I'm still in the process of assessing.)
Personally, I think the BuildBot failing on Windows x64 build is a blessing in disguise.
i'll try to post updated batch with comments
i. git checkout master
ii. git checkout -- e:\depot_tools\src\tools\battor_agent\battor_connection_impl.cc
iii. git rebase-update
iv. gclient sync --jobs=16
I don't think step iv is strictly necessary. For some reason I had to create a .gclient in 'depot_tools\src' before 'gclient sync' would work, which results in gigabytes of data being downloaded.
At the moment I'm experimenting with the build process and trying to establish best practice.
(maybe someone else will find it useful)
@nik Your builds are better compared with vanilla Chromium builds, since you've got full Google API (Sync, etc.) support, along with all media codecs (H.264, MP3, etc.). There definitely seems to be demand for your builds even despite these x64 buildbot failures. I would think that some users may even be willing to make donations to you to thank you for your time and for sharing with the community. Thank you, sir.
@WildByDesign: you're welcome.
here is new build 50.0.2634 with sync and codecs:
mini_installer - rghost.net/6TNrdDB9w
archive - rghost.net/7pwZGq2sJ
I know that on the #npapi section it says about 45.0.2416.0 (331982) being the latest one, but i have found through extensive testing, that this version has memory leaks/problems.
So if someone has an older chromium build (with NPAPI), thoroughly tested, please post any info.
Thank you!
Keep up the good work, You've demystified a poorly documented build process. Is there a reason why the standard chromium build does not include the AV CODECS?
Build 50.0.2634 available in x64 right now.
@848: Yes, all works perfectly!
@IamNoone: Go to https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/ or prefix=Win/ and get revision (= commit position) before 331982. The NPAPI plugin is enabled.
Thanks anyway!
I have small issue with this latest build.Somehow button X close is duplicate it self in the middle of the tab.
Teknik is established. It's open source, with a major update coming soon. Oh, and it's completely free. Anyone doesn't require an account to use the upload service.
@JohnFlower: i tried teknik.io and i couldn't upload, half *.js and *.css return 404, API doesn't work. message was "resource unavailable"
Then I let the file check by virustotal.com. 2/54 discovered malware:
Bkav HW64.packed.B4BF
Rising PE:Malware.Generic(Thunder)!1.A1C4 [F]
What is going on here?
> Firefox blocked my download
Because "Block reported attack sites" and "Block reported web forgeries" are enabled in your Firefox (as Chrome, Opera, Vivaldi) security parameters.
These options use Google Safe Browsing.
> virustotal.com: 2/54 discovered malware
False positive. Please check #malware section.
sometimes i'll be publish updates..
Chromium Portable 49.0.2623.23 is the last build compatible with XP:
https://downloads.sourceforge.net/crportable/ChromiumPortable_49.0.2623.23.paf.exe
Chromium developers what are you doing? :(
@nik, you need to recompile or last build 2642 now, or wait for 2643 tomorrow. ;)
https://chromium.googlesource.com/chromium/src/+/72fc4b00f6429a70e1c841a9678af04580ce1efd
@nik: You're the man. I've been wanting builds with codecs enabled for ages now.
@Jerry: Are you planning to keep separate sections for nik's stable and latest builds permanently? Because it sounds too good to be true.
@889: > keep separate sections for nik's stable and latest builds permanently?
Yes, we continue together. Nik does really great work! Note there will be no stable 32-bit version on Windows.
About chromium_x64_50.0.2644.0(r374049)_sync_codecs_portable:
Languages files (*.pak) be located in \bin folder, not \bin\Locales. Therefore, chromium can't run. Of course, the solution is simple. All languages .pak files must \bin\Locales. So, chromium portable is working.
Another matter/request:
I'm used to Chrome icon, not blue Chromium. Therefore I always "Icon Group" change with ResHacker.
Standart Chrome icon: https://commons.wikimedia.org/wiki/File:Google_Chrome_icon_(September_2014).svg
I use "List" as view in File Explorer . (CTRL+SHIFT+5). I changed the icons "chrlauncher.exe" and "\bin\chrome.exe" with ResHacker. Notwithstanding, both files still display blue chromium icon, not chrome icon. (Only "List view" in File Explorer). How can I fix its? Is it possible?
Thank you so much ;)
Visually, the 50 builds seem to be testing the Smooth Scrolling feature to various degrees of success. There are likely many other changes, but that is all that I can think of at the moment. It all depends if you want to stay with Stable channel releases that follow Google Chrome stable builds or follow the bleeding edge changes in the browser with faster development. Another visual change between 50 and 48 right now is that 50 contains some more Material theme effects, while 48 has some basic stuff for Material.
chromium_x64_50.0.2645.0(r374091)_nosync_codecs_installer.zip
rghost.net/8Qx8rV9cP → it is malicious, and Chromium has blocked it.
Does anyone else got blocked?
or is the download not safe?
or it is a false positive from Chrome?
Thanks
@pureocean: I ask nik.
@896: Please see my #comment-867
Who cares about Google Chrome? First, this site is about Chromium, Google Chrome's mother. Second, anyone foolish (and I'm using a polite term) enough to install a spyware browser....is the same person who installed Windows10.
"...I would still highly recommend switching to [ ], Opera,..."
First of all, Opera (another spyware browser) uses Google Chromium as its foundation, thus, since Chromium support for XP & Vista are/have ceased, you can't possible use this browser (and why the h*ll would you).
But why is the MD5 checksum does not match? for both 48 and 50 mini-installer?
Is this to do w my connection or theres some misunderstanding?
Still keen to try nik's
@Jerry: Thank you, sir, for providing this wonderful platform and wealth of information. I am relatively new to following your site and also following Chromium development in general. Also, thank you for allowing @nik's fabulous builds onto your site. I think that you have done a fantastic job with the way in which you've organized his builds at the top of your site; tidy, clean and professional. Clearly, Stable channel Chromium builds including Codecs is something that Windows users have wished for a skilled compiler to come along and build for quite some time. This is like a dream come true. Cheers!
or you have other goodies build in?
hv finally install v50 after temp shut down AV (which I didnt have to w normal chromium)
MD5 checksum is good but VirusTotal does bring up one suspiscion
some webpage w charts function dont load that well... and some other cosmetic changes
prob due to different ver - was using early 48 chromium
also notice the good increase of speed (loading and downloading)
dont really use any codec related that much but want to try your build
like the no sync fucntion for increase privacy
anyhow good effort much appreciated
thank you
@Jerry: Have you thought about separating the comments section into a separate page? Thank you for facilitating all this information in a nice, easy to understand format.
Adjusts scroll position to prevent visible jumps when offscreen content changes."
I'm over the moon right now.
Chromium has REMOVED the cipher information on HTTPS websites meaning you can't tell anything about it by clicking on it like before. No TLS version, no cipher information, nothing.
If you haven't explicitly disabled all RC4-specific ciphers then please do it NOW!
Here are the command line options I use on Win7 x64; just copy and paste it and remove extra spaces/line breaks and comments in ():
Target: %LOCALAPPDATA%\Chromium\Application\chrome.exe
-cipher-suite-blacklist=0xc007,0xc011,0x0066,0xc00c,0xc002,0x0005,0x0004,0x000a (these remove all RC4-specific ciphers)
-ssl-version-min=tls1 (forces TLSv1 and higher to prevent downgrade attacks on insecure/poorly-configured servers)
-incognito (private browsing mode)
-disable-sync-preferences (allows different preferences depending on the target OS/system)
-disable-print-preview (lets me do 'printable view' easier)
"WARNING to potential Chromium v50+ users!
Chromium has REMOVED the cipher information on HTTPS websites meaning you can't tell anything about it by clicking on it like before. No TLS version, no cipher information, nothing"
Sorry to inform you but I'm using Chromium v50 and the https connection information is exactly as it's always been.
ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION
Anyone can test it at https://www.howsmyssl.com or https://badssl.com
but it must support:
1) cURL upload or api
2) direct link to dir with files
3) auth for deleting old files
4) fast upload.
1. click the padlock
2. click "Details"
3. reload the page (??!)
4. select the main origin
I just write a script that is checking git updates, pull, compile and upload to filehost.
After that i don't do anything myself with this process :)
All I know is this:
https://en.wikipedia.org/wiki/Background_Intelligent_Transfer_Service
https://codereview.chromium.org/105853002
> Implement a background downloader using BITS in Windows Chrome. (Closed)
So the Chromium devs have chosen BITS component of a system services as a background downloader, but for what?
How to find out what exactly Chromium is downloading using BITS? and why the hell he don't clean up these folders after himself
I am a bit paranoid.
Using BITSAdmin Tool from Windows XP Service Pack 2 Support Tools
https://msdn.microsoft.com/en-us/library/aa362813.aspx
bitsadmin.exe /list
I found list of these BITS-jobs by Chromium, and all of them contain "Chrome Component Updater".
Further we can find this:
https://support.google.com/chrome/a/answer/3204698?hl=en
> Chrome Component Updater allows the Chrome engineering team to release small updates to parts of Chrome on a very rapid schedule. The Chrome component updater behaves as follows:
- Runs only when Chrome is running, and uses a small amount of bandwidth
- Doesn’t update the Chrome browser's core application (chrome.dll)
- Only updates components that the Chrome core already knows about
- Is used for some core plugins and components that are intended to be downloaded after the initial Chrome installation (such as SwiftShader and Pepper Flash)
Interesting. Now we can find more info about such components, like:
https://support.google.com/chrome/answer/6072728?hl=en
https://plus.google.com/+FrancoisBeaufort/posts/51erocHcazG
And here is list of all your Chrome components:
chrome://components
(Pepper Flash may be not included if you're using global installation into system)
Finally, if you need it for some reason, you can disable Component Updater using --disable-component-update
And all of this chrome_BITS_* folders will no longer created, but you will lose some (important) updates, see above.
If you go then on chrome://components you will see "No components are installed", but it's not true, e.g. you can check how pnacl is still working here:
https://gonativeclient.appspot.com/demo
Also the BITS-jobs itself will not be closed until your Windows rebooted (I guess), but they will be suspended.
Well ok then! But I still wanna cleaning up these folders with keeping updates on :D Anyway.
But of course, we can't be sure these BITS-jobs are used only for updating components and not for compromising some info about your computer/browser to google services... Without reading source codes or check it with something like Wireshark.
https://cs.chromium.org/chromium/src/components/update_client/background_downloader_win.cc
You can download: https://github.com/henrypp/chrlauncher/releases/
1. full version with portable PPAPI
2. version without portable PPAPI
Inside both versions there are folders '\32' and '64' that contains the file 'SetDefaultBrowser.bat': this script is for chrlauncher, but you can easily modify it for use with your Chromium Portable.
Where is exactly?
Also I've checked the HTML5 audio/video tester and found out that sample_100kbit.mp4 with MPEG4 video does not show that video for me, though audio is fine. Is that expected?..
Btw my bookmarks, passwords and the rest seems to be syncing on Windows anyway.
Is it only a my problem?
Thanks
https://github.com/megous/megatools
https://github.com/t3rm1n4l/megacmd
https://github.com/Akujin/chromium-disable-profile-button-patch
Personally not really looking forward to maintaining OS X and Windows build environments just so I can have a browser configured to my preferences. Any chance you might wanna have a specialized build released?
@956: chrlauncher is not my project, but try to look into the "chrlauncher.ini", there must be an option somewhere
If I add PepperFlash these builds simply are not performed: why?
Codecs contain PepperFlash?
choco install flashplayerppapi
1. command line switch (and)
2. the files for run Pepper Flash portable (pepflashplayer.dll, pepper.vch, manifest.json and mms.cfg)
The only Chromium portable that allows to run both: builds with codecs+sync and Pepper Flash portable is X-Chromium by winPenPack: the only tip is to update the Pepper Flash version number in the file 'X-Chromium.ini', [FileToRun], row 'Parameters'.
Others portable Chromium (by PortableWares or by Aluisio Augusto Silva Gonçalves) can only run Pepper Flash portable or builds with codecs+sync.
b.t.w. for non english users the 'sync' feature allows to use Google Translate.
@nik: Your builds are solid rock.
I think h265_10bit also must work
ps. h263, ac3, mpeg1/2 doesn't work and i don't now how to enable it (maybe it's for the best)
@969: Please read my #comment-238
@965: There is already a Chromium version and it is official.
"I made patch to get rid of the profile selection button in the title bar..."
On 25 Feb 2016, 20:32 nik said:
"I'll try to add this to the nosync build..."
That would be so awesome! Nobody likes that button there. Even people who actually use it think it should be in the hamburger menu rather than taking up valuable real estate on the tab bar.
Please, please do this... That useless button is the bane of my existence
And thanks (sincerely from the bottom of my heart) for all the work you do. Legendary!
Idem about \angle_deqp_libgles3.dll and \angle_deqp_libegl.dll
Nice and clean now (just like it used to be before someone got a stupid idea)...
I don't know what would make them think they should add something like that there without any option to hide it. It's our browser... we should be able to have it look and work the way we want.
I was almost ready to jump ship. Now I don't have to.
May I ask: Is it possible for someone like me to change the bookmark star graphic found in the address bar? Or how about the corners of the tabs... Can I square them off?
Thanks again sir
here is source and build.gn script https://chromium.googlesource.com/chromium/src/+/master/ash/resources/
maybe if you understand how it packed, you can create your own *.pak file
@Jerry: Thank you for this site
Greetings from Germany
BTW, this is the 32-bit Chromium Continuous build that I've installed in Windows Vista 32 bits, directly from the buildbot sources
Disable (default=Enable or Disable?)
Enable this flag "chrome://flags/#disable-direct-write" to Disable?
@eliotime3000: Check your mailbox ^^
@Illite Racy: By default, DirectWrite is enabled.
https://bugs.chromium.org/p/chromium/issues/detail?id=25541#c146
ps. chromium 49 build doesn't support h264-10bit and h265 at all because of ffmpeg version
@Jerry: If you don't mind me asking, I am very curious as to whether or not the Chromium builds with Codecs from @nik have created an increase in traffic to your site. The download numbers, at least according to the previous RGhost, were interesting to follow to see which builds users preferred (with / without codecs, with / without Google API, Portable, etc.). Some of those generated pretty decent download numbers. Statistics, I find, are quite interesting and fun. Cheers, and best of luck! Thank you for providing the wonderful platform here.
Also I'm often getting ERR_SSL_PROTOCOL_ERROR even on internal VPN resources, now trying the solutions from www.techfor.us/2015/10/err_ssl_protocol_error/ - did not get one since applied everything except 1st advice.
@gwindlord: Thanks for your feedback but I do not know how to resolve your SSL issue.
@Empol: Follow the nik tutorial at #source-code
In Webupd8 shows a tutorial of how to set-up the repo for those that use the 64-bit version of Chrome
http://www.webupd8.org/2016/03/fix-failed-to-fetch-google-chrome_3.html
Does these stable version communicate with Google backdoor servers?
I know there's also a guide made by him on how to make our own builds but due to lower HDD space and slow internet that is a no go for me.
@1003, @John: Use an online service like Jotti or VirusTotal. I put links in the #malware section.
Another question: nik's builds are different from the ones @rbon posted or they're the same? I assume they're the same, only difference is that the updater now has the option to download the unofficial builds, right?
Is it Archive version actually portable ?
Now that is some great teamwork, guys!
Over the past 6 months or so since using the wonderful information resources here at Jerry's site, I have also come to enjoy and appreciate Henrypp's chrlauncher because it is open source and does a great job of finding/downloading Chromium builds and also making it all portable. Then comes along nik's fabulous Chromium builds (Stable and Dev) with codecs and prove to be great compilations. Combine all of those resources together, and being able to use chrlauncher to download/update nik's builds, with downloads coming from Github now, and ability to make things portable if need be, that is truly wonderful reality of great things coming together to become greater.
Question: I know that Henry++ is trying to collect donations to digitally sign his software which would be great. But what I'm wondering is, if he receives enough donations, if in collaboration with nik, if it would be a future possibility to some day have Chromium builds also digitally signed?
Thank you all for the great collaborative effort and time.
Saturday, 19 Mar 2016; 51.0.2685.0 (382185)
checked correct SHA1
Run, but the pages load in a permanent, independently, page setup program or web page.
In debug.log:
[0321/030227: ERROR: main_dll_loader_win.cc (123)] Failed to load Chrome DLL from C: \ Users \ 1 \ Desktop \ chrlauncher \ bin \ chrome_child.dll: A problem has occurred in the program initialization, dynamic-link library (DLL). (0x45A)
Out of your builds only worked 49.0.2623.75 (x64, nik with all codecs), regardless of whether anti-virus enabled or anti-virus off.
The rest of your build (nik with all codecs, x64, sync/nosync) not work independently of antivirus.
translation google.translate xD
https://www.chromium.org/getting-involved/download-chromium
• https://bugs.chromium.org/p/chromium/issues/detail?id=407399
• https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/lKLCCjKjvJc
> http://chromium.woolyss.com/download/ are still from 18th...
These builds are official but the builders are dead. So there is actually no update. See my #comment-1019 for the official explanation.
• https://storage.googleapis.com/chromium-browser-continuous/index.html is also not updated.
• https://download-chromium.appspot.com/?platform=Win&type=continuous is also not updated.
> ...but the ones with codecs are more recent
These builds are compiled by nik, our devoted developer. They are not official.
Note you can compile your own Chromium version yourself if you prefer. Follow the nik tutorial on #source-code
I think I may have found an active source of Windows x86 builds for now:
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/
(there don't seem to be any Windows x64 builds, unfortunately)
Buildbot status URLs:
https://build.chromium.org/p/chromium.win/builders/Win+Builder
https://build.chromium.org/p/chromium.win/builders/Win+x64+Builder
URL traceback for reference:
https://build.chromium.org/p/chromium.win/console (scroll down and look for green boxes, hover over each box to see what it corresponds to, and click to show a popup. The last entry in the popup redirects to one of the above URLs)
https://chromium-build.appspot.com/p/chromium/console ('Chromium' line -> 'Win' link in table 'Tree closers')
I'm not sure if you are already aware of this, but I'm posting it just in case.
Thanks again. :)
@1024: Sure I know these builders. They compile automatically Chromium and put binaries in "Snapshots" repository. But here, we talk about "Continuous" repository and its relative builders. Please, read the #development process to understand the difference between "Snapshots" and "Continuous" repositories. Note "Snapshots" builds are very unstable.
https://chromium.googlesource.com/chromium/tools/build.git/+/ffe53a8970e65115b9d1721b46930f157302f0ee
So, according the posting, the continuous builds (LKGR) are no longer being created?
Wow. If this is the case we are stuck with the snapshot builds :(
LKGR builders: https://build.chromium.org/p/chromium.lkgr/one_line_per_build
Latest LKGR commit: https://chromium.googlesource.com/chromium/src/+/lkgr
So FreeSMUG (Mac) and nik (Windows) continue to compile and share their own binaries ^^
For the rest, wait 'n' see! ;)
I have just downloaded the snapshot build 383400 and it is functioning perfectly, no bugs (for me, anyhow).
One thing I have noticed though is that many months ago the site-permissions-details tab info was removed from the address bar right click menu on the continuous builds, but in the snapshot build it is present:
• only these builders are removed. They also compiled Chromium (executable + archive) → Continuous repo.
• but other LKGR builders work normally. Check my #comment-1030 to see the list of active LKGR builders and latest LKGR commit. These builders do not compile Chromium.
Finally, developers can always compile Chromium. That is why there are STABLE and DEV Chromium versions updated on this site ^^
Sorry, I cannot help you on Snapshots builds. There are too unstable.
I'm just a normal user who is grateful for your work, thank you!
I was wondering if you can make a simple installer for Chromium so that we can choose to install Chromium for all users.
I could barely found this website where's a good explanation how you can do that martin.rotterovi.eu/2014/06/chromium-windows-all-users/
Using the command line to choose an option in a graphical program can be done but is not an easy thing for most users and I'm pretty sure Google devs will never add this since they care only about Chrome and like to treat the user as a stupid person who doesn't need to know these things and should not be allowed to choose for himself if he wants to install for the current user only or for all users.
I think they believe that adding this feature to chromium will threat their Chrome market share since more users will easily jump ship to escape the crap Google puts in Chrome.
It's clear that they understand very well that there's no point to install a browser on a multi user OS and keep it for the current user only and they "fixed" this behaviour only in Chrome to keep it as advantage compared to the free version.
If you can and decide to do this, maybe you can add a field where you can choose the location too.
I normally install it in the default location and don't need this, but it's always good to have a choice.
@Daniel: I understand your suggestion but we will not add this feature because it already exists in command line. Sorry.
@Peach: I checked each "Archive" link. All works perfectly. Do you use a proxy/VPN with a limited bandwidth?
All info are fake and there are ads.
Today, I made site-archives of this page to prove my point of view:
- https://archive.is/EL1OD
- https://web.archive.org/web/20160330222545/http://telechargerchromium.com/
Example with the 32-bit Chromium version:
On the crappy site, you see:
Windows (ZIP) - Version 51.0.2694.1 du 30/03/2016 → storage.googleapis.com[...]chrome-win32.zip
Download is good but the rest is not correct at all!
Official info:
Revision: https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/382014/
Date: Friday, 18 Mar 2016
Version: 51.0.2684.0
Commit: https://chromium.googlesource.com/chromium/src/+/8f5eb4c1ae4cfea73a9886f6e4cc361e5373a5ab or http://crrev.com/382014
Download on official site: https://download-chromium.appspot.com/?platform=Win&type=continuous → Revision 382014
Search the LAST_CHANGE file in https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win/ → Revision 382014
Thank you
@1043: Most computers come with a 64-bit processor for few years. Nik does not compile 32-bit Chromium version. But if you want to share your own 32-bit builds, you are welcome! ;)
@Jerry: yes, but lot of users have only 32-bit like me. If I have good English and a 64-bit OS, I will do with pleasure ;-)
On all other builds I've used it functioned as usual
- nosync build doesn't have a Google api => no translate function.
- in sync build, all works
I already set "Automatic tab discarding" to Disabled in chrome://flags
but, no problem with "Automatic tab discarding" on nik dev no-sync build.
Hotword (incl. Shared Module)
Google Now
Google Feedback
Cloud Print
Google Webstore
Network Speech synthesis
Google Hangout
@1052: I don't know how :)
@Ayup: It's quite a lot of work, I'm not ready for this. But hotword and Google now disabled in nosync, hangout doesn't work also because Google api keys is undefined.
Under the section "Get PepperFlash (PPAPI)", could we add an option to install via chocolatey:
cinst flashplayerppapi
I just want to inform you of something, not sure if it's helpful, but I'll post it anyway...
I've just reinstalled Windows 7 x64 and installed Firefox and Chromium version 49.0.2623 of nik all codecs with no sync, no WebRTC
I learn some foreign languages on Duolingo.com
I tried Firefox first but it didn't work since Duolingo still requires flash for mike input, I don't want to install flash on my computer and I gave up on Firefox.
Then I tried Chromium and on mike input page, Duolingo failed without any error message.
I gave it before access to mike so it's not this (Duolingo complains anyway when doesn't have access to mike).
I took a look at html5test.com to check if the WebRTC missing is the problem and it showed Peer to peer section 10/20 (yellow color)
Then I uninstalled it installed the other version that doesn't show with no sync and noWebRTC and Duolingo worked fine.
I took a look again at html5test and the Peer to peer section now showed 15/20 and the only difference was that "Data channel" changed from "No" to "Prefixed"
That's all, I just wanted to tell you what for stubborn enough people not to use flash like me, there's a problem with the NoWebRTC version on this particular website.
Have a nice day.
@1061: Read at the top of page about "LKGR builders" :)
I have downloaded latest DEV version 'No WebRTC • 52.0.2705.0 (386294)' then I have browse to the site https://www.browserleaks.com/webrtc
This is the site answer:
WebGL Support Detection
Is WebRTC Enabled ! True
Where am I wrong ?
So I have tried Firefox Portable (PortableApps) and go about:config then ' media.peerconnection.enabled' and changed from true to false.
I have load again https://www.browserleaks.com/webrtc with Firefox and this is answer:
WebGL Support Detection
Is WebRTC Enabled × False
Any idea ?
There is the 'Peter Beverloo' site with all command-line switch for Chromium at https://peter.sh/experiments/chromium-command-line-switches/
In effect there are many command-line for WebRTC.
It's snapshot ?
• "Last Known Good Revision" (LKGR) → Continuous
• "Latest" → Snapshots
@1068: The problem IS NOT about commit/revision number. Like you, we know how to get it. For example, Nik compiles the latest LKGR build (#windows-64-bit-dev-nik) and other developers do the same thing on Linux.
The problem is about TESTED builds and auto-compiling of binaries (.exe or .zip). Since 18 March 2016, these binaries do not exist. The repository (Continuous by default) is not updated... but LKGR builders work prefectly: https://build.chromium.org/p/chromium.lkgr/builders
Do not use Snapshot builds for web browsing. They can be very unstable, They only exist for testing, for developers. More on #development
I have been using snapshot build 383400 (win x86) for 15 days. Functioning perfectly with no problems whatsoever.
@_M_: I agree with the mention "It may be tremendously buggy" at the official site https://download-chromium.appspot.com/ So use Snapshot builds at your own risk ;) I encourage you to check buildbot result at https://build.chromium.org/p/chromium/builders/Win and copy your user data before to install a new one.
I thought Nik's is refinement (no No sync • No WebRTC) of the latest chromium released.
Nik DEV is on 52.0.2705.0 (386294) - Should be tested and safe right? Just curious :)
Anyhow thanks Nik... all good so far for a light user who appreciate the 'extra security feature'
Thank Jerry for your awesome work here as always.
About safety: yes, Nik builds are safe. Note Nik shares his guide to compile 64-bit Chromium yourself (see #source-code). You can also use online services to detect #malware and reliable sites to do privacy #tests
The direct link to the build is https://storage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/350186/
Thank you.
@1083: Sorry, Nik does not compile an outaded version. So if you want to build your own version, compile it yourself. Follow the Nik's guide at #source-code part.
• with VS 2013 (before 11 March 2016):
https://chromium.googlesource.com/chromium/src/+/c80526b8ba29a72abe4bee22d1351a1798dd87e0/docs/windows_build_instructions.md
• with VS 2015 (current):
https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
I found the information at https://github.com/Akujin/chromium-disable-profile-button-patch but I am not able to do it.
- for stable build, it is here.
- for nightly build go to https://www.chromium.org/getting-involved/download-chromium
As it turns out, the issue also affects openload as well. I don't think it's Flash.
@1qqu: i check it, and with they js script it's broken for me too, but if you open the video stream directly you can use seek. After investigation i notice that the video size detected as -1, so that's the problem
Is it possible for you to also provide download link to the same build of x86 mini_installer/Chromium Authors?
For eg. I can't find--even using Google Omaha Proxy--the 50.0.2661.94 (378081) build for x86.
Or maybe you can ask nik to just provide the download link--not the x86 build?
Regards,
Thanks so much! Love using this site! :)
This is the target line: "C:\Program Files (x86)\chrome-win32\chrome.exe" --disable-reading-from-canvas. To verify if canvas reading is disabled check via https://www.browserleaks.com/canvas
https://bugs.chromium.org/p/chromium/issues/detail?id=584575
It suggests Chromium binaries can be compiled with Visual Studio 2015 using the additional "/guard:cf" flag.
Anyway, this would be another positive feature for your builds as long as compilation is successful and functionality is stable with minimal performance overhead.
Keep up the great work as always. Thank you for your time.
However I did install the CanvasFingerprintBlock extension and that seems to be a good workaround.
Two more questions:
- Why is there a still an "Update Extensions now" button under the Extensions menu when we still have to update Chromium extensions manually? Or was I misinformed?
- Will there ever be an updater for the Chromium browser as a whole for Windows? Both portable and native? My understanding is the Apple version already has this.
Thanks
@WildByDesign: i didn't find any option about guard flag, only CFI but it's for clang compiler, so we must wait when Google add CFG to chromium
you need latest visual studio + 64bit windows + some knowledge in c++ (if you get some errors)
Can anyone confirm?
It's such a universal command, why change it now?
For more: https://bugs.chromium.org/p/chromium/issues/detail?id=608016
Very good builds.But I can no longer sync my google content although right email and password provided.
Please help me.
thanks.
Can't access "About Chromium" in the new build (sync) and get the above message.
@WildByDesign: Thank you very much. We are honored ! Have a nice WE too!
I see you support us at https://www.wilderssecurity.com/threads/your-web-broswer-chromium-choice.382947/page-2#post-2557411 ;)
But you can:
- use an extension for translation.
- or use the Chromium build with "Sync"
- or compile your own Chromium version.
Finally figured it out- problem with my Google API key. Set it up properly and all translation issues are resolved.
Yes indeed, the translation works in this build. Thank you for helping to understand what was happening. Now everything is clear. Good luck.
How can you fix it?
- You can re-download the DEV version.
- or if you use chrlauncher, delete the "bin" folder and relaunch it. It will download the DEV version.
btw in my win7 i didn't see this black screen. what if you try a clean profile?
setx GOOGLE_API_KEY "no"
setx GOOGLE_DEFAULT_CLIENT_ID "no"
setx GOOGLE_DEFAULT_CLIENT_SECRET "no"
Alternatively, you can set the variables through System Properties. Under the Advanced tab, there is a feature to edit environment variables. I suggest setting them as user variables for your active user account, though I suppose you can set them as system variables for a multi-user system if desired.
- the developers have solved (I think) the conflicts with DNS: browser start very fast and surfing is very fluid
- the service Translate is disabled (again) and if You use 'Google Translate' from Chrome Web Store https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb it does not work well. You must manual select the language for translated page.
I will wait for the next build.
Thanks for your precious work.
- A bash script: https://github.com/mloporchio/chromium-downloader-script
- A C program, based on libcurl: https://github.com/mloporchio/chromium-downloader
Thanks for your great website.
@srgrass: Chromium is a fully open-source project.
• The Google-authored portion of Chromium is released under the BSD license:
https://chromium.googlesource.com/chromium/src/+/master/LICENSE
This is a standard licence. For more, read https://en.wikipedia.org/wiki/BSD_licenses
• The other parts are subject to a variety of different open-source licenses:
- in your browser: chrome://credits
- online: https://cs.chromium.org/search/?q=licence&m=100&sq=package:chromium
Detection:TR/Egguard.Gen (Cloud)
Source:\chrome-win32\chrome_elf.dll
I'm using (thanks!) Nik's 52.0.2743.82 (394939) stable build (No sync, No WebRTC, No Widevine) and some chrome's internal pages (chrome://memory-redirect, chrome://memory, etc) don't work anymore: Is it only my problem? Thanksssssssss!
Anyway, thanks nik
There are most Dev versions and all are 'No sync, No WebRTC, No Widevine' except '..dev_nik_sync'.
Good luck.
1. CentBrowser code and privacy policy
Closed-source. No privacy policy about their OWN browser. No wikipedia page.
So, who do this browser? and which privacy policy? The Google Chrome privacy policy - https://www.google.com/chrome/browser/privacy/ - focuses ONLY on Google Chrome, not CentBrowser or other Chromium-like browsers. CentBrowser is being closed-source, I do not trust in their privacy policy. And browser user agent is the same as Google Chrome.
2. CentBrowser update
Browser is up-to-date today. Good point... but until when?
https://www.centbrowser.com/history.html
3. CentBrowser settings
Sure, its settings are very interesting. Mouse gesture, Tab options, Privacy....
4. CentBrowser official website
- I see it is an amateur site.
- Site should be nicer → A web browser is in the technology domain ;)
- Site stores Chrome third-party addons → Not legal and secure!
- Official contact is a simple Gmail mailbox → Not really serious!
- The chrome://contributors/ page displays more media reviews than contributors.
Use it at your own risk! ;)
My site archives ^^
- https://archive.is/www.centbrowser.com
- https://web.archive.org/web/*/www.centbrowser.com
- https://web.archive.org/web/20160810112532/https://www.centbrowser.com/appcenter.html
Wasn't able to find a Super Drag extension that does the same thing a centbrowser/CoolNovo was capable of...
I got a old win32 version of chrome in c:\program files(x86)\win32-chrome\chrome.exe
for which I got a shortcut on taskbar with some convenient commandline parameter.
I tried all the versions provided : chrlauncher (you really should explain what is it and where it is supposed to be installed) no luck,
installer : no result (no message when launched on commandline).
Eventually copying the archive in the existing directory seemed to do the trick.
But when I launch it, the url bar produce no result (stalled).
I killed the process and relaunched it and now and now it (kinda) work.
Even if now I got 2 chromium instances listed when I need to choose a default program for opening *.html
So I appreciate your effort but I think the chromium installation process is still a terrible mess and definitely not for newbie
and it's a pity
only 52.0.2743.116 by NIK work fine
can i use pepperflash plugin without chrome command line and adobe installer, somethings in flags maybe can help?
@Andy: i check it, and for me even official chrome canary has this problem. But if you open embeded video, it work. Something in parsing component with chunked video
utility v8 proxy resolver
any info about this?
This site can’t provide a secure connection
[site.com] uses an unsupported protocol.
ERR_SSL_OBSOLETE_CIPHER
DETAILS
Unsupported protocol
The client and server don't support a common SSL protocol version or cipher suite.
I am asking because few month ago there was google API with sync etc in builds from official chromium repository.
@1222: Which website? Did you test it in another web browser?
For details about your issue:
- https://bugs.chromium.org/p/chromium/issues/detail?id=619194
- https://chromium.googlesource.com/chromium/src.git/+/b4c25b632a7078d2c3346a37b51034bb853b24b3
- https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/ShRaCsYx4lk
@Ghost: There was Google API few month ago... but now, Google API keys are missing. So, you cannot sync your data. I recommend to use Nik builds with "Sync" (#windows-64-bit) or compile your own version yourself. Info at https://stackoverflow.com/a/24274934 and https://www.chromium.org/developers/how-tos/api-keys
Is it possible to always include the last release of the previous version whenever a new major version is released? For example today when the major version 55.x is released, we can still download the last latest 54.x released (just one latest last build).
I tried but unable to find the download link in the "Chromium storage".
Thanks
The "Chromium storage" concerns only official builds released by the Chromium buildbot (info at #development). Nik builds are not stored over there.
Sometimes Chromium is trying to contact the domain 1e100.net with various urls, so is there a way to block this behavior ?
Thanks.
I have discovered that Chromium support TLS 1.2 on HTTPS connections.
- TLS means Transport Layer Security on Wikipedia https://en.wikipedia.org/wiki/Transport_Layer_Security
- Enable TLS 1.2 on Windows 7,8.1 (and 10) http://blog.wisefaq.com/2014/09/22/enable-tls-1-2-on-windows-7-8/
- online free check of 'Cipher Suites Supported by Your Browser' by University of Hannover (DE): https://cc.dcsec.uni-hannover.de/
(see in this page 'Further information' of User-Agent: Mozilla/5.0, Chrome/55.0.2842.0 Safari/537.36)
This means that TLS 1.2 is enable by default on Chromium ?
I have see this post on 'Information Security', but it is not clear. https://security.stackexchange.com/questions/120777/chrome-50-where-can-i-see-the-negotiated-cipher-suite
Previous ciphers is supported, and obsolete ciphers is blocked in browser. If a remote site is support tls1.2 then browser use this cipher, if the site support only tls1.1 or lower then it's okay, if the site supported SSL3 and not any TLS then chromium (chrome) show error.
Pepper Flash portable 23.0.0.151 (latest beta of august 24, 2016) works fine.
@Lyam: > Sometimes Chromium is trying to contact the domain 1e100.net
https://support.google.com/faqs/answer/174717
Check answers at https://superuser.com/a/883591. For more, you can inspire you from the scripts of these free and open-source #browsers: Inox Browser and ungoogled-chromium.
It has been noted that with M53, 64-bit builds, that Google has started to compile their Stable branch build with a PGO (Profile-guided optimization) flag in their compiler and apparently that optimization will come to x86 users with M54. Anyway, it has been said that the PGO has created some notable performance improvements. I have not confirmed the performance myself, just simply going by what some Chrome devs have been stating. Do you enable this PGO flag within your compilation or, if not, do you have plans to include this in future builds?
Thank you for your time.
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta
That version is Chromium v54.x branch. My question was that can we get something like that made available on Windows? So far we only have Stable or Dev branches. It would be nice to be able to 'sync' the major versions of Windows and Linux Chromium to more easily sync settings from one to the other.
I would use Dev branches but they've been completely unstable lately (for me) so I stick with Stable branch for now.
contribute what you have, if whatever way you have. I have never regretted telling someone exactly what they should put in the command-line or branching out some new set of updates on some forgotten custom firmware on some shitty device.
@WildByDesign: so.. i can't compile with PGO, my system is just not enough.. the compile time is increased to 2-3 times, and free space is needed not 20GB for each build, but 90GB+.. and when i got to the linking chrome_child.dll, this single process has passed 13GB of ram and i got an error with "not enough space"! :)
I mean "not enough memory" :)
Again, thanks for your amazing work. Is there anywhere I can donate?
About donate: i didn't expect this question.. i have a paypal account https://tinyurl.com/nik-paypal
@RobRich: ok, so you must add this options (i use GN build system)
is_official_build = true
full_wpo_on_official = true
chrome_pgo_phase = 0
then compile,
then change "chrome_pgo_phase" to 1 and compile again
then change "chrome_pgo_phase" to 2 and compile last time.
Here is more information https://msdn.microsoft.com/en-us/library/xct6db7f(v=vs.100).aspx
Waiting on the source code download right now, as I cleared out my old depot_tools directory and started over. Needed to finally get around to updating Windows to the anniversary release, Visual Studio to 2015u3, etc. as well. Took awhile. ;)
Been a few months since last building Chromium. Fingers crossed.
But: .116 works fine on my desktop. It just refuses to work on the laptop. Odd.
I have a computer at work with 8GiB of RAM and since I use Visual Studio for my job I often find myself strapped for memory. I would ask my boss for an upgrade but it might not be a good enough reason seeing everyone else doesn't have the same issue.
Would it be possible to make 32-bit builds available? I don't have a machine with enough umph to do it.
i didn't see the difference in speed vs regular build, and in addition this require 22gb memory free (in my case) while compile :)
@1257: with 8GB of RAM you can easily compile 32-bit version.
@Jason: yes, they're all with hardware acceleration, it's by default.
FWIW, users can check if their build is PGO by going to chrome://version, at the very bottom will be the PGO tag, example: MSVC 2015 (PGO)
Quote from: https://randomascii.wordpress.com/2016/03/24/compiler-bugs-found-when-porting-chromium-to-vc-2015/
"Profile Guided Optimization uses profiling information in order to generate better code. It can give great performance improvements but it’s scary because minor changes in your training – the stage when profiling data is gathered – can affect the generated code. This means that your builds are not entirely deterministic."
So apparently the "training" stage of PGO compile can really make (or break) as far as performance goes. Minor adjustments there can create even worse performance and therefore I assume there must be some magic involved with finding the sweet spot.
- I have not seen any difference in performance (minimal) with regard to application startup time using PassMark's AppTimer (https://www.passmark.com/products/apptimer.htm)
- I have not seen much difference with regard to JavaScript performance using Google's own Octane (https://chromium.github.io/octane/)
- However, I have consistently seen increased performance of actual web browsing using the Chrome extension Performance-Analyser (https://chrome.google.com/webstore/detail/performance-analyser/djgfmlohefpomchfabngccpbaflcahjf) and these results have been reproducible each time. The actual "feel" of web browsing in general has improved as well. I don't know that I would say that it's up to 15% perf improvement as some Chrome developers have stated, but it is a noticeable and appreciable performance improvement and certainly worth while.
So the bigger problem here is hefty hardware requirements for the builds machines and longer time to build. Does anyone know what a minimal cost might be to rent and run a buildbot server to help automate the compilation of Nik's builds? Depending upon that, I am wondering if it might be worthwhile to setup some sort of donation option to assist Nik, Jerry, Henry++, and this community in general.
As for PGO here, I am at a roadblock. AFAIK, I need src-internal for an "official" build, right?
As always, thanks for the hard work on the Chromium builds! :)
@WildByDesign: I opened a #donation part (on the right-hand side). Big thx2u!
@RobRich: If you want to share your own Chromium builds (under a free licence), contact me! ^^
What really blew my mind the most is that I had the PGO build running just on SSD initially, whereas my daily driver non-PGO Chromium runs from RAM disk. So PGO build ran faster and snappier in comparison to non-PGO build which was running within much faster RAM disk. Now I have the PGO build running from RAM disk as well and it is literally lightning-fast. All I can say is that, without a doubt, PGO compilation is the way to go. Nik has hit a home run with this PGO build, for sure.
An important note regarding PGO: EMET breaks PGO. So for any users who use EMET to protect their chrome.exe processes, it has been confirmed that EMET breaks PGO. Chromium team advises against protecting Chromium with EMET anyway. Personally, I just use EMET for it's system-wide mitigations and not so much for it's per-process mitigations.
@Nik, If all goes well with your PGO compilations and as long as you feel comfortable with it, would you be willing to re-compile the current Stable branch build? Sync or No-Sync, it doesn't matter too much either way. Thank you, sir.
However—I am someone who often uses a browser for days on end without closing it, and the PGO build began to have issues after long term usage. Random pages would experience a variety of problems—not loading any images, frames being gone, plug-ins no longer interacting with the page requiring reopening in a new tab, etc—which were not being experienced in version 55.0.2861.0 that I ran at the same time for comparative purposes. Now it's possible these issues are not related to the PGO compiling itself, and instead are related to the build bump to 55.0.2863.0, but just in case it was PGO related, I thought I should mention it.
With the above said, I look forward to trying the next PGO build to see how things progress, and thanks so much to Nik & Jerry for all their efforts here.
@Jason: Should not need a special build for hardware canvas and compositing. Hardware rasterization on Windows can be a YMMV depending upon hardware and drivers, though.
Do you have GPU log messages? Go to the chrome://gpu page in your browser, and check the feature status and log at the bottom of the page.
I suspect you likely have a driver compatibility issue, such as your GPU driver not (yet?) being whitelisted by Chromium. To determine, you can try enabling "Override software rendering list" via chrome://flags, restart, and again check the GPU page. If it works, you might still need to manually disable "GPU rasterization" in the flags if page rendering appears broken for you particular config.
Chromium: 55.0.2866.0 (Developer Build) (64-bit)
Revision: 3ce23fa6daab8fd4feb93e5d8bdd688f71e007bc-refs/heads/master@{#419561}
Compiler: clang
Linker: lld
----------------
@1257: I suggest just using the already available 32-bit master snapshot builds, but anyway, here is a 32-bit LKGR build if desired.
Chromium: 55.0.2866.0 (Developer Build) (32-bit)
Revision: 3ce23fa6daab8fd4feb93e5d8bdd688f71e007bc-refs/heads/master@{#419561}
Compiler: MSVC 2015
I dunno why, but SYNC version was compiled with errors again, so only nosync for now :)
Disabling sync and/or webrtc could be a workaround to lower file sizes during linking.
I know disabling webrtc is a build arugment. I am probably missing it, but how is sync disabled?
Also, if you do not mind, what are your particular build arguments?
I've patched some BUILD.gn files for webrtc in nosync, because even if you disable it through args it will be required.
And my args for sync:
current_cpu = "x64"
enable_google_now = false
enable_hotwording = false
enable_iterator_debugging = false
enable_nacl = true
ffmpeg_branding = "Chrome"
is_debug = false
is_win_fastlink = true
proprietary_codecs = true
symbol_level = 0
enable_iterator_debugging = false
target_cpu = "x64"
enable_widevine = true
remove_webcore_debug_symbols = true
is_official_build = true
chrome_pgo_phase = 1
I figured you might be patching the build files. I will retry PGO building later if/when the file size limit during linking with sync enabled is ever resolved.
----------------
Took a quick look at my recent builds. Appears linking is failing when WPO is enabled - a requirement for PGO. Hmmm.
On another front, today I rolled another clang + lld build for Win x64 with surprisingly decent results. No stability issues (yet?) to note, and general performance is comparable to generic VS builds.
Chromium 55.0.2868.0 (Developer Build) (64-bit)
Revision 6ed8696692c33df85a9d85aa4c3cf34347b9dae3-refs/heads/master@{#420048}
Compiler clang (+ lld)
Someday I might eventually get around to a github, sf, or similar account for hosting clang+lld builds.
is clang+lld required more memory or less?
ps. it's only two, content/renderer/BUILD.gn and chrome/browser/extensions/BUILD.gn:
target(link_target_type, "renderer") => source_set("renderer")
static_library("extensions") => source_set("extensions")
About memory, IIRC, clang+lld rarely went over a few GB when building. I will take a closer look next time I build with them. I can note clang-cl is somewhat slower at compiling than VS 2015u3, but it is still reasonable enough IMO.
Chromium 55.0.2869.0 (Official Build) (64-bit)
Revision 1713992c55069cc914715dac18356a3eef774b8e-refs/heads/master@{#420488}
Compiler MSVC 2015u3
I will try to do a PGO build of the same version for comparison. I might trying using some of the telemetry tests for PGO instrumentation so I can standardize my local build process. Telemetry can also write results from multiple runs for a quick comparison.
@RobRich: I used your build yesterday and all seems to work nicely. No crash. Thanks.
I am working on hls.js library to enable HEVC. and all worked fine on EDGE but not on your chromium build. But MPEG dast HEVC is working fine in your build. So I need to add some logs to Chromium to find problem.
Can you show me live demo? I'd like to test it too. I remember that i have trouble with patching for HLS.
WPO: https://en.wikipedia.org/wiki/Interprocedural_optimization
WPO is not the last stage of optimization. PGO is a subsequent stage that analyzes the behavior of a running executable, offering additional optimizations.
A good explanation at https://msdn.microsoft.com/en-us/library/0zza0de8.aspx
Only the 64-bit version of Google Chrome is currently based on Chromium with enabled PGO.
https://bugs.chromium.org/p/chromium/issues/detail?id=629603
This is my hls.js demo and it is working find in EDGE, but it crash your chromium build..
http://vpn.mdragon.org:60080/hls_HEVC/demo/
and this is MPEG HEVC demo stream that works fine in your build :)
http://dash.edgesuite.net/dash264/TestCasesHEVC/1a/1/TOS_OnDemand_HEVC_MultiRate.mpd
https://github.com/henrypp/chrlauncher/issues/33
We will try to do something with them. But note that non official patches (like ungoogled-chromium set) are often outdated because the Chromium source code changes each day. For info, all #browsers (Comodo, Iridium, Brave...) oriented to the protection of user privacy are outdated. So there are more security holes. Personally, I prefer to use an up-to-date build of Chromium with good #privacy settings ;)
I say just continue what you're already doing, time better spent training PGO's. =D
on next/future PGO built - if possible can you include SHA1 or MD5 for us to verify the secure download on our end pls?
cant be too careful these days :)
also ON chrome:flags > Material Design in the browser's top chrome -
is the <non-material> option not available anymore on the new build 55?
how can I get it back?
any ideas? anyone?
Thanks again for your awesomeness Jerry :)
you can update pgo-test build to 55.0.2868.0, it's already with pgo and have sha1 hashes
https://bugs.chromium.org/p/chromium/issues/detail?id=648281
due to the change of UI the bookmark bar is kinda less space and ... well... just new and need to adjust new behavior
how little changes 'affects' our usual mode of reality :)
Awesome work and special thanks to you again for all your work and time @nik
Now I will try to find why HEVC don't work with my test stream :)
this is PGO and two mini_installer for non-PGO (to compare a performance)
Again, similar to before, there was little to no difference with regard to application startup time. However, when it comes to actual loading of web sites, the PGO build performed the best under every scenario that I have tested. Not once has the non-PGO build outperformed the PGO build. Therefore the results have been entirely consistent which is important for this to be worthwhile.
Even from a perspective of how the browsing experience "feels", the PGO build is super snappy. For example, clicking the New Tab button loads instantly with the PGO build, whereas the non-PGO build has a slight hesitation to the loading of the New Tab page.
@Jerry, Great to see Secure encryption status for your site. congrats!
Chromium 55.0.2875.0 (Official Build) (64-bit)
Revision 2db1fd0045d02143eccc3315a9d6f1344be1e7a1-refs/heads/master@{#421671}
SHA-1 dfa09bc55df018cc908d8dd6ac005ae5d9032568
WPO built without any source changes. PGO phase one built, but the resulting instrumented build hit runtime DLL errors again. Hmmm.
is_official_build = true
chrome_pgo_phase = 1
is_debug = false
target_cpu = "x64"
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
Last two times I did PGO=1 builds, I extracted chrome.7z to prep for pgosweep, but chrome.exe failed to load chrome.dll and chrome_child.dll.
"Chromium compiled by Nik with all codecs (online tester) and PGO enabled."
Is it worth it ? and is it not needed? cause they said that its discontinued..
@RobRich: Thanks for sharing!
@versapps: From now on, Nik will compile Chromium with PGO enabled because the web browsing is faster.
@1328: Chromium M36: check revisions between 261035 and 268656 at https://storage.googleapis.com/chromium-browser-continuous/index.html
@Lynx: If you talk about ungoogled-chromium, you can download releases at https://github.com/Eloston/ungoogled-chromium/releases. I do not know if we will apply theses patches: #comment-1310
@Jerry, Can you update the Stable branch box at the very top of your site to note that these Stable branch builds are PGO-optimized now? Similar to how you have added PGO-enabled to Nik's LKGR build section. Thank you for continuing to run a site with such a wealth of valuable information. The way that you organize this site is wonderful.
Admittedly, I usually just build off master, though I get why that is not a great idea for most users.
Speaking of builds, I just completed an updated build with clang+lld for evaluation if anyone is interested.
Chromium 55.0.2878.0 (Developer Build) (64-bit)
Revision 6e9e64a37187edb10c3f3951820dbbc3c0e555b2-refs/heads/master@{#422335}
Compiler clang (+lld)
@nik, I will look into the pgort140.dll issue for my next PGO build attempt. Thanks! :)
@jj, it should be easy enough. Ideally though, I need to setup a GitHub or SF account first instead of using Google Drive. I will try to take a look when I have some free time. Also, thanks for the interest! :)
FYI - note on top on #comment-1 from admin
hope it helps :) we appreciate their work and labour out of their time and willingness
Chromium 55.0.2882.0 (Developer Build) (64-bit)
Revision bf38f84e48cb98ffdb2a9437e280b0e925690340-refs/heads/master@{#423332}
Compiler clang (+lld)
The early 55.0.2875.0 PGO by Nik is so far the best performing PGO build for me
Love the Un-google Complie works awesome no problem at the moment...
Hope this build gets updated like other Chrome Builds!
Good Luck with your work NIK!
Cheers!
@Tonmarkum Same build as my last post in a ZIP archive as requested.
@nik: I'm using your PGO-dev build at the moment, can I just download your ungoogled-stable version and copy and overwrite all the files?
@RobRich: Thank you for sharing. Contact me if needed! ;)
@Lynx: Yes, nik plans to add the "ungoogled-chromium" to his builds.
@Tonmarkum: Yes you can. Also use chrlauncher to browse on several Chromium versions in same time! ^^
Note:
- Prefer the secure connection: https://chromium.woolyss.com/ (I will force it in January 2017).
- Now, there is a red padlock near each unsecured site/link.
security is too important not to be secure :)
the hearts of man has changed.... ALOT.... these days...
2017 already huh? merry christmas first :)
@nik your work is much appreciated and .... AWESOME!
user experience report : finally chose current no-sync stable pgo for me since it still has non-md
and its blazing fast and zero problems surfing in the eastland
ungoogle seems to work very well too but some website is 'blocked' and 'unaccessable' (not sure if due to law of the land)
lkgr was hanging abit (about 3 second freeze but not sure if it was my mechine setup and other security software measures)
@Nik Will there be an update of your guide for pgo and/or ungoogled building ?
https://github.com/RobRich999/Chromium_Clang/releases
@qq 7z archives are included with builds if you want to add to crlauncher.
@Tonmarkum ZIP archives included, too.
@Jerry You can add my clang+lld builds if desired for whatever reason. If you need anything particular, I can email you to discuss. Just let me know.
I downloaded the pgo optimized chromium stable version archive but it seems it won't save any passwords. This is a bug because i tried the sync and no sync version and both won't save any passwords.
Also how can I use the chupdater to update PGO Chromium ? I think that one only works with non-pgo because there is no flag on the command to choose PGO.
@Andrew: Try an older version:
https://github.com/henrypp/chromium/tags
> chupdater to update PGO Chromium?
Yes, Choose a build with codecs in the "chrlauncher.ini" file.
For info, PGO is not a flag. It is a compiler optimization technique, also used for Google Chrome, Opera and Vivaldi.
https://bugs.chromium.org/p/chromium/issues/detail?id=654397
@Andrew IIRC, I seem to remember something about passwords in the bug tracker over the weekend. Possibly related.
Thanks for trying to remove Google as much as possible from Chromium for increased privacy.
I've noticed something when I did a clean install of Windows 7 on my computer.
I have disabled all network connectivity (both wired and wireless) so I won't be bothered with automatic updates for Windows and other software before I have the chance to configure them as I like.
I have installed Chromium and started it but I was really disappointed about the startup time even thought my computer has a quad-core cpu, 8 GB or RAM and a SSD on SATA3.
I found it very weird that Windows showed the spinning circle for a few seconds after the Chromium window appeared until those thumbnails appeared on the home page, even though there was no network connectivity.
I am suspecting that it waits from something from Google or it sends something.
Maybe you could take a look what's going on there.
I wish it had just a completely blank page without anything on it like in the old days.
New tab seems to have the same problem but I have installed an extension called "Empty New Tab Page" which seems to help.
Thanks.
chrome.exe --homepage "about:blank"
With that line above it will open up a blank tab every single time you open up Chrome browser.
https://github.com/RobRich999/Chromium_Clang/releases
Specific compile arguments for builds are included via the args.gn (text) file available separately for downloading.
@Jerry I will drop ya' a line later this week. Thanks for the interest.
I use ungoogled-chromium for mac however it seems Eloston does not have that much free time anymore.
Could someone compile mac version from the v56 branch?
Thanks in advance.
In your experience and understanding, do you think that they are still far off from official release Chrome builds on Windows compiled with Clang/LLVM? Also, have you tried CFI within your Clang/LLVM Chromium compilations?
I know that they are working hard to smooth out CFI with regard to Linux, Android and ChromeOS. But I suppose what I am trying to get at is whether or not CFI is problematic with regard to Clang/LLVM and Windows Chromium builds or if it is possible yet. I always have a special interest in security mitigations and such, so this is interesting to me. And since you seem to have an interest in compiling with Clang/LLVM, I figured I should ask you for your opinion.
Thank you, sir.
That said, the MSVS linker should be be a viable solution for Clang with CFI for COFF binaries since it readily supports LTO.
lld ideally should be possible as well, but Chromium still considers it "highly experimental" on Windows, so a huge YMMV IMO.
It appears clang-cl does indeed support the -fsanitize=* option, though I am not sure if Chromium build files have explicit support enumerated for CFI on Windows. I will toss the build arguments in the mix to see what happens.
I will do the same for future builds via my GitHub account. Sound good?
It's all good now, thanks @RobRich
https://github.com/RobRich999/Chromium_Clang/releases
Couple of notes to "cover the bases:"
- chrome.7z will be the packed archive automatically generated by the build process and basically what mini_installer. exe actually contains.
- chrome.zip will be structured in the "chrome-win32" format like Nic's archives. Please let me know if there are any issues. Thanks!
Any advice my friends?
Note:
"GPU rasterization should only be enabled on NVIDIA Pascal and Maxwell, Intel Broadwell+, and AMD RX-R5 GPUs for now"
"VPx decoding isn't supported before Windows 10 anniversary update"
"Zero copy DXGI video hangs on shutdown on Win < 8.1"
"Zero-copy NV12 video displays incorrect colors on NVIDIA drivers"
1. Nik's Chromium versions archive (can be on other server) - it can be useful for example, for users which don't like DirectWrite (disabling it was deleted in version 52)
2. 32-bit versions of Nik's Chromium (not everyone has 64-bit Windows)
3. Chromium 49 with codecs (32 and 64-bit) - especially for Windows XP and Vista users
https://en.wikipedia.org/wiki/Clang
Clang is an open source solution versus the proprietary solution in Microsoft Visual Studio currently used for default Chromium builds on Windows. Chromium is compiled with Clang on various other platforms like Linux and Mac, and it is looking like Clang eventually could become the default compiler for Windows builds in the future.
PGO is an optimization technique used during compiling and linking. Clang builds on Windows are not using any form of PGO at this time.
https://en.wikipedia.org/wiki/Profile-guided_optimization
Currently, there is no specific advantage - speed, privacy, etc. - to using Clang for Windows builds IMO. It is more or less a curiosity for me, and a way to keep tabs on where the project likely will proceed in the future. YMMV.
----------------
If not using chrlauncher, I recommend using mini_installer.exe instead. It is a silent installer, so click and wait a minute or so for a shortcut to appear on the desktop. You can then simply use mini_installer.exe with each new build to quickly overwrite the existing installation. If you ever do need to uninstall a mini_installer.exe installation for some reason, Chromium is listed in the Windows app/remove programs list.
More on Control Flow Guard: https://msdn.microsoft.com/en-us/library/windows/desktop/mt637065(v=vs.85).aspx
Anyway, I've inspected a recent build (https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/425305/) just now with Process Hacker and chrome.exe and chrome_elf.dll do indeed have CFG mitigation enabled. I have also inspected the recent Chromium Authors build from front page here (56.0.2891.0 (425289, 004d271)) and confirmed that it, too, includes CFG. Good news.
However, I've checked Nik's recent lkgr build also from today (56.0.2890.0 (425052)) and it did not include CFG. So what I am wondering is whether or not this is something that Nik would have to add (/guard:cf) specifically during his compile time or if he would just need a slightly newer build.
@Nik, if you can achieve CFG mitigation similar (starting with chrome.exe and chrome_elf.dll for now) following the completed report (https://codereview.chromium.org/2412983006) or referencing MSDN CFG article (https://msdn.microsoft.com/en-us/library/windows/desktop/mt637065(v=vs.85).aspx) that would be solid security feature for your builds. And if you can achieve this on Stable channel build as well, that would be fantastic. If you can make this happen, I will send you another donation matching my previous donation to your paypal.
# Control Flow Guard (CFG)
# https://msdn.microsoft.com/en-us/library/windows/desktop/mt637065.aspx
config("win_msvc_cfg") {
# /DYNAMICBASE (ASLR) is turned off in debug builds, therefore CFG can’t be
# turned on either.
if (!is_clang && !is_debug) { cflags = [ "/guard:cf" ] ldflags = [ "/guard:cf" ] }
Build details:
Chromium 56.0.2891.0 (Developer Build) (64-bit)
Revision 42d201137bc43d262c2acd2e81083354900f0a22-refs/heads/master@{#425324}
visual_studio_version = "2015"
is_win_fastlink = true
is_component_build = false
is_debug = false
symbol_level = 0
remove_webcore_debug_symbols = true
exclude_unwind_tables = true
enable_widevine = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
I've just confirmed now that Nik's latest build (v56.0.2891.0-r425278-win32) that just came in now includes CFG mitigation. That happens to be a win32 build, but I assume that builds v56.0.2891.0 r425278 (dev) and newer now contain CFG mitigation.
I suppose the main question now for either RobRich or Nik, and since I am not a programmer myself, is adding CFG mitigation to chrome.exe and chrome_elf.dll something that is easy enough to backport to Stable channel release? I don't understand what went into that specific patch that went through within the last day which enabled CFG mitigation and whether or not it could be applied to Stable channel builds.
For anyone who is unsure what CFG is a mitigation that is an option with MSVC 2015 on Windows 8.1 and Windows 10, which I suppose is somewhat similar to CFI (control flow integrity) mitigation that is an option with Clang/LLVM compiler. Although as I understand it, CFI is supposedly better. I assume that Chrome team's longer term goal is to make Clang/LLVM (with CFI) compiler work better with Windows and drop MSVC at some point although that would likely be a year or more away.
0) compile with pgo_phase=1
1) run chrome.exe
2) open 5+ random sites in tabs
3) find every PID of chrome.exe with command line "*type=renderer*"
4) run "pgosweep /pid:XXX PATH/TO/chrome_child.dll PATH/TO/SAVE/chrome_child!X.pgc" (XXX - pid, X - counter from 1)
5) close chrome.exe and retry if you want to collect more data, but don't reset the counter
6) compile with pgo_phase=2... done
@WildByDesign: are you sure that my build have CFG? Because i see in this commit that "CFG supported on x86 and x64 >= Windows 8.1 Update (KB3000850)." and i have windows 7. But if this is true, than i think the next x64 build will be with cfg already.
Just did a current stable release build with CFG manually patched and enabled. :) As previously noted, the chrome.zip archive for my builds now follows Nic's archive format.
Chromium 54.0.2840.59 (Official Build) (64-bit)
Revision 94e94a4190c88509a70809864e3bb7c4f92c6901
- mini_installer.exe
- chrome.7z
- chrome.zip
Build arguments:
is_official_build = true
full_wpo_on_official = true
target_cpu = "x64"
is_component_build = false
is_win_fastlink = true
is_debug = false
symbol_level = -1
proprietary_codecs = true
ffmpeg_branding = "Chrome"
enable_widevine = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
----------------
@nic That is pretty much the process I have tried. I do remember assuming pgosweep.exe would take relative paths if in the same directory as chrome.exe, but perhaps it needs exact paths. Hmmm. Will try next time I give PGO a go.
Log Messages
[884:1176:1015/003307:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 345
[884:5560:1015/005200:ERROR:interface_registry.cc(102)] : Capability spec prevented service service:content_browser from binding interface: mojom::ResourceUsageReporter exposed by: service:content_gpu
[884:1176:1015/014132:ERROR:gpu_video_decode_accelerator.cc(370)] : HW video decode not available for profile 12
[884:1176:1015/014143:ERROR:mf_helpers.cc(12)] : Error in dxva_video_decode_accelerator_win.cc on line 1391
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
Driver Information
Initialization time 666
Do the errors persist after trying to disable hardware acceleration of video decoding in about:flags config?
Hardware-accelerated video decode Mac, Windows, Chrome OS
Hardware-accelerated video decode where available. #disable-accelerated-video-decode
Of the listed errors, the "HW video decode not available for profile 12" can be disregarded for now IMO, as it appears to at least be properly falling back to software decoding for the particular format. Hardware decoding support for specific formats can be based upon OS, GPU, drivers, etc.
Although I must admit, my preference is builds with Google API for Sync functionality for the most part. But I will stick with this build as daily driver for the time being because it's stable and has the additional CFG mitigation.
@Andreas: It is normal. Hover your mouse on "No sync" tag at #windows It says: "Google API key is undefined in this build. So Google services like Sync, Hotword, Translate, Now, Hangout do not work".
- STABLE: version as stable as Google Chrome.
- LKGR: #development version tested by buildbots.
- DEV (or snapshot, nightly): #development version NOT tested by buildbots.
Similar to CFI/CFG, that is spread across all platforms now. See: https://twitter.com/justinschuh/status/788408516180533248
Good news for performance and security.
https://github.com/RobRich999/Chromium_Clang/releases
Next on the build list is an updated Clang build and then 54.0.2840.71 with CFG. Should have those later today.
Current stable release build with CFG manually patched and enabled. The chrome.zip archive for my builds follows Nic's archive format.
Chromium 54.0.2840.71 (Official Build) (64-bit)
Revision da72f35322ead1e293d0414f5fe219647f3d7776
- mini_installer.exe
- chrome.7z
- chrome.zip
----------------
Updated Clang build now available.
Chromium 56.0.2898.0 (Developer Build) (64-bit)
Revision e2cf786bb19426e44fe22a36fb8d509ea04d1e62-refs/heads/master@{#426801}
Compiler clang (+msvs linker)
----------------
@Jerry I have not forgot about ya'. Just been busy on other stuff. Will drop a line soon. Thanks for the great resource provided here.
----------------
@Nic Thanks for the help. It appears I previously tried to profile chrome.dll instead of chrome_child.dll, thus the instrumentation error. I will try to cookup a quick PGO tutorial in the upcoming days, plus get my PGO build(s) onto GitHub.
btw whats cfg pls? whats is it for? just curious from non-tech person :)
My first PGO build for public release. :)
Chromium 56.0.2899.0 (Official Build) (64-bit)
Revision 516005ea9c2ffe59b5d468bf4673a549996010df-refs/heads/master@{#426972}
Compiler MSVC 2015 (PGO)
- mini_installer-pgo.exe
- chrome-pgo.7z
- chrome-pgo.zip (Nik's format)
For those interested, here are the PGO profiling statistics:
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
286 of 1319580 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
8657421 of 16073940 inline instances were from dead/cold paths
1319570 of 1319580 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
155104427740 of 155104427740 instructions (100.0%) were optimized using profile data, and the rest of the instructions were optimized without using profile data
----------------
@1457 Control Flow Guard is a security mitigation to help protect against buffer overflow attacks and similar exploits against memory allocation.
https://msdn.microsoft.com/en-us/library/windows/desktop/mt637065(v=vs.85).aspx
I think that it is a great idea to show what makes Nik builds special. Especially since Google's own Chrome browser does not yet have CFG for their stable channel builds. So currently Nik's stable (54.0.2840.71), LKGR (56.0.2897.0), and 32-bit LKGR (56.0.2899.0) all have control flow guard enabled.
Another possible suggestion here would be to make those tags so that you can hover the cursor over them for additional information similar to the info popup you have with No Sync - No WebRTC - No Windvine. So the user could hover the cursor over the pgo-optimized or control flow guard tags for example for a brief description of what it means and hopefully that will help prevent some repetitive questions from coming up in the comments section.
@1465: The patch to remove the profile button does not work on latest Chromium versions.
@Andreas: Google Translate works on STABLE version: Sync • WebRTC • Widevine • 54.0.2840.71 (414607)
Ex: Go to http://starin.edaily.co.kr/ → right-click in the page → Translate it in your language (https://i.imgur.com/sZaH2MP.png)
@Chromium User: You only need to use chrlauncher.exe. It will install, launch and update automatically Chromium.
@John & WildByDesign: Thanks for feedback. I updated the site ;)
I tested with chrlauncher, on win7 and win10: https://chromium.woolyss.com/f/translate-2016-10-26.mp4
Video tools: Screen Recorder (by mchehraz) + Avidemux.
https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb/
Chromium 56.0.2899.0 (Official Build) (64-bit)
3f7d99feb499fb68ab0f78e6df93871ec8b3cc43-refs/heads/master@{#427578}
Compiler MSVC 2015 (PGO)
----------------
Quick comparisons with my previous PGO build below. Tested on an older AMD A10 notebook.
Chromium 56.0.2899.0 PGO
Peacekeeper: 2071
SunSpider: 374.0ms +/- 0.9%
Chromium 56.0.2901.0 PGO
Peacekeeper: 2489
SunSpider: 349.4ms +/- 1.7%
I've tried to manually apply the patch at http://pastebin.com/iG5UF258 but when I "gn args out/LKGR_x64" get duplicate linkage issues.
Sorry everyone, comment'll be in French... I'd like to say something to this website's admin, who can speak this tongue if I recall correctly.
Je me permets de revenir sur une modification que tu (je me permets également le tutoiement, désolé) as apportée ici. Tu sembles déconseiller Opera (en tout cas c'est comme ça que je le comprends, vu que tu as barré la mention éponyme) désormais, au prétexte qu'il "appartient" à Qihoo. Il se peut très bien que tu sois au courant des nuances de "l'affaire", mais des piqûres de rappel ne font pas de mal j'imagine :
1. Déjà quand tu marques "by Qihoo 360", c'est inexact. D'une part, parce qu'une partie d'Opera est rachetée, et pas l'intégralité (l'accord initiale n'ayant pas eu l'accord des autorités concernées, une autre proposition a dû être faite); par exemple, la branche navigateur est rachetée, mais SurfEasy (service de VPN payant, et également fournisseur du VPN de navigation gratuit) ne l'est pas. D'autre part, car ce n'est pas Qihoo qui rachète, mais un consortium Chinois, Golden Brick, qui comprend une participation mineure de Qihoo. Ce ne serait donc pas lui le principal décideur.
2. Lorsque l'accord avait eu des échos dans la presse notamment, Opera est passé rapidement en mode Contrôle des dégâts en indiquant qu'elle resterait la même, que ça n'aurait pas d'incidence sur l'expérience des utilisateurs et que ça lui permettrait surtout de gagner en ressources (financières notamment). Je pense que tant qu'on a rien repéré de gravement suspect dans les agissements des logiciels concernés, on ne devrait pas négliger ces propos. Innocent tant qu'on n'a pas prouvé qu'il est coupable.
Si ça ne te pose pas d'inconvénient, j'aimerais donc que tu édites en conséquence. Peut-être que tu pourrais indiquer de manière transparente qu'il y a eu un rachat, avec un communiqué dudit accord, ainsi que les propos qu'avaient tenu Opera pour rassurer les gens. Ainsi, libre aux internautes lisant cette "recommandation" de décider s'ils veulent donner sa chance ou pas, plutôt que de déjà fermer la porte sans ne rien voir derrière.
Désolé pour le chipotage, merci pour ce site sympathique et bon surf.
Regarding Control Flow Guard: According to Trend Micro who has dug into CFG in the past, Microsoft has hardened CFG even further with Windows 10 Anniversary Update which is great news, even more so with 64-bit, I believe. Link: http://blog.trendmicro.com/trendlabs-security-intelligence/control-flow-guard-improvements-windows-10-anniversary-update/
@Jerry: There's another hosts file you could add to your list: https://github.com/StevenBlack/hosts
Have a good day everyone.
Anyone knows why google translate won't work even with Chrome?? This is a strange issue. I have downloaded chrome and it also doesn't work. It translates the page , it says page translated but nothing changes. What could affect both Chrome and Chromium ?
In the nightly Chromium builds CFG is (now) the default.
Once you have done a PGO build (or collected sufficient data), is it really necessary to do subsequent PGO builds for new Chromium releases?
I mean once you have the PGO data could you not manually apply it to software components that most require optimising?
For example,
if (!is_debug && is_win) {
configs -= [ "//build/config/compiler:default_optimization" ]
configs += [ "//build/config/compiler:optimize_max" ]
}
Would you be willing to provide a list of the main Chromium components that benefit the most from PGO?
Thank you for your good work.
My next objective is to integrate some of the "ungoogled" works into my (nightly) build.
AFAIK, you need to PGO profile for each build. All but 19 functions were optimized in one of my recent PGO builds, even if the vast majority of functions are optimized for size instead of speed.
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
266 of 1322755 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
8639617 of 16081063 inline instances were from dead/cold paths
1322736 of 1322755 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
653309896679 of 653309896679 instructions (100.0%) were optimized using profile data, and the rest of the instructions were optimized without using profile data
That said, I probably should do some serious comparisons between WPO and PGO. WPO is heuristics-based optimization versus PGO using profile-based optimization. If there is only a percent or two real-world performance difference, then I am not sure the build time for PGO is worth it, at least to me.
Updated Clang/LLVM builds are now available for both Windows 32- and 64-bit platforms.
Been busy, so apologies for the slow update interval.
Thanks
@RobRich: I am waiting for you! ^^
@1495 and @Andreas: No, we do not store very old Nik's builds. And they are not PGO compiled. If you want to remove the profile icon, you can:
- use the incognito mode
- or compile Chromium yourself (Note the Akujin's patch does not work on version 51+... so make yours!)
"no plans" is not an accurate way to put it, as there was no plan to begin with. Someone else wrote a patch to remove that profile button, and anyone who compiled Chrome/Chromium could use it. Then Google changed the code for the profile button, integrating more into the framework of the browser. The patch no longer worked, and due to the way it's coded, it (so far) seems unlikely that a new patch will be created to remove it again. If someone does figure out how to make a new patch to remove it, then I am sure nik and RobRich (and anyone else who wants to) will use it.
Comments for nik & RobRich:
nik's last few PGO lkgr builds have some issues where a page will go black for a moment, then the page comes back. It happens on all pages, and seems much more frequent in the first minute or so of opening the browser, but does continue to randomly occur even after a length of time.
I thought it might be just that the builds were PGO optimized, and / or the build #'s themselves had issues related to development. However, when I used RobRich's PGO builds, sometimes even the same build # as nik's, the pages turning black never happens. In addition, RobRich's builds are slightly faster. My guess at this point is the way nik performs his PGO optimization is introducing this issue, but I am unsure.
If it helps - I am Windows 10 x64 1607 & I use the lkgr archive No sync builds.
Thanks Jerry, nik, and RobRich for all your efforts.
"Official" built with Clang/LLVM for 32-bit and 64-bit Windows.
"Official" built with MSVS for 32- and 64-bit Windows.
"Official with WPO" built with MSVS for 32- and 64-bit Windows.
"Official with PGO" built with MSVS for 32-bit and 64-bit Windows.
It should allow for comparison testing of the various stages of optimization.
----------------
I am not sure what build arguements Nic currently is using, thus perhaps some differences.
My PGO builds currently use:
is_official_build = true
chrome_pgo_phase = (1-2 phase #)
is_debug = false
proprietary_codecs = true
ffmpeg_branding = "Chrome"
enable_widevine = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = fals
"nik's last few PGO lkgr builds have some issues where a page will go black for a moment, then the page comes back. It happens on all pages, and seems much more frequent in the first minute or so of opening the browser, but does continue to randomly occur even after a length of time."
===
I compile non-pgo builds (with full codec spupport and no sync) and have the same issue. It's more likely to do with the "gn args". Does RobRich's PGO builds include full codec support?
I'm not particularly sold on the benefits of optimisation - WPO or PGO: I'd be surprised if the performance gain is in the "order of magnitudes". I attempted a WPO build today and ran out of disk space! At the start of build, I had ~40Gb of excess disk space.
I will take a look later, but IIRC, my PGO builds have been like 100+ GB each.
For comparison, I remember a recent Clang/LLVM build without symbols was a little over 3GB.
And here is my args.gn versions https://github.com/henrypp/chromium/blob/master/args_gn.md
This patch allows user to block aggressive advertising from XXX sites.
Is this patch inside the current build of Chromium ? If not, it's possible add it to Yours builds ?
So back to my original question, since there aren't any current Chromium ADMX templates available to download from the Chromium site or from here, can someone help me out with building the policy_templates Chromium project? It would be great if the ADMX tempaltes were posted on this site with each new Chromium release.
nik I've been using your builds for a long time, it was only until the recent builds that this started happening.
I'm on (No sync • No WebRTC • No Widevine • 56.0.2906.0 (428695) my OS is Windows 10 x64.
Updated PGO build now available. Experimented with extensive profiling for instrumentation. Took hours. YMMV.
Chromium 56.0.2913.0 (Official Build) (Windows 64-bit)
Revision 474ffeb14d5b30ff925c15dfde05c7b49ea2572f-refs/heads/master@{#430219}
Compiler MSVC 2015 (PGO)
- mini_installer-pgo.exe
- chrome-pgo.7z
- chrome-pgo.zip (Nik's format)
----------------
Updated Clang/LLVM 32- and 64-bit builds now available. Same revision as above.
https://github.com/RobRich999/Chromium_Clang/releases
----------------
For comparison testing, I have a MSVS dev build of the above revision done. Waiting on official and official with full WPO builds to complete. I likely will just toss them all in single archive for download. Probably Tuesday sometime.
Try to disable the hardware acceleration in options, maybe this will help.
I have assembled multiple builds of the same revision (v 56.0.2913.0-r430219-win64) for those interested in comparison testing. Builds include development compiled with Clang, development, official, official with WPO, and official with PGO. The archives are in Nik's format.
- chrome_builds_x64.7z
- chrome_builds_x64.zip
The archives are the same, just in different compression formats. Either way, the extracted size is around 874MB.
@new_user: there's no looking into it, chrome team is deleting old chrome UI code so there's no way to enable old UI anymore, only Material desgin from now on. The last non-material build is 55.0.2867.0 (revision 419802) and is available at @nik's github
black flickering with the new build 56.0.2915 AND also with Robs 56.0.2913 \Dev_MSVS_x64
NO black flickering with Robs 56.0.2913 \Official_PGO_x64
i hope this helps.
is_debug = false
is_win_fastlink = true
symbol_level = 0
remove_webcore_debug_symbols = true
proprietary_codecs = true
ffmpeg_branding = "Chrome"
enable_widevine = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
I built Release_PGO_x64 with the following arguments:
is_official_build = true
chrome_pgo_phase = 1 (2)
is_debug = false
target_cpu = "x64"
proprietary_codecs = true
ffmpeg_branding = "Chrome"
enable_widevine = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
On a side note, I should have an updated PGO build later today. It is currently in instrumentation.
Updated PGO build available. Download via GitHub. :)
https://github.com/RobRich999/Chromium_PGO/releases
Chromium 56.0.2915.0 (Developer Build) (Windows 64-bit)
Revision d3db0dba7ab7119602cb4e83b785044f6f44619b-refs/heads/master@{#430950}
Compiler MSVC 2015 (PGO)
Maybe revert back to non-PGO for the time being?
No flickering with RobRichs last PGO Build.
@RobRich: got it, will check
Is it normal?
https://www.chromium.org/developers/how-tos/api-keys
https://www.computerhope.com/issues/ch000549.htm
I build Chromium with all the codecs enabled for both the macOS and the Windows platforms. I dual boot an Optiplex 780 (Hackintosh) with a Radeon HD5450 graphics card. I'm able to use HA on the 'mac' with no problems; but not under Windows: the performance gain using HA is negligible.
google again integrated webrtc more deeply in the main code and my patches not enough *sigh*
1. Chromium Portable on nik builds: https://sourceforge.net/projects/thumbapps/files/Internet/Chromium-nik/
2. Chromium Portable on RobRich999 (or other than nik) builds: https://sourceforge.net/projects/thumbapps/files/Internet/Chromium/
can someone check this build for flickering issue?
@mnsch: it was for test, but now i uploaded other files
since v.56 whoer.net detects a proxy. i dont use a proxy and v.54 with same settings dont show this. anyone a idea whats behind this?
https://github.com/RobRich999/Chromium_PGO/releases
Chromium 56.0.2920.0 (Official Build) (Windows 64-bit)
Revision fe5ea3f7cb872ea6fa2e560cfefc9185393a8cb2-refs/heads/master@{#431896}
Compiler MSVC 2015 (PGO)
----------------
Updated Chromium Clang 32- and 64-bit builds now available.
https://github.com/RobRich999/Chromium_Clang/releases
Chromium 56.0.2920.0 (Developer Build) (Windows 32/64-bit)
Revision fe5ea3f7cb872ea6fa2e560cfefc9185393a8cb2-refs/heads/master@{#431896}
Compiler clang (+msvs linker)
Kudos to everyone who contributes for this site, the work you put in in this project is just amazing!
It appears the site is using CloudFlare as a CDN reverse proxy provider for HTTP traffic, thus potentially confusing the script on the server-side of the situation.
Take a look at HTTP headers at the site. Example:
URL: https://whoer.net/js/jquery.main.js
Request Method: GET
Remote Address: 104.25.38.26:443
cache-control: public, max-age=2073600
cf-cache-status: HIT
cf-ray: 3026185ff70717f2-MIA
content-encoding: gzip
content-type: application/javascript
server: cloudflare-nginx
status: 200
IP 104.25.38.26
NetRange: 104.16.0.0 - 104.31.255.255
CIDR: 104.16.0.0/12
NetName: CLOUDFLARENET
NetType: Direct Assignment
Organization: CloudFlare, Inc. (CLOUD14)
Comment: https://www.cloudflare.com
About CloudFlare:
https://en.wikipedia.org/wiki/Cloudflare
Might be worth someone mentioning to the whoer.net webmaster if desired.
Recently had to move from linux to windows and chromium is one of my favorite browser.
Reasons:
1) It is outdated. Stable version is currently 54.0.2840.99. So there are many bugs, issues and security holes corrected from version 53.
2) It is buggy itself: https://github.com/Eloston/ungoogled-chromium/issues
3) Eloston promises to compile a 64-bit version for Windows: https://github.com/Eloston/ungoogled-chromium/issues/62
4) Chromium code often changes. So it is difficult for developers to maintain unofficial patches (like ungoogled-chromium by Eloston).
5) You are on a website about Chromium, not about #chromium-forks
Super Smooth Performance
Better RAM Consumption than other Chromium Builds
No Flickering Issues so far so goood <3 Keep it up NIK and Other Chromium Devs!
https://github.com/RobRich999/Chromium_PGO/releases
Chromium 57.0.2926.0 (Official Build) (Windows 64-bit)
Revision 3076aa222b62ac770f2c887bc11b7e246fe5b063-refs/heads/master@{#433443}
Compiler MSVC 2015 (PGO)
Silent Install works fine using " --system-level --do-not-launch-chrome" but i was wondering if there is a switch for updating as well because it keeps the old version installed almost completely if you just run the installation again.
Thanks!
Need to try a new test build with Clang and lld to see if a stability issue has been resolved, as right now I am having to link the Clang compile with Visual Studio.
Using Nik's (No sync • No WebRTC • No Widevine • 57.0.2933.0 (434488) • Sunday, 27 Nov 2016)
In the previous build this wasn't happening I find it disrupting especially the red one. Nik?
Resetting flags resolved the issue, though I have not tracked the exact flag.
I do know the last few times I have had flag issues, zero copy was my usual first suspect to check.
Also on the newest 57.0.2935.3 Canary build there seems to be a problem with Reddit Enhancement Suite, you get 'Aw Snap!' errors while browsing Reddit with this extension.
Also tried resetting all flags to defaults. Several sites still 'Aw Snap!'.
I did not notice the borders when instrumenting my latest PGO build, either. It is currently in phase two building, so it probably will be late tonight or tomorrow before releasing it.
I think the recent crasher now should be resolved, too. :)
I think Nik builds with all codecs available, including those in the codebase perhaps needing build file edits to manually enable, so there could be differences.
I just tried to upgrade Chromium portable (regular dev) from 57.0.2929.0 to 57.0.2939.0 and get this message on start up:
"Failed To Create Data Directory
Chromium cannot read and write to its data directory: "D:\PortableApps\Chromium64\Data\Chromium\User
OK "
The portable configuration are the same, so it's kinda weird. But maybe more luck with latest release so I tried with 57.0.2940.0, but no luck!
I thought it was the portable configuration, but when I run the last release (57.0.2929.0), surprisingly it's OK no strange error message.
Happen both on 32 and 64 bit. Anyone with the same experience?
Ronny
@thumbappsOrg
Fixed soon.
Website: http://www.henrypp.org/product/chrlauncher
Download: https://github.com/henrypp/chrlauncher/releases
ALL GOOD and somehow is much much more blazing fast-er than b4
still i pref the old non-Material Design User design - which ver is the last copy again pls?
Thanks for your good work
Also thanks jerry for your site
so something like this..
do you have more user for nosyc or sync?
i pref nosync
perhaps you can do a alternate ver - sync when 54.0.2840.99 then nosync when 55.0.2883.75
or like once a month or couple of months or even quater or half-yearly - like a major upgrade...
not sure if the everyday user needs to update ver everytime chorme new release
unless there is a major bug
so pls consider keeping the nosync (be it not regular updates)
appreciate your work and time :)
@Nik: Yes! Let Rob do the NoSync.
Is it possible to keep no-sync, but just compile without PGO (like you used to)?
I suppose there is the issue of cold and dead paths, but again, I supect most of us are running systems with plenty of memory and probably processors with decent cache sizes.
Point? PGO is not a tremendous performance improvment on decent hardware compared to full WPO, which uses heuristics instead of instrumented profile data for optimization. Full WPO is build intensive, as PGO uses it too, but it does not require instrumentation profiling or second phase linking - a potential build time savings of several hours.
I know Pale Moon (forked Firefox) dropped PGO, and IIRC, the decision was made quite a long time ago. I suspect it might have been done due to similar results as we are noting here.
I have an updated PGO build that just completed last night. I can do a full WPO build easily enough. How about I then post both bulds, and a few of us comparison test them for feedback on any actual usability peformance differences?
In terms of daily usage, snapshot dev and even my own Clang dev builds peform decent enough - IMO anyway - on my various systems, including my older notebook with an early AMD A10 processor.
btw i'm also using the NOSYNC build and i think i can keep nosync without PGO (i had already planned to do it for myself).
@RobRich: that will be great, maybe after that i'll stick with wpo instead pgo and do the both builds :)
I have three builds for the same revision: official, official with full WPO, and official with PGO. The did a shorter instrumentation pass for the PGO build than usual, but the optimization stats are similar enough to my previous PGO build for comparison testing IMO.
The files are named accordingly, and the ZIP archives are in nik's "chrome-win32" format.
Chromium 57.0.2940.0 (Official Build) (64-bit)
Revision 22c3ee4fc5e755a4c08d900b63dbe48f7974946c-refs/heads/master@{#435933}
- mini_installer_official.exe
- chrome_official.zip
- build_args_official.txt
- mini_installer_official_wpo.exe
- chrome_official_wpo.zip
- build_args_official_wpo.txt
- mini_installer_official_pgo.exe
- chrome_official_pgo.zip
- build_args_official_pgo.txt
Full WPO • No sync • No WebRTC • No Widevine • All Codecs • LKGR • 64-bit
Drop PGO - What RobRich said.
No sync - I don't have a Google account or wish to use sync.
No WebRTC - Get rid of IP leaks, must for those on VPNs.
No Widevine - I don't use any services that require it.
All Codecs - Life saver as my Windows Server 2016 OS is missing codecs.
LKGR - Bleeding edge without being Canary-tier in terms of unstability.
64-bit - Plenty of RAM to spare and performance benefits of course.
Of course for those that do need them keep the alternate builds up too, choice is good.
Regardless I appreciate the work you gents do and the choices you will make.
here is new build https://github.com/henrypp/chromium/releases/tag/v57.0.2940.0-r436006-win64
Skip the Official with Full WPO builds. Typical JS performance, even when showing any positive gains, is generally around 1% faster compared to Official. Some rendering tests are actually slower than Official. ?! There are not enough positives to bother IMO.
On to Official with PGO. Admittedly, performance is generally improved if instrumenting the optimization profile for specific benchmarks. Some of the biggest gains I noted are certain rendering and DOM processes, though even then the overall results still are typically within a few or less percent of Official. Being realistic considering the build times involved and for the vast majority of typical day-to-day browsing activities, I see no overtly compelling *performance* reason to build Chromium with PGO at this time - again IMO, of course.
Official already does targeted compiler and link-time optimizations, just like Google was doing for Chrome until going live with PGO builds, and that worked fine (enough) for several years. ;) Unless one is solely crunching benchmark numbers, I recommend building Official without Full WPO and PGO for now, and maybe we can reevaluate performance differences again in a couple of months if interested.
All that said, I still intend to occasionally build LKGR with PGO for ongoing performance testing purposes, so I will continue to push build updates as possible. Maybe once a week or so? Otherwise, I probably will be concentrating the bulk of my build efforts on Clang/LLVM releases for the immediate future.
https://chrome.google.com/webstore/detail/material-incognito-light/necpbhkfondbpbloppmkjpdkdimldobc
Curious, does anyone actually use WebRTC? I know it is a potential security concern for some people, and it is one less feature to build that I do not personally use anyway. Unless someone has a good argument otherwise, I probably will disable its functionality in my future builds via the associated GN build parameter.
I got it from #comment-1591
And I've just tried your release, and the bug's still there, or do you have any tip to disable the bug?
Even I Disable WebRTC using Flags
Its better if you disable in Future builds!
Cheers!
57.0.2943.0 (436242, b887e7c) • Monday, 5 Dec 2016
has the bug removed.
also "So most folks that come to Woolyss' site for Chromium builds would have security and privacy as their priorities when it comes to choosing Chromium builds." is true for me atleast, I got fed up with firefox, /g/ linked me here so glad to have found this page, thank nik and rob importantly.
I also will disable it for my next PGO build, though that could be a few days out since PGO is not a current priority IMO.
That "Aw, snap!" error that was happening repeatedly in recent builds seems to be gone as I haven't had it happened since updating.
Thanks.
https://github.com/Eloston/ungoogled-chromium/issues/137
BTW, a quick explanation for those not building Chromium. "Official" does WPO on select targets when building, versus "Official with Full WPO" does WPO on all targets when building.
My primary focus right now is building Chromium using the open source Clang/LLVM compiler, as that likely the future of Chrome on Windows. It already is the compiler used for Chrome on Linux and MacOS. Note I am still linking with Visual Studio. I just filed a bug report for a crasher with the open source LLD linker, which I hope to soon again be using for published builds.
As for Virtual Studio builds, I am going to continue occasionally churn out Visual Studio releases with profile guided optimization (PGO) so we assess ongoing performance changes, but it is not a priority roght now since PGO offers minimal to moderate retuns in exhanged for dramatically increased build times.
Speaking of optimizations, I noted link time optimization was recently added to the "Official" build type with Clang+LLD. :) I was able to do such a build yesterday, and it showed some performance gains, though it was highly unstable due to the ongoing crasher involving LLD. Hopefully it will be resolved soon.
Same as Ed and Cyberrufus, i get an error "cannot create data folder" during launch.
Build 2933 and Rob's 2946 all work great.
@nik Thanks for the info, and of course, the Visual Studio builds. :)
----------------
Today I noticed VS Community 2017 RC1 is now available. Gave it a shot, but build landmines have not yet been updated for it. I might take a look at the landmines file later, as VS2017 still is using SDK 14393, so I doubt there are many (if any) differences in the build process.
FYI: your "clang" build is very responsive and fast.
I've switched to your build.
I have not seen it with 2946, which I have been running locally for over a day.
The performance of Clang/LLVM builds ideally should improve even further if/when the LLD linker issue I mentioned earlier is resolved. Then I can build with link time optimizations similar to existing Visual Studio builds using the "Official" build process.
Thanks guys.
I just pulled code off master and am currently building. If the builds appear stable, I will try to publish them later today, then replace when LKGR is eventually updated.
Reset to default your about:flags config?
https://bugs.chromium.org/p/chromium/issues/detail?id=664177
With stable I have none of the problems I was having on Nik's or Robs lkgr builds and I'm happy with performance.
Maybe in due time when I see complaints here settle down try lkgr again.
I also should have fresh LKGR builds published today.
no problem at all
I let it collect a few errors when it crashed, and perhaps that data was submitted. I've since deleted the Extension and have reverted back to Disconnect for the time being.
Maybe others using that particular Nik build can replicate the issue.
For those having stability issues, this is just a quick thought, but see if disabling the recently introduced "No-State Prefetch" option in about:flags makes a difference.
I have been using my 2952 x64 build for awhile today. No stability probs so far here, but as usual, YMMV.
I did note a couple of minor video-related errors in the GPU log, but they are rather trivial and not crashers.
57.0.2952.0 - r438537 Snapshot- no crash with clean profile.
57.0.2952.0 - r438537 Clang build with codecs- crash with clean profile.
Disabling javascript on the site eliminates the issue.
I know someone earlier speculated that the builds without WebRTC were the ones suffering the crashes, and I can confirm that to be the case for me. When using the same build # (57.0.2952.0) from Nik - the one with WebRTC doesn't crash, while the one without WebRTC does. Easy pages to cause the crash for me are Paypal, or google voice, and even image pages from Photobucket. Those pages haven't crashed for me with builds having WebRTC.
I'm hoping this is just a compiling issue, meaning that in builds without WebRTC there is something left behind that causes certain pages to attempt to utilize WebRTC--even though it's not there--thus causing the Aw, Snap crash. Or something of a similar nature.
Just checked and http://heavy.com/ is generally okay here. It does generate some minor DXVA-related video errors in the GPU log on 2953, but that is because I do not have hardware acceleration (or perhaps even outright support?) for whatever video format is being used. Basically means those annoying video ads do not work properly - assuming that is a concern. ;)
Also to note, while I do enable a few extensions as needed for specific purposes, I typically do not use any extensions with Chromium.
https://chrome.google.com/webstore/detail/material-incognito-light/necpbhkfondbpbloppmkjpdkdimldobc
which build is better between 'clang' or 'pgo' for 64 bit systems ?
My Clang builds are built with the open source Clang/LLVM compiler. I am using Clang to keep tabs on development progress, as there are expectations Chromium will eventually migrate Windows builds to it. The project already uses it for MacOS, Linux, etc.
If you want the best performance, nik's builds have additional link time optimizations available with Virtual Studio. If/when a crasher is resolved with builds linked with the open source LLD linker, I should be able to experiment with similar optimizations for Clang builds. In the meantime, I am compiling with Clang and linking with Vistual Studio.
I have been using snapshot development and similar builds of Chromium, Mozilla Nightly, Opera, etc. for many years without much to note from stability and usability standpoints. That said, I do not load a half dozen extensions, multiple themes, and numerous plugins, either. ;)
Thanks for your comment cyberrufus.
@1690: proxy switch omega
By the way, thanks both of you for the fresh builds! :)
Personally, I never see aw snap! error on win7 too. However, I see sometimes this error on win10.
Thank you dear developers! ;)
Latest 'RobRich' working build without "AW SNAP" error is Version 57.0.2927.0 No WebRTC, No Sync RobRich Clang version
Chromium saves only a page (horizontal) not in large mode. Tried with Nik's build and Chromium Authors build with the same result.
Tried on Windows 8.1 and 10.
Some idea ?
Today I internally updated to 2959. No stability issues to note thus far. I should have updated builds published later today.
GOTO chrome://settings/content -> PDF Documents (tick or untick)
or right click on the page you want -> PRINT (i dont have printer and set to PDF print)
or https://www.printfriendly.com/ (they have app extension for chrome too)
or if the page has a already has a PRINT button -> right click select save as
something funny going on...
No 32-bit release for now, as there is a newly introduced LLVM compile issue. Appears a component is expecting 64-bit even when the compile is assigned 32-bit. Probably a typo, flawed conditional, or similar in the affected code.
@Raf: You do not use the stable version. Check #windows-64-bit-stable-nik
I have tried Yandex Browser Portable (Chromium-based russian browser) and my Pdfs are better, not perfect but better. (I have used horizontal layout and A3 page).
Git just pulled over 650MB in objects since my source update yesterday. o.0 Looks like 2960 could have multiple changes and/or updates compared to 295x.
----------------
32-bit building is back to working with Clang/LLVM. 2960 published for both 32- and 64-bit paths.
A small gif of what happens:
Nik's Stable build doesn't require it, but the Dev builds do. zenmate.com doesn't load regardless of adding 'www.' manually. I have to use stable for that site.
I would think perhaps a DNS issue, but apparently stable is working for ya. Chromium does keep an internal DNS cache, so perhaps that could explain the different results for different profiles.
Go here: chrome://net-internals/#dns
Clear that internal cache, then flush Windows' local DNS cache from a command prompt....
ipconfig.exe /flushdns
....then try loading the sites again. :fingers crossed:
Maybe it's an issue isolated to me I suppose. I'm happy using stable at the moment. I just hope it doesn't remain an issue when stable reaches v56+
Why chrlauncher is downloading 2950 for dev-codecs-nosync 32-bit, while 2960 for dev-codecs-sync 32-bit, although 2960 is available for both?
Also, the same situation is here on this website - Installer for 2960 32-bit is available, while Archive is linked to 2950.
Read all the info and if ok with you install it
And when done (may need to restart)
on the page you want to pdf
you should be able to right click
select PRINT
and choose a variety of format including A3 horizontal
good luck
also happy holidays and thanks to jerry + nik + RobRich and all the developers and users :)
use HTTPS Everywhere / KB SSL to force browser to HTTPS
// 2950, 2960 32-bit
See if that helps with the closing issue.
For me deleted 252 in folder "CertificateTransparency\
After chrome://components - Signed Tree Heads - update
Have 253 in v57.0.2963.0 end of random closes
Thanks, but that option is disabled by default (ok for me) and what it does when enabled is launching system app for pdf viewing (whichever your chosen one) instead of opening it inside Chromium. That's not what I'm talking about. I want neither, as was possible before by disabling the PDF Viewer plugin (so only the save option was possible). Now seems that it can't be disabled (no disable option on plugins page for any of them).
Chromium PDF Viewer? or some plugins you install?
try chrome://plugins
and disable Chromium PDF Viewer there
Thank you a sorry. Yes, it is working as you say. Didn't test myself because the setting description was not the desired behaviour. It seems the description is not accurate or at least it can be misinterpreted. The pdf file is downloaded for *later* viewing with user's app of choice.
I have internally updated to a LKGR 2964 build released after the applied bugfix/revert and it appears okay even when manually forcing an update of the signed tree heads. I should have updated builds pushed in the next hour or two.
There is a merge request for a commit to resolve the issue, and it includes the needed JS file edits if one wants a manually patch the extension before a release with the commit merged is available.
https://github.com/EFForg/privacybadger/pull/1108
I've been using the version with sync and webrtc in the meantime, trusting PB to do its job, but I'd prefer to use a non-webRTC version and then be able to use PB for the rest of what it does as well. Thanks much.
Another method, which I borrowed/learned from chrlauncher, was to modify the Chromium shortcut. For example, I use the Nik Stable Archive download and run entirely from RAMDisk. So I create the following shortcut "R:\Program Files\Chromium\bin\chrome.exe" --user-data-dir=..\profile -- "%1".
Directories:
R:\Program Files\Chromium
R:\Program Files\Chromium\bin
R:\Program Files\Chromium\profile
So that is the directory layout that I borrowed from chrlauncher but I no longer use chrlauncher. I am still able to make Chromium from that RAMDisk location the default browswer, no problem. But there is one problem. When you open a link from, for example Thunderbird, it will try to open default browser and it will run Chromium from RAMDisk but it will start a new profile within RAMDisk.
To fix that, I had to search the entire registry and replace:
"R:\Program Files\Chromium\bin\chrome.exe" -- "%1"
with
"R:\Program Files\Chromium\bin\chrome.exe" --user-data-dir=..\profile -- "%1"
Therefore with that rather minor registry work (3 or 4 replacements) I am always running Nik Stable Archive builds entirely portable from RAMDisk (though you can run anywhere you like) and zero issues. This is the more difficult manual method. But the quick and easy way would simply be to use chrlauncher since it would keep you portable and up-date-date with builds once you specify the channel within the config.
In a previous comment I asked for a way to disable the PDF Viewer plugin, since that option at chrome://plugins has been removed in recent builds. I was suggested to just enable the last option in content settings to achieve the same behaviour as disabling the plugin (just offer to save a clicked pdf without opening it). I reported it working, since clicking a pdf link after enabling that option worked as expected.
However all attempts after that just download the pdf (without asking for path, just ignores the Always ask setting) to my default download folder *and* then opens it with my system viewer, which is unacceptable behaviour. Only current semi-workaround is right-click and download, but this doesn't always work depending on how the pdf is served.
I set all the flags to have the material design page for all pages (settings, extensions, history, etc).
All are displaying right, except for the History page, which shows the old UI.
but since update on 55.0.2883.87 it seems its 'fixed'
could be something in the chrome:flags?
you can also try and read comment - Anonymous (1716)
Regarding comment 1716, it doesn't really apply to my issue. I think giving to the user the option to disable the plugin like before would be the most convenient solution.
Also just noticed my latest PGO build was incorrectly uploaded with a non-PGO build. I already cleaned out the local build files for the release revision, so the download is borked for now. It is not an immediate priority, but I will try get a build up later today or tomorrow.
https://bugs.chromium.org/p/chromium/issues/detail?id=615738#c54
Another possible option would be to attempt to use Group Policy. No idea if that would produce the behavior you desire but it does say pdf is treated as a download.
Sad move, unneeded limitation...
Hopefully the future stable ver stay the same...
Thanks Rob for you version "57.0.2971.0 (441109) • Tuesday, 3 Jan 2017" ! It works perfectly !
I have a question, what is the difference between CLANG and PGO ?
Thanks dear developers and users! ;)
@Dan: I searched in the #command-line-flags list and chrome://flags but found nothing about that.
@Sifink: Please check these links:
- https://en.wikipedia.org/wiki/Clang
- https://en.wikipedia.org/wiki/Profile-guided_optimization
PGO is an optimization technique offered with Visual Studio, but it takes multiple linking passes and up to many hours to build. Load the older comments for more info. I am providing a PGO build for basic testing, but it is not a priority. In fact, the current PGO build links are borked until I get a new build done. It is currently compiling, but the last couple of builds failed, so.... could be awhile longer.
Technically these are not LKGR builds, but instead off the master trunk. Anyway, the revision seems stable enough in my limited testing. Hopefully LKGR should roll in the fix(es) for disabling WebRTC in the next day or two.
In the meantime, I pushed a build off master (after quick stability testing) as an interim solution until LKGR is updated.
I will have updated builds tonight or tomorrow.
Quick FYI while thinking about builds and revisions. My current Clang builds are back to LKGR. I have an updated PGO build cooking, too - perhaps for release tomorrow.
so much regressions and bugs..
https://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=SO29058
i see two options: upgrade chromium or disable transparency (the link above)
the registry key for chromium is HKEY_LOCAL_MACHINE\Software\Policies\Chromium\CertificateTransparencyEnforcementDisabledForUrls
https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb
The addon keeps crashin on startup.
Using the official dev builds the addon works however then I can't watch streams so thats not an option.
Is there any way to see crash reports and send them to nic to maybe fix the issue with privacy badger?
The extension never crashed or anything here.
I'm using the latest nik version (No sync • No WebRTC • No Widevine • 58.0.2988.0 (445274) • Saturday, 21 Jan 2017) on win 64 and privacy badger doesnt even start to run. It just crashes as soon as I start my browser...
https://fat.gfycat.com/FoolishViciousKob.webm
After I enabled the flag Overlay Scrollbars, the scrollbar cannot jump to another position if I click on a different point on the invisible bar. Also, it doesn't become visible when I hover the area with the mouse, as it should. Only when I use the mouse wheel the scrollbar becomes visible.
This problem doesn't exist in the stable build (55).
However, a problem I reported with build 55 (when the History page wasn't displaying material UI, even if I enabled it in the flags) now is fixed.
I think I've had this scrollbar issue before, and that's why I reverted to stable some time ago. If I disable the Overlay Scrollbars flag, it works normally, but it displays the permanent, solid scrollbar, instead of the optimised overlay one.
so wait a bit
- no-sync build working great in general, however all Flash content causes Aw Snap crashes
- sync builds all tabs are painted black with no working content at all
Unfortunately I am not sure yet what is causing all of these issues with Nik stable 56. I can confirm these issues are not occurring on Google Chrome stable. Maybe something during compile time?
@WildByDesign: i just check clean sync build v56 with chrlauncher on 3 different pc's (cpu - amd/intel, gpu - nvidia, os - win7x64) and all work fine: flash, tabs, windows, webgl, video content, i'm also tried to switch HWaccel on/off and nothing yet :\
I am successfully able to use the Sync build now without issues and Flash content is not crashing either. So that seems to be the better build at the moment for users wanting to use Stable channel that rely on some Flash content. For whatever reason, my initial testing with this build caused all tabs to be black and not working. That was testing with a freshly created profile. So I decided to test again with an existing profile (therefore carry forward existing settings) and now everything is working great, no issues.
Therefore I am using Stable/Sync build (usually I use no-sync) but simply just not logging into Google's sync service for now.
@1833: i think they did something with ppapi code part
I think I'll stay on the v55 stable no-sync for now, I really don't like WebRTC enabled, leaking stuff everywhere.
Ever read Flash security bulletins? Many include the following or similar language:
"....vulnerability that could potentially allow an attacker to take control of the affected system."
The page here says that this ppa has the stable release. So, is it stable or dev?
For info, PPA is also stable. There is a spanish tutorial: http://somebooks.es/instalar-chromium-la-version-libre-de-google-chrome/
In terms of web dev, but admitedly not necessarily animation, there is very little Flash does that HTML 5 does not. DRM used to be the primary excuse, espcially for audio/video, but browser support for EME went mainstream with Chrome, Edge, Firefox, etc. last year. Even Adobe has been pushing its own customers and clients toward HTML 5 since late 2015.
Now to Chromium users personally concerned about the issue, crbug.com is a good place to file a report. Perhaps a Chromium project dev will have more info. I suppose it even could be a code regression, but I suspect not.
I do NOT use the PPA. I DO use the one in Ubuntu's repos. But the Ubuntu repos are sometimes very slow to update. I wanted to see whether the PPA has a more recent version, in which case I would use the PPA instead of Ubuntu's repos. But I'd only do that if the PPA had stable versions, not dev or beta.
The question is simple and focused. Is chromium in the PPA stable or anything before stable?
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage
I wish we could somehow use a large hammer on the people who run websites that are broken if the user doesn't allow flash to run.
@nik: Are you getting treat "errors as warnings" compile errors when you try to build all codecs?
This is the error message (Trying to build Version 58.0.3005.0 (64-bit)):
C:\depot_tools\src>ninja -C out/LKGR_x64 mini_installer.exe
ninja: Entering directory `out/LKGR_x64'
[641/773] CC obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj
FAILED: obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj
ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64/cl.exe" /nologo /showIncludes /FC @obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj.rsp /c ../../third_party/ffmpeg/libavcodec/error_resilience.c /Foobj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj /Fd"obj/third_party/ffmpeg/ffmpeg_internal_c.pdb"
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(405): error C2220: warning treated as error - no 'object' file generated
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(405): warning C4047: '=': 'int (*)[2]' differs in levels of indirection from 'uint8_t *'
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(406): warning C4047: '=': 'int (*)[2]' differs in levels of indirection from 'uint8_t *'
[650/773] CC obj/third_party/ffmpeg/ffmpeg_internal/h264_loopfilter.obj
ninja: build stopped: subcommand failed.
The error is caused by the addition of the the "blocklist" macro to "error_resilience.c"
I've tried to solve the problem but have failed. So I've reverted to using the previous version of ffmpeg.
I'd like to try and build Chromium using LLVM to see if that would solve the problem. Since the Mac Chromium build uses LLVM and latest version of ffmpeg with all codecs enabled compiles cleanly and works.
If building LKGR, it could be lagging behind trunk by tens to hundreds of commits. Try building master to see if a fix for the issue recently has been implemented.
----------------
I have been occasionally poking at the LLVM build process, including resolving a runtime libraries issue and now locally building LLVM for the needed Clang and LLD binaries.
I just completed a working internal test build of Chromium compiled with Clang and linked with LLD instead of the Visual Studio linker. It is a component instead of static build, which is not a big deal for now. Component builds *might* be *slightly* slower to load. :shrug:
If the Clang+LLD internal builds look stable, I likely will migrate my public builds tonight or tomorrow, too. I will have to roll back the "is_official_build = true" argument until my Clang+LLD static build issue is resolved, as "official" does not support component shared library building. Again, not really a concern right now for Clang+LLD builds either IMO.
See here: https://bugs.chromium.org/p/chromium/issues/detail?id=584575#c15
RobRich, Specifically notice "Also disabling compilation of CFG with MSVC compiler. Preparing for clang CFI instead." Since you are more familiar with clang, that may signify more to you. If you have a look at that link, does that change any for the way in which you or Nik build Chromium to still achieve CFG mitigation?
Thanks!
Looking at the comments and changed build files, it appears CFG still will be invoked by the MSVS linker regardless if the compiler is Clang or MSVS.
AFAIK, it is the linker that generates the security checks in the LoadConfig table of an executable. If my understanding is correct, CFG in the compiler stage is more about security auditing at build time, while CFG in the linker stage is more about security auditing at run time.
On a side note, I am not entirely sure where the LLD linker currently stands on CFI support for Windows executables.
Go to the browser URL: chrome://components
Check all components for updates for good measure.
Thanks for the fresh builds as usually, @nik & @RobRich.
For months the lkgr release without sync, WebRTC and Widevine keeps crashing me on eBay and Paypal log-in pages.
Is anyone else experiencing this? Thoughts or solutions?
Cheers!
This site can’t be reached
The webpage at chrome://plugins might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL
Any help would be highly appreciated.
Thanks in advance.
3010 for nosync 32-bit
3003 for sync 32-bit
But there are 3017 and 3024 already.
Maybe this happens when for some reason Nik's release on github lack either some .zip or .exe? And then Woolyss's scripts break down for checking following updates?
Just like now: 3010 build lack chromium-sync.exe (so for sync 32-bit: Installer points to 3003, while Archive points to 3010).
Same was before: @1714 + @1715
So we don't getting updates for 32-bit builds a looong time sometimes :(
Current version: 58.0.3024.0
New version: 58.0.3010.0
@nik: could you please fix chrlauncher, about version comparison, and maybe about checking github directly...
We are sorry for any inconvenience caused.
@nik: Thank you very much.
I use v58.0.3025.0 The Chromium Authors with uMatrix uBlock origin and uBo-Extra.
In Setting Privacy impossible to uncheck :Use prediction service to load page more quickly.
Thanks
Addon: uBlock, Scriptsafe, PrivacyBadger Windscribe, IDM, https everywhere, Youtube Enhancer and CaretTab
@1092: Go to chrome://gpu, then http://camendesign.com/code/video_for_everybody/test.html to start a HTML5 video, then refresh chrome://gpu. Scroll to the bottom of chrome://gpu, and see if video playback errors are being reported.
@1903: Welcome. :)
Thank You.
Chromium accepts a long list of parameters. There's a --user-data-dir parameter with which you can specify the location of the profile. Using it with relative paths, the solution is simple.
I create the following structure: A directory named Chromium, that contains two directories, named Program and Profile. I extract the archive into Chromium\Program.
Create a .bat file in the Chromium folder, with the following one-liner:
start .\Program\chrome.exe --user-data-dir=.\Profile
On the first run, it'll populate Chromium\Profile with a new profile. You configure this profile to your preference. Every time you launch the browser, it'll load with this profile, regardless of user account and on any machine. This now behaves as a portable program is expected to behave; taking it's profile and settings with it.
This also allows for updating. Simply download and extract the files into Chromium\Program, and leave the Profile folder as it is.
On a side note, the Installer is also not really an installer. It simply extracts the same stuff to a location in your user profile. Since it's in a user's profile, it can only be run by that user. Since so, it'll always load up that users profile, as I explained above
[EDIT by Jerry: obsolete link]
That way the profile will be outside of AppData directories and all users can use the same shortcut with command line.
Maybe I am using the wrong search terms, but is there any way to fix this 'problem'? Not being able to use keyboard shortcut is a real pain in the ass...
https://v8project.blogspot.com/2016/08/firing-up-ignition-interpreter.html
I'm having this issue exactly the same on two different computers. One is a 32bit and the other is 64bit. I've tried cleaning apt and all caches/cookies/temps, no help. Any ideas?
Installed: 56.0.2924.76-0ubuntu1.16.10.1338
Candidate: 56.0.2924.76-0ubuntu1.16.10.1338
Version table:
*** 56.0.2924.76-0ubuntu1.16.10.1338 500
500 http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu yakkety/main amd64 Packages
As you can see, this info is coming not from the Ubuntu repos, but from this page's repo.
Looking more into it, I see that the repo itself doesn't actually have a v57, despite this page showing so. If you look at http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu/dists/yakkety/main/binary-i386/ and read the packages, you'll see that they're all 56.0.2924.76.
Also see http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu/pool/main/c/chromium-browser/ All packages go up to 56.0.2924.76, and no further.
The repo is giving consistent information wherever you look. Wherever you look in the repo, you find up to 56.0.2924.76. This page is the only one saying that the repo has a v57
Both NoSync and Sync, when on YouTube, hovering over any thumbnail of video is popping all kind of glitchy graphical anomalies often blocking out the link or the ability to hover over the link to see a full video title.
Reverting back to 3030 immediately resolves the problem.
Is it not impossible to revert back to previous without completely uninstalling?
https://www.chromium.org/administrators/frequently-asked-questions
But by now we see an issue with THIS repo, and/or its maintainer. The Linux part of this page shows that the ppa offers the updated 57.0.2987.98, but if you actually check it (either by adding to your sources or by checking the repos URLs) we see that its latest version is 56.0.2924.76, which is not one stable release before, but TWO. Indicating an issue with the repo itself. Before this current release, tis oage showed the repo to offer v56.0.2924.87, while that wasn't true either
Any ideas what is wrong?
At the time of writing this, Chromium (and all its related packages) is 56.0.2924.76
Arch have it. Checking that out, out of lack of other options.
It is still a more pressing issue. There seems to be some disconnect between the updating of this page and the repository for Ubuntu (again, NOT the Ubuntu repos. This page's repo)
The coordination issue still needs to be addressed or clarified
https://packages.debian.org/unstable/chromium (currently v57.0.2987.98-1)
No idea about the page here. Jerry might have more info to add.
Btw, i've been using @RobRich PGO builds, and they are great. Good work!
@1946: WPO and PGO are build optimization techniques. WPO uses heuristics, while PGO uses both heuristics and direct profiling of the application to optimize. PGO technically offers more optimization opportunity, but it can take many hours to build, profile, and build again; thus why it is not a regularly updated build here. I have a 32-core Opteron system, which is why I still occasionally do a PGO release, and even then it still takes a few hours to build. o.0 As for WPO vs PGO, the real-world results of the resulting build on decently spec'd systems often are minimal outside of benchmarks anyway.
https://en.wikipedia.org/wiki/Interprocedural_optimization
https://en.wikipedia.org/wiki/Profile-guided_optimization
CFG is a software security mitigation option. Most current builds using Visual Studio should have it be default. My Clang build might even have it by now since I currently link with VS linker, though I have not checked in a while. Maybe later when I log into my build box.
https://en.wikipedia.org/wiki/Control-flow_integrity
Clang is a front-end for the open-source LLVM compiler. I use Clang instead of Visual Studio for compiling Chromium. It is an alternative method right now, but eventually it likely will become the project's default compiler for Windows builds as it is used already for builds on Mac and Linux. My build is more or less an insight into how the work is proceeding.
https://en.wikipedia.org/wiki/Clang
Of note, I still link my Clang compile with Visual Studio for releases here, but ideally, I want to get builds linked with the open source LLD linker. I have LLD linked builds working locally, but it is only working correctly for component builds right now. I prefer to release non-component static builds due to size, complexity, etc.
Summation? You should be "okay" using Nik, mine, or even the project's own default builds. Pick one or test all. ;) Stability likely will be about the same. Performance could vary a few percent. Features could be different, though. For example, Nik and I have builds with sync, WebRTC, remoting, etc. disabled for potentially improved security. As with most things, YMMV.
So, the page wasn't giving false info. I apologize for the accusations.
Thanks to (Jeremy?) whoever keeps up this wonderful work!
@1950: Hope all is ok for you. Officially, there is no #stable-chromium-version So devoted developers re-compile Chromium for us, on each OS (Windows, Mac, Ubuntu, Debian, Fedora...).
@RobRich: Thank you for your great explanation on your #comment-1947
@nik: Thank you for news too.
@RobRich, @nik: I added a Portable version (using chrlauncher) for each Chromium version! ^^
BIG thanks for your time and constant effort about the Chromium project.
The Nik builds Portable, No sync/No WebRTC/No Widevine isn't available on this time.
The other problem is. I have made a desktop shortcut and move it in the taskbar. In other versions everytime i click this pictogram in the taskbar, a new window will open, not with this version.
- Chromium 57.0.2987.110 is the STABLE version.
- Chromium 59.0.3040.0 is a LKGR version.
My advice:
For using multiple/different versions of Chromium on your OS, use **only** chrlauncher.
So uninstall Chromium (via Control Panel or Ccleaner) if "Chromium" is in the list of installed software.
I wish there was a version that had bundled together:
auto updating, flash support, and no sneaky Google telemetry tricks.
@Jerry Might as well add the CFG tag to my PGO build listing, too. Thanks! :)
@1967: We talk about builds with SYNC. Did you really check args_gn.md content?
@gwindlord: Thank you for your report.
https://bugs.chromium.org/p/chromium/issues/detail?id=703992
A patch landed about an hour ago. If fixed, I will try to issue an updated build later tonight or tomorrow.
these programs are both portables
1. create a subfolder in C:\PortableApps with name ChromiumPortable
2. download from this site a portable version that You like
- put downloaded archive in ChromiumPortable, unzip and launch chrlauncher
- after finished update close chrlauncher (DO NOT run Chromium)
3. from the site PortableAppZ download 'Tor_Portable_MultiVersion_Online.exe' from
this page http://portableappz.blogspot.it/2014/01/tor-02420.html
run this online installer that create a subfolder TorPortable in 'C:\PortableApps' and run TorPortable.exe
4. edit the file 'chrlauncher.ini' in ChromiumPortable and add one of these strings:
a. ChromiumCommandLine=proxyserver="socks5://localhost:9050"
hostresolverrules="MAP * 0.0.0.0 , EXCLUDE localhost"
this is very comfortable and allows You to obtain chronology
b. ChromiumCommandLine=incognito proxy
server="socks5://localhost:9050" hostresolverrules="MAP * 0.0.0.0 ,
EXCLUDE localhost"
this allows You to run in 'incognito' mode, but it's very hard to manage the browser.
I suggest to add the string to number a) for run as normal mode
after this modify run chrlauncher.exe
5. for check if Chromium is anonymized by Tor:
- disable any ad-blocker
- go to Whatsmyip.org http://www.whatsmyip.org/ and press
'Geopgraphic IP Location' and verify Your fake IP with Your fake address
(this page do not appears if You do not use Tor)
----
The problem with chrlauncher is that there are two functions in one configuration
file. a better solution is to have three files:
- chrupdater.exe -> for update Chromium
- chrlauncher.exe -> for launch Chromium
- ChromiumTorPortable.exe -> for launch Chromium AFTER TorPortable
-------
Anyway I suggest to use an ad-blocker as uBlock Origin
We're not always looking at plain text pages on internet!
Nik's builds have most modern a/v formats, including additional formats needing underlying code edits to enable.
My builds should have whatever a/v formats Google's own Chrome browser build supports, including Widevine for a/v DRM at many premium media sites.
https://chromium.googlesource.com/chromium/src/+/master/docs/mac_build_instructions.md
Is such a behaviour somehow normal, usual, explainable (due, for example, to the portable build) or shall I infer there's something wrong with my system (Win10 64, i7-860, 8GB ram)?
Thanks for any help
I am new to Chromium since one month and I must say it is fantastic !
I was using FF for the last fifteen years, the move forward is incredible !
I just want to say there is an issue with the last two stable versions : sometimes it doesn't scrool down with the mouse wheel, I think this occurs when you keep scrolling while clicking on a new link
This is really annoying...
If that could be fixed, that would be fantastic !
Cheers
@Fred: hm, i don't use a stable version but i remember somethink like that on a some dev releases, but now i don't have this issue.
@1980: i'm using dev nosync all the time.. checking the twitch yesterday and today, but i don't catch this error :\
Tested with:
- 57.0.2987.133 (64-bit, sync, Flash enabled, Nik build, on win7) → it works.
- 59.0.3060.0 (64-bit, sync, Nik build, on win7) → it works.
- 59.0.3061.0 (64-bit, nosync, Clang, RobRich build, on win7) → it works.
Do you use win10?
Do you have any content filtering extensions or software installed?
Windows 8.1pro 64bit. Temp solution: clear the cache often ("Clear browsing data").
It may be Twitch breaking things with its recent internal change to allow higher bitrate streaming. If I force the quality to High at 720p30 instead of source at 1080p60, the memory increase is drastically slowed (but still increases without bound until crashing).
By the way, thanks for your continued compiling PGO no-sync builds, very much appreciated. =)
I also thought about cache and I tried using the launch argument " --disk-cache-size=1000" to nearly disable the cache.
This seems to be working: when I use the CTRL+SHIFT+DEL shortcut to clear the cache I read that cached images and files are "less than 1 MB". No speed improvement at all, however.
Do you think there's something else I can try?
PS. My browser, together with profile data, is on hdd, which by the way is the same hdd I used when Chromium used to start quote faster.
You can try the Procmon to capture all hdd activity only from the chromium start to full load (then stop the capture because it'll load your system) and see where the longest gap between operations.
Sync • WebRTC • Widevine • 59.0.3060.0 (461321) • Saturday, 1 Apr 2017
By the way @nik & @Jerry: @nik has sync version of build 59.0.3067.0 (463134) on github and here on woolyss it's on 59.0.3060.0 (461321). Archive points to the correct build but the Installer doesn't. That's probably because the chromium-sync.exe file is missing from github. Talking about 64bit versions
@2004: hm, yeah thats a bug, i'll fix it
It happens very oftently and this is highly annoying...
Thank you for your support !
But the page says it should be this: sha1: 1707c3522910ec876e1c19347cac2d3561f4465a - chromium-nosync.zip
@Fred: sorry, i don't know, ididn't see this bug on a recent dv builds :\
@2009: that was a bug, my script rebuild zip archive and updated this site, but not github, i fix it just now.
YMMV as usual, especially as Chromium has not migrated to VS2017 yet.
No sync (well, no API keys anyway ;p ), WebRTC disabled, and Widevine enabled. Compiled with WPO and CFG.
Chromium: 60.0.3074.0 (Official Build) (64-bit)
Revision: 6d3aa4c52ee23c233ec65f08c0a6ee0cb1aeca6a-refs/heads/master@{#464896}
OS: Windows
Compiler: MSVC 2017
In case anyone notices, the revision is off master instead of LKCR, as I forced a top-of-tree update for a possible quick fix when encountering an error building with WebRTC disabled. I still had to do a quick source edit to fix the error anyway, so whatever IMO.
Looking forward, I need to run a test build to verify, but I probably soon will be migrating PGO builds to VS2017 as well.
Go to the about:flags configuration, and take a look at the below flag. You can try forcing the flag disabled to test.
Optimize background video playback. Mac, Windows, Linux, Chrome OS, Android
Disable video tracks when the video is played in the background to optimize performance. #disable-background-video-track
Update on PGO. Tried a PGO build with VS2017. No go, yet, so PGO will remain VS2015 for now.
Quick FYI while on the topic. My latest Clang compiles here are linked with VS2017, plus I am now building the Clang/LLVM compiler with VS2017, too.
Chromium60.0.3075.0 (Official Build) (64-bit)
Revision929fcfc0778b8848e9a4b2b5c205c1ae43cfa9f9-refs/heads/master@{#465262}
Compilerclang
Flash: Not Working
Jump List: Not Working
Chromium60.0.3074.0 (Official Build) (64-bit)
Revision6d3aa4c52ee23c233ec65f08c0a6ee0cb1aeca6a-refs/heads/master@{#464896}
CompilerMSVC 2017
Flash: Not Working
Jump List: Not Working
Chromium60.0.3074.0 (Official Build) (64-bit)
Revision6d3aa4c52ee23c233ec65f08c0a6ee0cb1aeca6a-refs/heads/master@{#464896}
Compilerclang
Flash: Working
Jump List: Not Working
@All Does anyone know yet what the status is with regard to those Flash Player crashes on No WebRTC builds? Is there a specific patch/bug report to reference? Thank you.
Thanks jerry for maintaining the site :)
Strange. In this version, uBlock Origin blocked items counter stopped working.
I always do clean install instead of updating, to avoid weird stuff like that. Current stable nosync seems to work flawlessly for me so far. Addons: uBO+uBO Extra, HTTPS Everywhere, Privacy Badger.
uBlock Origin continues to crash from time to time (sometimes after some event, sometimes after several [tens of] minutes)
Made a backup of settings to file (uBO feature).
Tried to remove all uBO settings (Local Storage - .localstorage + .localstorage-journal, also from "Local Extension Settings" and "Managed Extension Settings"), launched Chromium, imported settings from file - continues to crash.
Tried to remove uBO, reinstalled it, imported settings from file - continues to crash.
Currently reinstalled and testing with default settings, will keep you informed.
If someone else has the same problem - please let us know...
P.S. Didn't check on clean profile because don't have much time (sometimes it doesn't crash for a really long time) and RAM, but will try to test it later (maybe some conflicts with other extensions?)
Chromium: 60.0.3080.0 (Official Build) (64-bit)
Revision: c4cb0d38f0bd26578120775e9c09be813b5215c0-refs/heads/master@{#466630}
OS: Windows
Compiler: MSVC 2017
As you can see from the screenshot, the dialogue is not offering an option to Run the exe, only if you click the slightly different words "more info" do you get the option to run it anyway.
Is MS just trying to stomp on your browser as competition for Edge, or does the new Windows Defender Smartscreen need educating about the best open source browser on the planet ?
So far what I did was to install the PPAPI plugin from Adobe page, enable flash in the chrome://flags, but everytime I try to load a webpage with flash content the browser crashes and displays the message: "Something went wrong."
Am I doing something wrong? I've been using Chromium 32-bit no Web-RTC builds (unofficial stable channel).
I know in the future Flash will eventually be dropped but for now it's still needed for some livestreaming websites
My way:
1. Download and install Portable version of Chromium with enabled WebRTC.
2. http://effect8.ru/soft/media/adobe-flash-player-portable.html --> Get "pepflash 25.0.0.148" PPAPI 32-bit version.
3. Unzip pepflashplayer32_25_0_0_148.7z
4. Rename pepflashplayer32_25_0_0_148.dll to pepflashplayer.dll
5. Put pepflashplayer.dll and manifest.json into the "plugins" Chromium folder
6. Launch Chromium
7. Check chrome://flash
8. Manage Flash at chrome://settings/content/flash
9. Normally, animation works on https://www.adobe.com/software/flash/about/ ;)
Unless you are doing PGO or serious debugging, 2017 should be good to go for 64-bit Chromium builds IMO. 32-bit building on a 64-bit build box should be okay now, too, from what I am seeing about recent cross architecture compilation updates.
https://bugs.chromium.org/p/chromium/issues/detail?id=683729
No sync • No WebRTC • No Widevine 60.0.3082.0 (467367) Wednesday, 26 Apr 2017
uploadfiles.io/h3ckm
(Feedback appreciated - if demand will update!)
Is it some sort of a requisite for Flash, to have Web-RTC enabled or it is a bug in the current versions of Chrome/Chromium?
Thanks in advance and keep it up guys.
Using Nik sync 60.0.3079.0 (64-bit). Not sure what build (recent, of course) started it, but now I have to enable the "Offer to translate.." option under settings in order to get the translate option on the right click context menu, but this also implies the annoying offer to translate on the upper right corner. Previously I could disable that option and still get the context menu option.
chrome://components The Chromium Authors dev 64-bit.
Chromium for 64-bit macOS - All Codecs - Thursday, 05 May 2017
Chromium 60.0.3090.0 (Official Build) (64-bit)
Revision 8bef0bcb6a3190e14abced2eefb51f37cae90abc-refs/heads/master@{#469489}
OS Mac OS X
No Sync • No WebRTC • No Widevine
uploadfiles.io/no67i
Sync • WebRTC • Widevine (chrome://components to install)
uploadfiles.io/xm62u
If I sign out from my google account, why do all of my bookmarks/favourites and passwords get wiped ?
Is that a google thing forcing us to always be logged in ? - If it is is there anyway we can stop that horrible behaviour ?
All of my bookmarks and passwords I have collected in Chrome for a few years >BEFORE< I ever let this browser note and login to my google account, so if I choose to log out, I should be left with all those bookmarks and passwords .. You would think.
I liked the idea that should I ever have a browser problem or machine problem that caused me to lose my setup, and all the accounts and web locations details that are becoming so necessary these days, that they would all be synced to cloud storage and encrypted, only for me to unlock them with a new instance of chrome on lets say a future machine ..
.. I didnt expect that I would be bullied into always having the browser logged in so that google can track everything I do, the carrot on the stick being all of my saved bookmarks and passwords will be available - Otherwise they get wiped out completely.
Does anyone else think this behaviour is right ?
If I am posting in the wrong place could someone please raise an issue in an appropriate place for the relevant coders. Thanks.
been using the same nik's stable NON-sync for days
been able to log in and log out of gmail and nothing as describe happen
(btw i dont have google account and I elect to type in password everytime)
so is it smth to do with google account or smth to so with sync?
hoepfully you find a resolution
maybe there is still a backup copy somewhere?
or system restore?
Chromium 60.0.3095.0 (Official Build) (64-bit)
Revision d5523a250fa3faed2930cabcc13ac0746c1cfb2f-refs/heads/master@{#470386}
Compiler MSVC 2017
I have a PGO build cooking, too.
@Marmaduke: Thank you for your builds. I put them manually on the site (#mac-64-bit) Please, can you contact me by mail (https://info.woolyss.com/)
@RobRich: Like ever, you are a master. Also, thank you very much for your great builds ;)
Someone can provide me links for always Chrome dev and Canary latest not offline installer.
Please
Chromium 60.0.3098.0 (Official Build) (64-bit)
Revisione2e34549299c2acc264bebabcc891a756ab35804-refs/heads/master@{#471270}
OSMac OS X
(My github is a work in progress!)
Optimization stats:
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
355 of 1377779 ( 0.03%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
9936433 of 18009824 inline instances were from dead/cold paths
1377778 of 1377779 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
1146127996516 of 1146127996516 instructions (100.0%) were optimized using profile data
The contents in this site are minimal, very practical and useful.
Thank you VERY MUCH for all this excellent site!
Cheers!
Chromium 60.0.3100.0 (Official Build) (Windows 64-bit)
Revision df78633101a43642053c681b8530c88bf7032e06-refs/heads/master@{#471635}
Compiler MSVC 2017
I'm using HenryPP's build, with chrlauncher dev-official build and PPAPI dll portable in plugins folder.
Windows 10 x64 version 1703, PPAPI from http://effect8.ru/soft/media/adobe-flash-player-portable.html
I have also tried dev-codecs-nosync/sync.
Versions:
Chromium 60.0.3105.0 (Developer Build) (64-bit)
Flash 26.0.0.110 C:\Utilities\Chromium\plugins\pepflashplayer.dll
. I used a blank username for a long time and i could see a gray small section . Now its gone. It looks great but i don't know why it "cured" this profile button :)
brand new profile, default settings.
Constant flash plugin crash in *every* page, never been able to load once.
The same config without any mods worked just fine up till maybe 10 days ago, no mods since then, just chrome updates.
Tried every possible build (dev-official, sync/no-sync, etc) but makes no difference.
Thought maybe EMET screwed up something, but disabled system it wide and for chrome specifically and restarted several times, but still no luck.
Any ideas?
Anyone else experiencing this?
TIA.
@John McClane: For me, the #flash plugin works nicely on all Chromium 64/32-bit versions. Follow tutorial at #comment-2039 and disable "Ask first" in the chrome://settings/content/flash page (https://i.imgur.com/dHHC6Z4.png). Now, the Flash plugin works for all websites ;)
Visual Studio 2017 build with profile-guided optimization (PGO). No sync. WebRTC disabled. Widevine enabled. CFG enabled.
Chromium 60.0.3109.0 (Official Build) (Windows 64-bit)
Revision 1ffa477756f92b6a6a318a0d6689e04f398c5705-refs/heads/master@{#474119}
Compiler MSVC 2017 (PGO)
i have never noticed this large of a perf difference between PGO and WPO builds previously.
As before, build times are still rather extreme. I will probably keep the existing update schedule of 2-3 weeks between releases.
@Jerry: Might be a good idea to add a "VS2017" tag to my PGO build since it is not (yet) the project's default compiler/linker.
@2090: If you are referring to the "chrome-win32" directory in the archive, it is just a directory structure. The program is 64 bit. Point the browser to about:version to verify. :)
would pref stable chrome but will give it a test run over the wkend :)
RobRich made a mistake about the version on his latest CLANG builds ;)
I corrected manually the version but the version on GitHub links still stay wrong. Nevertheless, RobRich can change them.
bug: icons are cut off:
Chromium61.0.3120.0 (Official Build) (64-bit)
Revision 9171a2ab9637d50fb574ebc354a859776efa9dd0-refs/heads/master@{#476991}
OS Mac OS X
I've updated today to 59.0.3071.86 from this page's Ubuntu repo (ppa:canonical-chromium-builds/stage) on three Lubuntu machines. Two machines are 64bit, and the third is 32bit. On the two 64bit machines, it's working fine. But on the 32bit machine, it cannot run and errors out. (will post error below, it's long). I've been using this ppa for a few months, and hadn't had any issues with any version.
Tried deleting the profile by deleting the contents of ~/.config/chromium, same error. The directory DOES start to populate, but then the process errors out. The directory is not fully populated as it should be. Tried deleting ~/.config/chromium, same.
Tried running with another, new, profile, (chromium-browser --user-data-dir=/path/), same error.
I then double checked this by reverting back to 58.0.3029.110 from the Ubuntu repos, and it works fine. Updated to 59 from the ppa, error. Checked this several times back and forth, and it's consistent. Version 59 from the ppa cannot run, and the previous version does run. I should point out that before this update to v59, the previous v58 has also been from this ppa
https://pastebin.com/4mf6X5WT
1) I uninstalled flash, but it made no difference. The first line of the error (loading the flash library) was obviously gone, but the rest of the error is the same.
2) If it's a video issue, the hardware comes into question. So I need to add that the 32bit on one my the 64bit instances are on the same machine. One machine, dual-booting two instances of Lubuntu. One 32bit and one 64bit. And as I mentioned, the 64bit works fine. (then there's another 64bit, on a different machine, which works fine as well)
Another addition I should've included in the original post: All instances of Lubuntu are 16.04.2, on kernel 4.8.0-54
I already do way too much tech reading, and whilst the "no-sync, no-widevine" etc options are really cool to have separate and distinct, this "I just want a portable install to run with the least [or I'd use Chrome itself] bullsh1t possible... is a bit of a fail, you know?
There is actually a previous version of the portableapps application for chrome/chromium which is much easier to configure for flash.
Respectfully, the only "fail" is on your part.
I guarantee you: compiling [ "no-sync, no-widevine" etc options] is not for the brain damaged or the "too cool" to think brigade.
look pretty buggy
bug: icons are cut off:
and crashing sometimes without reason, 0 problems with prev version
Sync • WebRTC • Widevine • 59.0.3071.86 (464641) • Tuesday, 6 Jun 2017
pl help
and using nik's No sync • No WebRTC • No Widevine • 59.0.3071.86 (464641) • Tuesday, 6 Jun 2017
with no whitelist on norton and No problem as describe.
you can always add to exclusion or more likely (what I did) was to list it as 'Trust'
the chromium here are not exactly the official version of chrome - you have to decide if your trust nik's or rob's or Marmaduke
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
344 of 1417494 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
9926829 of 20497462 inline instances were from dead/cold paths
1417493 of 1417494 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
365776514899 of 365776514899 instructions (100.0%) were optimized using profile data
By the way, how are the clang builds? Did anyone really test (or bench) them so far?
About Clang builds, I rarely benchmark them as VS builds probably are better optimized on Windows right now, but I do use them. Not sure about others' use, though there do seem to be occasional posts about the builds in the comments here.
BTW, while on the topic of Clang/LLVM, FYI that most of my Clang builds are now being done with external LLVM builds instead of the ones included in the Chromium repository, as the bundled builds tend to be several to many revisions behind the LLVM source. I usually do a latest SVN pull of off the LLVM source repository and build 64-bit Clang/LLVM locally before proceeding with building Chromium.
Experiencing Piriform CCleaner not cleaning Chromium cache cookies etc. Anyone else?
CCleaner 5.30.6065 has no problems. maybe clean reinstall both again?
At a loss here
Send them a link to this site that's what I did with AVG free & Pro and within hours no more problems. I use Kaspersky Pro on my Windows os and it never tries to remove it. And zero problem in Xubuntu my default OS.
I love this browser and install it on every computer I service monthly (400+)
My question is WTH happened to the settings? In the newest version (59.0.3071.86) they are horrible all that clicking right and left! And the mobile menu style why? The amount of people using mobile internet has never been over 22% and that was three of four years ago and it's been a steady drop ever since. All the websites and servers I watch it's less then 2% (3 years ago 18%) of the users on mobile? I could see making all the laptop & desktop people use mobile if there were lets say 60% of the internet users? But there are so few when you look at the amount of people online. And all of us are forced into using these horrible mobile style settings & menu's? The old setting were so much faster to work with so I'm asking are these new right & left & right... settings (mobile) menu's here to stay?
Thanks Great browser!
I agree it's a bit of pain to navigate through now, especially when setting up default site permissions. Maybe they will make a few adjustments over time, since it seems to be about Material look rather than copying mobile Chrome.
also in chrome://flags there maybe something there for you to toggle
still questioning the REAL benefit for the forced change or not offering the option for non-MD
as mentioned by many here
we all have difference screen on difference device
anyway thanks nik for your selfless work and jerry for holding up the site for free - Model citizen :)
@beast-usa: To disable Material Design:
1. Go to chrome://flags
2. Open the search box (F3 Keyboard shortcut) and type "enable-md"
3. Disable what you want (chrome://flags/#enable-md-settings in your case!)
4. Relaunch Chromium
@2135
"A merchant describes the automatic shaving machine he's selling:
- The customer rests their face here, and inside there is a set of razors that quickly perform the shaving.
- But, everyone's face is shaped differently!
- Only before the first shave..."
Would the brand of the auto shaving machine be call "new world order"? lucky guess?
I went to chrome://flags/#enable-md-settings and set "Enable Material Design settings Mac, Windows, Linux, Chrome OS" to DISABLED. Back to the fast desktop settings. lol
I'm the guy who had the crash with the previous build (1283). Confirming that 1285 works well. Thanks!
hv a gd wkend :)
I suppose it could be the file name, too. It is not actually chrome, but it does have a chrome filename, thus potentially invoking a cautionary warning.
If it persists, I can try renaming the archive download for a future release.
No sync • No WebRTC • No Widevine • 59.0.3071.109 (464641) • Wednesday, 21 Jun 2017
been using a few days - so far working great!
hv a gd wkend
Clamwin results for the current Clang x64 chrome.zip download:
Scan Started Fri Jun 23 16:34:49 2017
----------- SCAN SUMMARY -----------
Known viruses: 6298541
Engine version: 0.99.1
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 179.31 MB
Data read: 66.71 MB (ratio 2.69:1)
Time: 21.574 sec (0 m 21 s)
--------------------------------------
Completed
--------------------------------------
Chromium 61.0.3143.0 (Official Build) (64-bit)
Revision 6b4ec7b883c9758c427a883a6fe5a461c170b3bf-refs/heads/master@{#482587}
Thank you all and especially to developers for their constant work.
@Marmaduke: I updated your releases info ;)
Compiled with Visual Studio 2017 (MSVC 2017)
Chromium 61.0.3144.0 (Official Build) (64-bit)
Revision 834321a24d546bfcb0ab4a2606c5e30cfa0ab7e2-refs/heads/master@{#482964}
OS Windows
Compiled with Visual Studio 2017 (MSVC 2017)
Chromium 61.0.3144.0 (Official Build) (64-bit)
Revision 834321a24d546bfcb0ab4a2606c5e30cfa0ab7e2-refs/heads/master@{#482964}
OS Windows
I get the "We cannot find all the required components to play Netflix on this device. Please visit chrome://components, locate the WidevineCdm component, and click the "Check for update" button." message. Well, the Widevine component ?*is* there, but Netflix (And Amazon Video, for that matter) can't see it. Nothing can see it. But it's there! I can see it! AGH
Widevine is version 1.4.8.903. The developer console gives me "POST https://www.netflix.com/ichnaea/log net::ERR_BLOCKED_BY_CLIENT". I'm at a loss. Halp
I never use the functionality of Widevine. In order to enable Widevine support in Chromium macOS, I used Eloston's (ungoogled chromium) patch.
To "widevine_cdm_version.h", I've added:
#define WIDEVINE_CDM_AVAILABLE
#define WIDEVINE_CDM_VERSION_STRING 1.4.8.903
But on the test page https://shaka-player-demo.appspot.com the Widevine options are greyed out.
I always strip/deactivate all the privacy/security leaks in macOS on my virtual/physical machines; in doing so I might have deactivated DRM.
I will upload an amended version of Chromium with the aforementioned changes.
@nik @RobRich
Does Widevine function correctly in your respective build(s) of Chromium?
If a solution to Widevine in macOS can't be found then I will deactivate the functionality in subsequent builds.
@Craig: Would you please try this new revision with Netflix. I've tested Widevine/DRM (all tests passed) at https://bitmovin.com/mpeg-dash-hls-drm-test-player and https://shaka-player-demo.appspot.com
I really appreciate you helping. I'm a pretty computer-savvy guy and it's unusual that I come across a problem like this I can't solve.
I did grab that latest version you posted there, and same Netflix error message. Additionally, when I visit the Shaka demo, all the Widevine options are greyed out. While bitmovin.com, however, reports that widevine is available as an available system for EME, I cannot load the video at the top of the page. "DRM: Failed to create and initialize a MediaKeys object"
Same in Incognito mode, so I don't believe it's an extension doing it. Is there some console output that would be useful here?
Widevine Chromium console log of https://shaka-player-demo.appspot.com/demo/#asset=//storage.googleapis.com/shaka-demo-assets/angel-one-widevine/dash.mpd;lang=en-GB
https://github.com/macchrome/chromium/releases/download/v61.0.3143.0-r482587-macOS/shaka-player-demo.appspot.com-1498916028327.log
From a standard macOS 10.12.4: no web filters/sanitising proxies, no firewalls, no security/privacy enhancements, etc. The Widevine components where obtained from the latest stable release of Chrome.
many thanks for that
Chromium 61.0.3147.0 (Official Build) (64-bit)
Revision d5588cf4ffb5a932dcbfd87cd7761d390c790ea9-refs/heads/master@{#483909}
https://demo.castlabs.com/ is another good Widevine/DRM test site.
Mac users (backup and) delete "/Users/<whatever>/Library/Application Support/Chromium/Widevine".
I've tested the Widevine/DRM functionality extensively and am satisfied.
Hackintosh users make sure you have a UUID and such.
Can I ask what you changed / updated on the backend to make it work? I'm curious. Regardless, thank you very much.
That's good to know.
To "widevine_cdm_version.h", I've added:
#include "third_party/widevine/cdm/widevine_cdm_common.h"
#define WIDEVINE_CDM_AVAILABLE
#define WIDEVINE_CDM_VERSION_STRING "@WIDEVINE_VERSION@"
and I noted that the release version of Chrome stores the Widevine library in the equivalent of:
Chromium.app\Contents\Versions\61.0.3147.0\Chromium Framework.framework\Versions\A\Libraries\WidevineCdm\_platform_specific\mac_x64\
I also realised that there was an older - possibly conflicting, obsolete and redundant - version of the Widevine library in:
/Users/<whatever>/Library/Application Support/Chromium/Widevine
Nice catch. And thanks for all the work you put in helping me track down this problem, digging through the internals of Chromium, and your help putting together your releases in general.
For anyone who comes after me who still encounters the "Something went wrong" error message with Netflix, setting your user agent string to "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3147.0 Safari/537.36" does the trick. Apologies, admin, if this isn't the right place to post "support" information like this.
@Craig: All is ok. Thank you for your help too!
@marmaduke: Great work and help! I updated your section. Thx
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
331 of 1440783 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
10438332 of 20674769 inline instances were from dead/cold paths
1440782 of 1440783 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
420941766409 of 420941766409 instructions (100.0%) were optimized using profile data
I installed Chromium 64 bits by installer (the first). I am in Windows 10
It doesn't have the right to write anywhere (contact the administrator, etc)
This pb is proper to Chromium; Can you help me please, thks
- Clang builds: https://github.com/RobRich999/Chromium_Clang/releases
- PGO builds: https://github.com/RobRich999/Chromium_PGO/releases
I've noticed that swiping left and right on my wireless Apple mouse ("magic mouse") doesn't work like the back and forward buttons any more, and Googling has not led me to a current flag that re-enables it yet. Accidentally scrolling back was frustrating at first, so I can understand why this would be a good thing to disable, but I got used to it and now I like it, so if I can turn it back on for myself, that'd be cool.
I'll do some research.
https://github.com/Eloston/ungoogled-chromium/tree/develop
I prefer to use Gorhill release uBO-Extra, he knowns what he create in depth in uBlock Origin.
It's just in opinion.
Full multi-touch functionality (on macOS) is a job for the Chromium authors; perhaps when they've implemented mp3 they'll give it a try.
@2198: Yes. It was always my intention not to enable WebRTC on any of my builds. Initially getting WebRTC to build was a challenge!
In my opinion, while the former is important, as it protects from invisible yet serious threat, using the latter just gives undeserved views to websites that are showing the door to safety-conscious users.
"For browsers based on Chromium 57 and below, WebSocket connections are not available to the chrome.webRequest API. This companion extension (it's pointless to use it as a standalone) will allow uBlock Origin to become aware of WebSocket connection attempts: they can be filtered, and will be reported in the logger."
"Instart Logic's technology used to disguise third-party network requests as first-party network requests, including the writing/reading of third-party cookies as first-party cookies. I consider this to be extremely hostile to users, even those not using a content blocker, as it allows third-party servers to read/write cookies even if a user chose to block 3rd-party cookies through your browser setting.
The company behind the technology understand how hostile its technology is to users, and thus tries to hide what is being done by making it difficult to investigate by detecting whether the browser's developer console is opened, and when it detects it is opened, it ceases completely to make use of the obfuscation mechanism. The developer console-detecting code works only for Chromium-based browsers however, and therefore the obfuscation technology is not used when using Firefox (a different web page is served for Firefox)."
Read all : https://github.com/gorhill/uBO-Extra
Chromium62.0.3165.0 (Official Build) (64-bit)
Revision 00043bdefebe1d854b0cffbd1d35d90c0091057c-refs/heads/master@{#488859}
OS Mac OS X
[Mac users (backup and) delete "/Users/<whatever>/Library/Application Support/Chromium/Widevine".]
Toolbar support is only available in macOS > 10.12.1
Can anyone else confirm?
Another bug: cannot use Discord in browser anymore, can only type 2 letters, then the textarea loses focus. Then I have to click in the textarea again, but it only allows me to type one more letter. Discord is basically unusable because of this. On the previous (61) build, this issue didn't exist. There was no meanwhile update to Discord.
I would go back to 61 until this gets fixed.
A question : do you take all the security fixes mentioned here ?
https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html
Nonetheless, your work is amazing. Thanks for all the updates.
has slight momentary black screen (~1-2 seconds) on some charting website (only on the charts not the whole webpage) but came back alright
prob has to do with some extensions?!
Otherwise ALL GOOD !!!
Thanks nik and Jerry for your time and effort :) Much appreciated Hv a gd wkend
@Jerry: I have discontinued Widevine DRM for my builds. Please update accordingly. Thanks! :)
@Nik and other builds, something of possible interest:
https://chromium.googlesource.com/chromium/src/+/master/docs/jumbo.md
Enabled it for my latest builds. I did not gather stats, so no build time data, but it seemed faster. The default file merge limit has been updated to 100, though I suppose it could change with revision, so YMMV for now. It can be manually tuned, but check the Google Doc at the above link about diminishing returns and potential parallelization performance penalties if increasing beyond 200.
Also, when I click an Youtube link from another page, the launched tab just keeps loading the video forever while displaying this:
Never seen this issue before either. Seems to be some problem with a codec. I haven't installed or removed any codec in the meantime. Youtube videos launched from another page work fine in Chrome, Firefox and Edge. So, maybe it's just an issue with this version of Chromium.
Chromium 62.0.3170.0 (Official Build) (64-bit)
Revision eb3ac0215bfc80f02ceb9575dafb79142110d7c7-refs/heads/master@{#490294}
Compilerclang
While on the topic, a quick note for anyone comparing issues between various build types. After patching a couple of SDK files, I am now building both my Visual Studio 2017 and Clang builds against the Windows 10.0.15063.0 SDK. There is a (slight) chance issues might not exactly reproduce (even at all) between different SDK versions, as Chromium currently defaults to the 14393 SDK. As with most of this stuff, YMMV. ;)
@RobRich: I updated your builds info. Keep up the good work! ;)
"When the Creators Update SDK (10.0.15063.0) came out it was buggy so we
locked Chrome builds to to the Anniversary Edition SDK (10.0.14393.0).
However this means that if developers only install the latest SDK they
cannot build Chrome. This is particularly frustrating for developers who
want to build Chrome with VS 2017, which now ships with 10.0.15063.0.
Since the 10.0.15063.468 SDK fixes the bugs this change removes the
SDK limitation. Builds with the local toolchain will now use the latest
SDK version installed. 10.0.14393.0 is the minimum."
Remove Chromium from Control Panel.
If you cannot:
1) Show hidden files and folders in your OS
2) Remove Chromium.dll, chrome.exe, chromium.exe.
3) Remove C:\users\{username}\AppData\Local\Chromium\ and C:\Program Files\Chromium\
4) Clean registry (with Ccleaner for example)
https://en.wikipedia.org/wiki/LLVM#Linker
----------------
@2222 & @2224: Interesting on the the ongoing black screen issue. I did not do much testing, but disabling Partial Swap seemingly fixed the black screen issue on one of my affected Win10 systems. Have ya'll checked crbug.com for a related issue, yet?
----------------
@marmaduke Yeah, I spotted similar in the bug tracker on VS2017. I used one of the dev's patched SDK files, plus I had to remove an apparently invalid include in another SDK file to get Chromium to build with 15063.0 using Clang. I will try 15063.468 for my next round of builds.
----------------
I have an updated PGO build cooking. Needs profiled and second-pass relinking. Probably sometime Monday assuming I feel like it.
Here's a capture of the issue I'm having with Discord. The textarea is losing focus, everytime I'm trying to type something in it.
https://www.youtube.com/watch?v=yO34rhuJoyA
Btw, thanks guys for building this Chromium. I didn't want this to sound like I don't appreciate your efforts. Just wanted to report this issue, because I'm using discord every day, so it's kind of annoying that now I have to go back to the desktop application.
I don't have any add-ons or extensions that could mess with that. Just an adblocker and it has worked before with it.
This issue doesn't exist in other browsers (regular Chrome, Firefox, Edge, etc), I tested in all of them. So, I suppose something must have changed in this build. I haven't made any other changes to the system. I did upgrade Win10 to Creators', but that was before upgrading Chromium and it was working fine.
"Chrome switched to Clang on Windows last week, and it's a very big deal. Thanks to @reidkleckner, @thakis, @hansw2000, et al."
Also: https://twitter.com/marcaruel/status/892017367454273538
"Chromium now defaults to clang on Windows
In ~3mo, 1 Billion Chrome users will get to run clang generated binaries"
@WildByDesign Figured something was up. I had to manually set "is_clang = false" for my pending PGO build, as otherwise it tried to default to the revision's own provided LLVM (even despite invoking PGO). I still need to see what linker is being called, though I suspect LLD, as it is working now for even 64-bit non-component builds.
Assuming it is Clang+LLD, I am not sure what is going to happen with CFG/CFI support in the near term. I could not force it on my Clang+LLD builds over the weekend, so support does not yet seem available. I am having Jerry pull the CFG tag on my Clang builds for now.
While on the topic, I typically roll my own local LLVM tools, as Chromium's bundled LLVM usually is several to many revisions behind the LLVM trunk. As usual, there could be a little "YMMV" with my builds compared to an expected standard build.
Chromium 62.0.3173.0 (Official Build) (64-bit)
Revision 0f3fc0e039844614d7db61352dc9ce9d09b9abbf-refs/heads/master@{#490706}
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3173.0 Safari/537.36
Command Line "C:\Users\RobRich\AppData\Local\Chromium\Application\chrome.exe" --flag-switches-begin --autoplay-policy=document-user-activation-required --enable-browser-task-scheduler --delay-reload-stop-button-change --no-pings --blink-settings=disallowFetchForDocWrittenScriptsInMainFrame=true --enable-distance-field-text --enable-checker-imaging --enable-clear-browsing-data-counters --enable-fast-unload --disable-gpu-rasterization --enable-quic --enable-use-zoom-for-dsf=true --enable-lcd-text --reduced-referrer-granularity --save-page-as-mhtml --ui-disable-partial-swap --v8-cache-strategies-for-cache-storage=aggressive --windows10-custom-titlebar --enable-features=AutomaticTabDiscarding,BackgroundVideoTrackOptimization,ExpensiveBackgroundTimerThrottling,FontCacheScaling,FramebustingNeedsSameOriginOrUserGesture,IdleTimeSpellChecking,MemoryAblation,MemoryCoordinator,OffMainThreadFetch,PauseBackgroundTabs,ResourceLoadScheduler,ScrollAnchoring,brotli-encoding,browser-side-navigation --disable-features=NoStatePrefetch,SpeculativeResourcePrefetching --flag-switches-end
CompilerMSVC 2017 (PGO)
You can try the usual suspects. Disable GPU hardware acceleration. Reset custom about:flags settings to defaults. Disable all extensions, then re-enable one-by-one. Do a clean browser install - remember to backup bookmarks first.. ;)
@Dolan: Temporarily disable that ad blocker, too. It could be new rule or similar is causing an issue. Also search crbug.com to see if there is a related bug report.
@Jerry: Thanks for the tag updates. :)
Someone has same problem? I use a latest Chromium and OS X 10.10.5. Two finger swipe in opened tabs just breaks down after night. I mean, I use Chromium all day and everything works fine. I go to sleep and next morning two finger swipe (only for previous/next pages) doesn't work. When I close this broken tab and open new swipe wokrs.
And it's not every day. I don't understand where is cause.
Also, now videos and streams start normally again. They used to keep loading until I clicked on the progress bar to start from a later point.
Thanks a lot for the fixes. 👍
All back to normal. 👌
it's been a while since I compiled my own version of Chromium, around April '17 I guess?
I was going to update my development build last weekend but failed to include hevc/h265 decoding.
Apparently the ffmpeg directory structure changed, can anyone point me towards an updated set of patches to enable hevc demuxing?
This is being built on and for Win10 x64.
Appreciate your work and input, thanks everyone!
As for my current plans, I am continuing with the migration of my Clang-compiled builds to the open-source LLD linker now that 64-bit non-component builds appear to be once again working with it. Note, CFI(/CFG) is not yet available for Clang+LLD builds, but it was not available for a long time with Visual Studio builds, either. ;)
Thanks a lot for sync, no webrtc build!
Chromium62.0.3180.0 (Official Build) (64-bit)
Revision 869a82d654689a118a22bdd340b8433ac6ac85e3-refs/heads/master@{#492595}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- nosync without WebRTC and Widevine support
- sync without Widevine and WebRTC support
- official build
(Widevine support at the moment is broken in the Chromium macOS developer build).
It also has some stability issues, but the discrete graphics thing is a killer :(
I was not familiar with the "discrete graphics thing".
I don't know if this is applicable to Chromium: Chrome can be lauched from the command line with this argument: --force_discrete_gpu=0. Others have prevented Chrome switching to discrete graphics by unchecking (in chrome://settings) "Use hardware acceleration when available".
https://bugs.chromium.org/p/chromium/issues/detail?id=754589
First suspect is usually about:flags settings. Try setting them to default assuming you have any custom flags set, then work from there.
----------------
Updated PGO build available. Optimization stats:
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
243 of 1466526 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
11547822 of 21923246 inline instances were from dead/cold paths
1466524 of 1466526 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
415784549945 of 415784549945 instructions (100.0%) were optimized using profile data
What do you think about this : https://jspenguin2017.github.io/uBlockProtector/
It's enough to use: µBlock Origin + µBO-Extra ?
Or better to use : µBlock Origin + µBO-Extra + uBlock Protector Extension ?
uBO Extra is no longer needed when you have uBlock Protector extension.
Personally, I would recommend staying with uBO + uBO Extra. But if you have a pressing need to use sites that would otherwise prevent you from entering unless you turn off content blockers* - then uBO + uBlock Protector.
* From my observation so far, most sites that do such thing are also exposing their users to potentially malicious ads and tons of trackers, and therefore they don't deserve any views.
Filter rule removed by DMCA request, because it was bypassing anti-adblock wall.
Using Archive.zip version with chrlauncher on Windows 7 64bit.
SHA1 hash is the same, so download was fine. Deleted profile so it would do first run and create a new one. Not sure what else to try.
I've rolled back to the previous PGO build. Might fiddle with it later, it must be something on my system if it works for you. Thanks for confirming, much appreciated =)
You can add this URL in uBLOCK ORIGIN : https://ssl.bblck.me/blacklists/ublock-origin.txt
( Or in Adguard app )
Or use extension or other solution here :
Source : https://github.com/paulgb/BarbBlock
@Jerry Hello, i remember you are developper.
Maybe if you have time or you want, you can participate at this project.Very interesting for Chromium. I think.
Cookie-AutoDelete Chrome extension.
Above all it, he want happen deleting Localstorage : https://github.com/mrdokenny/Cookie-AutoDelete/issues/44
Issue open since 2011 ( shame on developper ): https://bugs.chromium.org/p/chromium/issues/detail?id=78093
Home page : https://github.com/mrdokenny/Cookie-AutoDelete
Webstore : https://chrome.google.com/webstore/detail/cookie-autodelete/fhcgjolkccmbidfldomjliifgaodjagh
Best regards.
Chromium 62.0.3191.0 (Official Build) (64-bit)
Revision 72f8c23709f8159233eba6c1bfa2ed76bc825d3a-refs/heads/master@{#495832}
Compiler clang+lld with thinlto
It is built with Clang+LLD using ThinLTO optimization. (Thin)LTO is not (yet) supported by the project, so a huge YMMV here.
https://clang.llvm.org/docs/ThinLTO.html
http://blog.llvm.org/2016/06/thinlto-scalable-and-incremental-lto.html
I forced ThinLTO via manually adding a compiler flag in the project's general build configuration script.
Performance hopefully should - or more like *might* - be improved. I have not done much testing other than making sure the build loads and renders a few web pages.
----------------
@Ball Have you tried --force_integrated_gpu via command-line argument? I am not sure if it is still supported, as I do not have a modern MacOS system here.
Any reason why the previous build would work on a Ramdisk and why the current one doesn't?
I'm guessing new code in chromium, since Nik's build gives the same result.
Chromium 62.0.3192.0 (Official Build) (64-bit)
Revision b57c9753a6187ac1f118d6935493c58d0aecd424-refs/heads/master@{#495845}
Compiler clang+lld with thinlto
I changed where the ThinLTO cflag was being passed to mimic how VS builds do WPO versus yesterday's outright sledgehammer approach to implementing ThinLTO. The mini_installer now builds, file sizes are more towards expectations, plus there could be other fixes with the change. Casual surfing seems okay thus far. SunSpider might have picked up a ms or few on my Core i5-7300HQ notebook, though I did not do a serious test. Peacekeeper crashes, but "whatever" for now IMO.
Barring any major usability issues - Peacekeeper crashing aside ;p - over the next few days, I am likely to enable ThinLTO for future Clang+LLD builds.
https://bugs.chromium.org/p/chromium/issues/detail?id=52663
https://bugs.chromium.org/p/chromium/issues/detail?id=176727
There is a flurry of file activity upon loading Chromium, as it is loading and accessing various resources.
After a few seconds, it settles down. Load a page, and it churns through the usual stuff: cache, history, cookies, top sites, etc. It appears file buffer flushes are occasionally invoked for explicit writes for at least some priority file creations and/or updates that would be needed for example to restore a session. Otherwise, Windows handles it own write caching and lazy writes unless those buffer flushes are invoked.
If you move a few GB of data through your browser per day, then yeah, there is a decent chance you are probably going to move a few GB through your data storage - HDD, SSD, ram drive, etc. - per day as well. Perhaps (much) less if certain caching is disabled, like by modifying disk-cache-size and media-cache-size from the command line. YMMV.
Risks? A spinning HDD might spin more often and/or longer, thus increasing energy consumption, heat, etc. A SSD might not go into a low-power state as often, which is again a possible energy issue, though a typical consumer SSD tends to use only a few watts under heavy load anyway. The bigger SSD concern could be data writes causing excessive drive wear, though a modern SSD with wear leveling running along with a modern OS using AHCI and TRIM can have write endurance ratings measured in the hundreds of TBs,
For an alternative, consider installing a Chromium portable version to a RAM drive if it is truly a concern. Many RAM drive utilities also offer the ability to easily save and restore the RAM drive image on system shutdown and startup.
WebStore : https://chrome.google.com/webstore/detail/ultrablock/ijnodnmgpgmgaajhagolfiemmmamfcgb
Me , yes . Works good. Not less ; no more. Ublock origin or Adblocker ; difficult to configure.
The negative point , can not disable random user agent. Broke some site.
And you have choice if you want sent data collect of your use to UltaBlock.org
Read. Privacy Policy on UltaBlock.org : ( Data the extension collects )
But you do what you want !
- closed source
- has an apparently copypaste license ( "Content and Accounts" policies? Certainly neither of those are a part of using UltraBlock or its site), a common indicator of a scam/malware service or software.
- has very little userbase (7 votes, 79 users, and 3 opinions currently)
Good luck to it in competing with popularity and reputation of open source uBlock Origin, which is also simple for a non tech-savvy user, and doesn't rely on data grabbing mechanisms, optional or not. Same for its common "partner in crime", Privacy Badger developed and maintained by Electronic Frontier Foundation (https://www.eff.org)
And Ghostery is closed source too and it is very widespread.
And it collects user data.
You do not like so much ; what ever. Ok. Thank You Best Regards.
And you you are not Anonymous maybe?
Contradict and annoying.
You cumulate sir.
The people here know very well what they do.
And Jerry Admin monitor perfectly his site. When there is danger, he erases the message.
This is dear friend on this words I say bye bye. (For always, i hope)
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
287 of 1401048 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
10574932 of 19493833 inline instances were from dead/cold paths
1401046 of 1401048 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
211202524477 of 211202524477 instructions (100.0%) were optimized using profile data, and the rest of the instructions were optimized without using profile data
--------------------
FYI. The latest Clang+LLD 64-bit build has ThinLTO link time optimization enabled. It is an interprocedural optimization technique. Think something similar to WPO, but using the open source LLVM compiler and linker.
https://en.wikipedia.org/wiki/Interprocedural_optimization
ThinLTO can often deliver much of the optimization benefits of traditional monolithic LTO, but usually with with much improved build times due to increased parallelization, especially for large projects. Check the build processor graphics for a quick comparison of the two techniques:
http://blog.llvm.org/2016/06/thinlto-scalable-and-incremental-lto.html
The only immediate downside I am seeing right now is an increase in output binary sizes, but I am not too concerned about the difference, as much of Chromium is optimized for performance over size anyway when doing an "official" build on Windows.
Note, ThinLTO is not an official current project build technique, as in there is no GN build argument to easily enable it for a Windows build. I am manually modifying the project's compiler build configuration file for now. It is a quick edit to set a new conditional, but anyway, FYI and YMMV as usual.
Jerry should be adding a ThinLTO tag to the Clang+LLD 64-bit build soon. :)
John Doe Chrome improves privacy and reduces fingerprinting effectivness.
*Replaces Http headers with generic ones
*Replaces javascript window, navigator and screen attributes with generic ones
*Removes analytics parameters from urls
Peacekeeper (higher is better)
PGO-r497669: 4280
ThinLTO-r497813: 4392
MotionMark (higher is better)
PGO-r497669: 295.55±16.19%
ThinLTO-r497813: 316.14±19.83%
ARES-6 (lower is better)
PGO-r497669: 35.07±0.42ms
ThinLTO-r497813: 33.44±0.47ms
SunSpider (lower is better)
PGO-r497669: 293ms+/-0.7%
ThinLTO-r497813: 290.2ms+/-0.9%
Those are my latest publicly available ThinLTO and PGO builds. I know the build revisions are different, but they are still relatively close enough for (extremely) casual testing IMO. Note I am not factoring memory, power, etc. in the tests; just basic performance. The test system is a notebook featuring an Intel Core i5-7300HQ, 16GB DDR4, GTX 1050 2GB, Win10, etc.
Interestingly enough, my PGO build even included Peacekeeper as a part of its instrumented profiling for optimization, yet ThinLTO still returned a higher score there! I would have added JetStream overall scores as well, but one of the JetStream benchmarks crashed on my ThinLTO build. It be could be a revision issue, so I will try to revisit later.
As to the build processes involved, PGO takes several hours on my 32-core Opteron box and like 150GB-180GB of output space to build. ThinLTO takes a faction of the time and currently less than 3GB of output space to build.
I do not intend to immediately discontinue PGO builds, but the reasons to keep building PGO over the long term are becoming considerably less compelling for me, especially if there are no longer appreciable performance benefits compared to a much less intensive build process.
I also finally took a look at a recent build log. Clang+LLD with ThinLTO took a little over an hour to do a fresh build. I used my own local release build of LLVM with a few tweaks, so compiler and linker performance could vary compared to the LLVM tools provided by the Chromium repository.
Looking forward I might have something else interesting to try in the near future if/when I feel like delving into the process. I will post details and hopefully an experimental build when possible.
Chromium 63.0.3203.0 (Official Build) (64-bit)
Revision f8eb347a09709d0ae8b84bf5f2dfffe670dec552-refs/heads/master@{#499157}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- nosync without WebRTC and Widevine support
- sync without Widevine and WebRTC support
- official build
After much consideration in recent days, Visual Studio 2017 64-bit with PGO builds are discontinued. There is just not enough (any?) truly appreciable performance returns for the build times involved, especially with much less build-intensive Clang+LLD with ThinLTO builds now offering similar or sometimes even better raw performance in my basic benchmark testing.
thanks for the hard work, but it is sad to see the VS2017 builds go. For me and all the benchmarks I´ve done, they have been beating the Clang builds each and every time. Have a look at my results:
RobRich VS2017 (62.0.3184.0):
peacekeeper.futuremark.com 4942
web.basemark.com 423.34
browserbench.org/JetStream/ 186.05
browserbench.org/ARES-6/ 33.05
RobRich Clang (62.0.3202.0):
peacekeeper.futuremark.com 4718
web.basemark.com 389
browserbench.org/JetStream/ Crashes (Aw, Snap!)
browserbench.org/ARES-6/ 33.18
This is a considerable difference in those benchmarks - VS2017 beats Clang hands down and by a good margin and always had since you´ve started these VS2017 builds. I hope you can reconsider your choice and bring them back on, given that they are that much faster than the Clang builds.
Also ThinLTO is not officially supported on Chromium builds for Windows, so there should be room for more improvements once devs start actively targeting it. That said, I am not even sure about any timeline specifics on migrating the official Windows build linker to LLD.
As for my personal interest, I recently added a couple of more compiler configuration conditionals to get ThinLTO working with the full_wpo_on_official build argument. I need to get a fresh build to push a public release. Maybe over the weekend.
If I get full_wpo_on_official working locally, then there is a chance for something even more exciting that hopefully should further improve performance. No promises as it might be a wild-goose chase, so I will just call it an idea for now. ;)
thanks for your reply. I am running Windows 10 Creators Update (1703 / 15063) x64 on an i7-3770k @ 4.4 GHz. Any bench I´ve done looks exactly like this, regardless which one, they are all slower with the Clang builds (also the previous months as I have been testing this often actually). Speed-wise it goes like this each and every time for me:
(Slowest): Official Google Builds
(Mid): Clang
(Fastest): VS2017
Hence you can imagine how much I regret that you are ditching VS2017, especially since the difference is not marginal but noticeable and reproducible for me. Hope you can bring them back....
Cheers,
Lorenz
I previously have done an internal clang build with microarchitecture targeting for the max optimized parts of the source, though I did not note much of a difference in a quick test. Could be worth a revisit.
As to VS2017, I might consider adding back a build with WPO instead of PGO. I will have to think about it, as even WPO is a time consumer with VS. Maybe do a test build for you and others to try.
I totally understand that you like Clang and I will not force you into anything, but the VS2017, no matter what, have always been faster than any of the Clang builds you had done - and I have tested that so many times during the past months...
I understand that VS2017 with PGO takes a long time, but it´s worth the great performance improvement over currently any other compiler (as it seems). I hope you can bring them back on :)
Thank you,
Lorenz
I recognise and deeply appreciate Rob's time and effort in making PGO builds for us, but if the current ThinLTO builds much faster and deliver pretty much the same result, I'm all for it. I see it as a trade off, we might get more builds more often which would make revisional bugs more bearable. =P
But in webstore it's https://chrome.google.com/webstore/detail/decentraleyes/ldpochfccmkkmhdbclfhpagapcfdljkj
Is it still happening?
I might have an idea or two about maybe speeding up PGO builds. There is a chance for reconsideration if there is an improvement in build time. I also know the official buildbots use a script to automate profiling. I might have to look into that as well.
Right now it is churning through a build of LLVM with custom optimizations and WPO using VS 2017.
Is this something that can be fixed for users of Chromium who use Netflix?
IE11 works perfectly fine, but your previous versions of Chromium (with sync) worked prior.
Thanks for your time!
~Dustyn~
Can you play any of the videos using Widevine DRM at the below link?
https://shaka-player-demo.appspot.com/demo/
Any chance for updated build? I believe it has been reported in: https://chromium-review.googlesource.com/c/chromium/src/+/644907
Chromium 63.0.3206.0 (Official Build) (64-bit)
Revision f8656a9f4d11201ee19392f3939d647fca11f357-refs/heads/master@{#499489}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- nosync without WebRTC and Widevine support
- sync without Widevine and WebRTC support
- official build
Have you tried updating components?
chrome://components
No data colected. If you find bug you can contact hin .Have his email on download web page store
7 Times Faster : https://chrome.google.com/webstore/detail/7-times-faster/bcidahcpjehlemnbmeaepadalhjofnmp
How are you scrolling: mouse, keyboard...?
Octane 2.0
test: 36652
pgo: 35619
JetStream 1.1
test: 185.50
pgo: 183.83
ARES-6 1.0.1
test: 26.71ms
pgo: 27.25ms
SunSpider 1.0.2
test: 229.6ms
pgo: 234.6ms
Basemark Web 3.0
test: 818.06
pgo: 790.75
Peacekeeper
test: 5419
pgo: 5271
"PGO" is my latest public build. "Test" is an optimized Clang build built last night, which I will try to release later today if I feel up to it.
Note PGO is back in the listings above, as I will try to do an occasional build for comparsion testing, though note it is no longer a personal priority.
The Chrome components you are referring to are all up to date. I was hoping I would have caught the attention of Nick specifically as it's his builds that are in question but perhaps... your builds share the same issue? Nevertheless I am appreciative and quite thankful for any assistance you may provide. :)
@Dustyn: The reason I might not be much help is my builds do not have Widevine included, so unless Netflix has adopted other digital rights managements platforms, my builds should not support Netflix playback at all. Thus I have not personally experienced the issue. ;)
It appears Widevine is working and updated as per your testing. Curious, are you showing any GPU errors? Replicate your Netflix error, open the page chrome://gpu in another tab, and check the log messages at the bottom the page.
If the log does not lead to anything informative, do you have any custom configuration flags in chrome://flags set?
While in the flags, you can try temporarily disabling hardware acceleration of video playback as a troubleshooting measure, too.
chrome://flags/#disable-accelerated-video-decode
Driver Bug Workarounds
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_delayed_copy_nv12
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_framebuffer_cmaa
exit_on_context_lost
force_cube_complete
scalarize_vec_and_mat_constructor_args
texsubimage_faster_than_teximage
Problems Detected
Some drivers are unable to reset the D3D device in the GPU process sandbox
Applied Workarounds: exit_on_context_lost
TexSubImage is faster for full uploads on ANGLE
Applied Workarounds: texsubimage_faster_than_teximage
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
ANGLE crash on glReadPixels from incomplete cube map texture: 518889
Applied Workarounds: force_cube_complete
Framebuffer discarding can hurt performance on non-tilers: 570897
Applied Workarounds: disable_discard_framebuffer
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Zero-copy NV12 video displays incorrect colors on NVIDIA drivers.: 635319
Applied Workarounds: disable_dxgi_zero_copy_video
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Decode and Encode before generateMipmap for srgb format textures on Windows: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Delayed copy NV12 displays incorrect colors on NVIDIA drivers.: 728670
Applied Workarounds: disable_delayed_copy_nv12
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Log Messages
[11032:12528:0905/201926.053:ERROR:gles2_cmd_decoder.cc(8948)] : [.DisplayCompositor-00000241D107AAE0]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[11032:12528:0905/201926.053:ERROR:gles2_cmd_decoder.cc(8949)] : Context lost because SetDrawRectangleCHROMIUM failed.
[11032:12528:0905/201926.053:ERROR:gles2_cmd_decoder.cc(5417)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[11032:12528:0905/201926.053:ERROR:gpu_channel_manager.cc(195)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
Chromium 62.0.3198 PGO
Jetstream - 263.04 ± 2.9534
Speedometer - 190.4 ± 0.91
Chromium 63.0.3207 thinLTO WPO
Jetstream - 269.32 ± 3.8748
Speedometer - 196.3 ± 0.60
Good stuff!
The new layout kinda hurts my eyes :)
Thanks In advance
@2338: AFAIK, much of the previous non-MD code is simply not there anymore. Trying to gather the likely numerous commits and doing successful reversions could be a code management nightmare IMO, and especially if newly introduced components and features explicitly rely upon MD UI code that has no likewise functionality in previous UI code.
For the sake of feedback about user into the wild :
PGO (dev-pgo-nosync / Chrome 62.0.3198.0)
VS
CLang (dev-clang-nosync / Chrome 63.0.3207.0)
- Windows 8.1 64-bit
- Intel Core i7 4710HQ @ 2.50GHz
- RAM : 16,0 Go Canal-Double DDR3
- Monitor 1920 x 1080 @60Hz
- Intel HD Graphics 4600 + NVIDIA GeForce GTX 850M
- Samsung SSD 850 EVO 250GB
/Octane 2/ Higher Better
PGO : 30870
CLang : 31766 (winner)
/MotionMark/ Higher Better
PGO : 248.89 ±29.07%
CLang : 286.69 ±24.19% (winner)
/Basemark Web 3.0/ Higher Better
PGO : 650.11 (winner)
CLang : 635.59
/Speedometer/ Higher Better
PGO : 133 ±18
CLang : 145.0 ±1 (winner)
/JetStream 1.1/ Higher Better
PGO : 175.49 ±10.161 (winner)
CLang : Freeze on typescript
/Re-Test/
PGO : 163.88 ±10.341
CLang : 166.67 ±9.5386 (winner)
/Ares-6 1.0.1/ Lower Better
PGO : 31.55 ±0.79ms
CLang : 31.18 ±0.78ms (winner)
/Sunspider 1.0.2/ Lower Better
PGO : 255.2ms ±1.7%
CLang : 249.1ms ±1.3% (winner)
/PeaceKeeper/ Higher Better
PGO : 4822
CLang : 5019 (winner)
wow, that new VS2017 build you´ve added is AMAZING. It is beating any of the Chrome builds you´ve ever done in my tests.
Look at these benchmarks (http://peacekeeper.futuremark.com/):
RobRich VS2017 (62.0.3184.0) = 4942 (the one I´ve been using previously)
62.0.3198.0 (497669) • Sunday, 27 Aug 2017 (RobRich pgo vs2017 cfg lkcr 64-bit) = 5106 (WOW!)
63.0.3207.0 (499551) • Tuesday, 5 Sep 2017 (RobRich wpo ThinLTO clang lldl kcr 64-bit) = 4798 (Clang losing out big time as usual)
Whatever you´ve done, keep those VS2017 builds coming, they beat Clang (and not just in that benchmark) big time.
Thanks so much,
Lorenz
Curious, during benchmarking is your system running a power profile with processor and/or GPU frequency scaling enabled?
@Lorenz: Thanks for the clarification. Just curious about possible reasons for the differences, as I am no longer showing any significant raw performance advantages for PGO in most benchmarks tried here.
Anyway, I am going to try keeping occasional PGO builds going to do continued comparison testing.
yes, it is kinda odd that we both get such different results. As I saw and just fully realize now, we have both tested the exact same builds, also with PeaceKeeper. Your results were:
/PeaceKeeper/ Higher Better
VS2017 PGO : 4822
CLang : 5019 (winner)
And my results were the exact opposite:
VS2017 PGO : 5106 (winner)
CLang : 4798
That is very odd if you ask me - and we are both using an Intel platform and Windows 10 (15063 currently) - all x64. Not sure what to make out of all of that, but you see, for me, and possibly others, it would be cool if you could keep the VS2017 builds as well, as they are faster by a good margin for me.
Thank you so much:)
The clearest difference IMO noted thus far is our Intel x86 boxes are using different processor architectures. That could mean a myriad of things related to instruction flow, scheduling, buffering, branch prediction, etc.
For example, Intel added a third vector integer ALU to Skylake and later archs that might benefit IPC for vectorized loops. Optimizations generated by different loop dependence analysis for auto loop vectorization might or might not exploit the (hopeful) ILP benefit of additional hardware SIMD units due to contentions, stalls, etc.; and especially so if comparing two compilers with two likely different analysis algorithms.
@Evan: ArnoldTheBats compiles #chromium-os for few years! ;)
I don't know if you are aware.
3 big problems with Firefox from 15-20 sept and more with version 57.
Source:
https://www.ghacks.net/2017/08/22/mozilla-plans-to-collect-anonymous-firefox-browsing-data/
https://www.ghacks.net/2017/08/29/firefox-57-lists-third-party-accessibility-tools-that-may-spy-on-users/
https://www.ghacks.net/2017/08/30/firefox-webextensions-may-identify-you-on-the-internet/
Maybe is better to stop recommended Firefox.
Better Use Firefox 52esr not touched before 2018 ; by this problem.
Pale Moon
Firefox based browser. But for the moment respect users.
in section : 1. Open-source browsers of your site.
Off course use Chromium ; the Best.
@2356: No, settings panel is not purple for me, wih the same Chromium version!
And especially with your link.( Thank you ; I did not know that ).Like this , users do can do what it takes to protect themselves.
Best regards. And always thank you for your great site.
And how disable "bad" features directly in the about:config page. Step by Step.
About "bad" features, I use my own settings + https://github.com/ghacksuserjs/ghacks-user.js in Firefox.
Meant only selection color is different, really don't know is it combination of some hardware/software which resulted in this going to check in few builds.
chrome://flags/#enable-color-correct-rendering
My area was in the path of Hurricane Irma. Thankfully got power back Tuesday and cable ISP back Wednesday.
Power and cable were out, but those were expected. Both were restored quickly. :)
One of the large front palms picked up a slight lean, which might eventually have to be straightened. Not a big issue for now.
----------------
New ThinLTO build pushed.
Quick FYI. Like an earlier ThinLTO build, it crashes in Octane and JetStream benchmarking for JavaScript performance, but otherwise it seems stable in casual browsing. There have been some comments about Octane in recent bug reports. Might be related.
No sync • No WebRTC • No Widevine • 61.0.3163.91 (488528) • Friday, 15 Sep 2017 32 bit
Maybe if you have time, hope can compile v63....
it stopped working some time ago in LKCR
I can't find any option about DRM content in the settings.
I have disabled every plugin but the issue is still going.
Do you know how can I fix that ?
Some people are concerned about potential security implications using WebRTC, particularly about possibly exposing your actual IP address when using a proxy or VPN.
There is the WebRTC Network Limiter extension, but there has been discussion on whether it works properly anymore. I know Jerry has discontinued its recommendation here; check the extensions section.
Set "Use my proxy server (if present): This option forces Chrome to use the same network path for media as for normal web traffic, including use of a web proxy." in the extensions options, and ideally, it should (or perhaps previously once did?) force WebRTC to only see the same network interface as Chromium is set to use - even if it a proxy or VPN. Huge YMMV there, and if anyone has tested it recently, drop a line here. :)
Given the uncertainties and concerns, disabling WebRTC at build time has proven to be an acceptable alternative for many users here, at least when I previously sought feedback on the issue for my own builds.
I use the sync widevine webrtc build of chromium
@2380 & @2381: Thanks, and yeah, I have no particular intentions of enabling WebRTC as I do not have a use for it personally. ;)
I am a little more open on Widevine if there is a compelling reason or enough user demand, as I am not aware of any current privacy or security implications with it enabled. I mostly disable it to skip step or few when building.
Compiled under High Sierra GM [17A362a] & Xcode9 GM
Chromium 63.0.3219.0 (Official Build) (64-bit)
Revision 37f0b5bfd017a546822e698587cab533cce7d007-refs/heads/master@{#502524}
The 10.0.15063.468 SDK is expected to soon be a requirement as well.
How does that affect stable Win builds?
@RobRich: i just migrated to vs2017, i hope it resolve the issue
@2390: well, the stable is compile normally, but i've already installed vs2017 so the next stable will be depend on "Visual C++ 2017 Redistributable"
i've just compiled v63.0.3219.0 with vs2017 and upload it, don't know how it goes.. for me all functions work (but i can't test netflix because i don't have it)
same issue on a totaly different computer running Win7
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
355 of 1419720 ( 0.03%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
10768839 of 19978335 inline instances were from dead/cold paths
1419714 of 1419720 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
1081256973703 of 1081256973703 instructions (100.0%) were optimized using profile data, and the rest of the instructions were optimized without using profile data
^Translation? Ya'll typically get the same builds I use locally. :)
I think that builds requiring Visual C++ 2017 Redistributable to run need to have it mentioned in description. Also, currently it's not available among downloads on microsoft.com, but on https://www.visualstudio.com/downloads/?q=redist instead.
https://www.visualstudio.com/en-us/productinfo/vs2017-system-requirements-vs
https://www.ghacks.net/2017/09/19/first-chrome-extension-with-javascript-crypto-miner-detected/
https://www.ghacks.net/2017/09/19/steam-inventory-helper-monitors-your-browsing-activity/
To be technical, my builds might work with sync if setting up and supplying your own Google API keys as environment variables. YMMV, as it has been quite awhile since last dealing with sync.
amazing that you are continuing the VS2017 builds, I appreciate it!!
Thank you!
Octane: 33k score for PGO, crashed for ThinLTO
SunSpider: Both relatively similar. But ThinLTO has higher variance in its results (all around) compared to PGO
PGO: Total: 250.1ms +/- 0.8%
ThinLTO: Total: 249.7ms +/- 1.3%
May test it some more later when I get time. But yeah, more of a YMMV with ThinLTO, at least in synthetics.
I did note there were a few warnings while building V8 with my latest internal ThinLTO build generated locally today. Could be related.
----------------
The V8 subsystem has been highly optimized, thus I am not too surprised at both builds generating similar scores.
Perhaps try a more comprehensive benchmark suite to test multiple browser components and subsystems. Peacekeeper is technically rather out of date, but it still is a good place to start IMO. It is also included in the sites currently used for profling my PGO builds.
----------------
I have a local ThinLTO build without Octane 2.0 and JetStream crashing. :)
Portions of V8 have been pulled into the jumbo build option that basically groups files together for building with less steps. I disabled jumbo, and got a build without the crashers.
If I feel up to it, I will try to push a new public build in the next day or two.
Chromium for 64-bit Windows - All Codecs - Wednesday, 20 September 2017
Chromium 63.0.3221.0 (Official Build) (64-bit)
Revision e595973066aea66151989c1a7e189b5cabac837f-refs/heads/master@{#503103}
OS Windows
only for Windows 64
with codecs (h264, h265, flac, xvid, etc..)
no sync, no WebRTC and no Widevine support
official build (WPO thinLTO lld)
Compiled with clang
No Sync • No WebRTC • No Widevine
chrome.packed.2017.09.20.7z
https://github.com/macchrome/winchrome/releases/download/v63.0.3221.0-r503103-Win64/chrome.packed.2017.09.20.7z
SHA256 A78B905C5EA03FCAD06F6C4265C99138C08C1A9BC623F390B1399451963C384D
gn build arguments:
Build arguments go here.
See "gn args <out_dir> --list" for available build arguments.
#is_clang = true
#clang_use_chrome_plugins = false
is_official_build = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
chrome_pgo_phase = 0
current_cpu = "x64"
enable_google_now = false
enable_hotwording = false
enable_iterator_debugging = false
enable_nacl = true
ffmpeg_branding = "Chrome"
is_component_build = false
is_debug = false
is_win_fastlink = true
proprietary_codecs = true
symbol_level = 0
#syzygy_optimize = true
target_cpu = "x64"
visual_studio_version = "2017"
#exclude_unwind_tables = true
remove_webcore_debug_symbols = true
enable_remoting = false
enable_webrtc = false
#rtc_use_h264 = false
#rtc_use_lto = false
enable_hevc_demuxing = true
enable_ac3_eac3_audio_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
use_jumbo_build = true
use_lld = true
use_thin_lto = true
is_clang = true
clang_use_chrome_plugins = false
clang_base_path = "//third_party/llvm-build/Release+Asserts"
full_wpo_on_official = true
#is_cfi = true
cfi fails to link!
Don't ask for mini-installer: expand into respective destination.
The mini_installer also is being targeted for link-time optimization as "use_thin_lto" currently is configured, but the mini_installer does not support building with LTO.
You can skip "full_wpo_on_official" as it does nothing with how "use_thin_lto" is currently configured. It extends /GL coverage for VS builds.
The args for "is_win_fastlink" can be disabled. AFAIK, it does nothing for LLD.
Using "use_jumbo_build = true" currently breaks V8. It will produce a build, but V8 will crash in certain benchmarks.
You might need to set "allow_posix_link_time_opt = true" to ensure whole-program-vtables is set when invoking LTO. I am not sitting in front of the build code right now to verify, but I do know that is how the ThinLTO buildbot args are configured.
----------------
I do not use the new "use_thin_lto" and its associated build arguments in the current state.
Instead I modify the compiler build configuration file to place additional conditionals to enable ThinLTO and vtable coverage when setting official and whole wpo. That way ThinLTO has the same code coverage as Visual Studio /GL and does not interfere with code requiring the "no optimization" compiler setup, such as the mini_installer.
----------------
@John Widevine provides digital rights management. It is not needed for the various a/v formats to work, but it oftentimes is needed for commercial streaming services likes Netflix.
I appreciate your observations.
The gn settings provided actually build/produce a mini_installer.exe; which since I prefer to use Chromium in a portable(apps) format is personally not a requirement.
Basically, I was trying to replicate Nik's "wpo cfg all-codecs lkcr 64-bit windows" using clang. The abortive cfi link (a memset failure) was performed after the initial conventional build and took twice as long.
Quick comparison of my currently available public builds....
Intel Core i5-7300HQ, 16GB DDR4, nVidia GTX 1050 2GB
PGO = v63.0.3219.0-r502527-win64 (117GB to build)
ThinLTO = v63.0.3221.0-r503271-win64 (3.65 GB to build, including incremental cache)
Octane 2.0
pgo: 35137
thinlto: 38180
JetStream 1.1
pgo: 184.38s
thinlto: 189.69s
ARES-6 1.0.1
pgo: 25.23ms
thinlto: 24.88ms
SunSpider 1.0.2
pgo: 226.9ms
thinlto: 230.3ms
Kraken 1.1
pgo: 1057.7ms
thinlto: 1047.3ms
Dromaeo V8 JavaScript
pgo: 1698.58runs/s
thinlto: 1852.58runs/s
Basemark Web 3.0
pgo: 821.24
thinlto: 805.26
Peacekeeper
pgo: 5343
thinlto: 5494
----------------
@marmaduke No prob. I went down the ThinLTO path well before "use_thin_lto" recently appeared for Windows builds, so I have hit some of the build issues associated with implementing it.
Someone might have patched the mini_installer build script. It was failing when "use_thin_lto" initially was implemented due to a memset error building mini_installer, which occurs because mini_installer is not supposed to be exposed to LTO. IIRC, Chromium devs mentioned other pending patches regarding "use_thin_lto" usage. Could be rolling them out.
For now I am proceeding with my ThinLTO process, as it replicates VS coverage, thus hopefully less surprises while the devs work on the project's own implementation. Today I did get around to adding fast incremental link caching into my modifications like "use_thin_lto" does. I have yet to try it, but it should further speed building times if properly working.
Chromium for 64-bit Windows - All Codecs - Wednesday, 20 September 2017
No Sync • No WebRTC • No Widevine - ThinLTO (for real!)
Chromium 63.0.3221.0 (Official Build) (64-bit)
Revision e595973066aea66151989c1a7e189b5cabac837f-refs/heads/master@{#503103}
OS Windows
https://github.com/macchrome/winchrome/releases/download/v63.0.3221.0-r503103-Win64/chrome.packed.thinlto.2017.09.20.7z
SHA256 6C1C93CE05E8C14C4A522A9A28C1C5F5F6451442528F536CE38BC578000DFDC1
This build is actually ThinLTO: built without "use_jumbo_build = true" and with the addition of "allow_posix_link_time_opt = true". LLVM whole-program-vtables coverage is implemented as standard on the compiler (but not the linker - produces message saying this parameter is unrecognised). As expected, mini_installer.exe fails to build.
Benchmarks:
Octane 2.0
Standard: 27349
ThinLTO: 27763
Jetstream
Standard: 137.57 ± 1.6136
ThinLTO: 140.64 ± 3.5677
If there's a MacOS requirement, from now on, it would be nice to specify it somewhere. ;-) — and maybe put a link for the last compatible version for each MacOS (Mavericks, Yosemite, etc.)
Thanks anyway.
OSX (v63.0.3219.0-r502524) was an experimental build that's why I stipulated "Compiled under High Sierra GM AND Xcode9". I think that Xcode9 GM might be the culprit: since then Xcode9 "proper" has been released. I will continue to compile under 10.12.6 and Xcode8 until the official Chromium build requirements change. My knowledge and usage of OSX is limited to 10.11 and beyond.
v63.0.3219.0-r502524 functions "correctly" under 10.12.6 and 10.13. My preference is to use the latest tools available: OS, Xcode and Chromium. As such I will continue to provide the latest builds.
No sync • No WebRTC • No Widevine • 63.0.3221.0 (503329) • Thursday, 21 Sep 2017 32 bit !!!
- Sometimes Chromium will produce slightly off colors, and sometimes it won't. It's erratic.
- Started happening in v61.
- Color correct rendering does not help.
- In my case, I use an ICC profile in Windows.
chrome://flags/#force-color-profile
But if you need an offline installer:
1) Go to https://www.visualstudio.com/downloads/
2) Scroll down to the bottom page
3) Check "Other Tools and Frameworks"
4) Choose your 64-bit or 32-bit version of "Microsoft Visual C++ Redistributable for Visual Studio 2017"
@Aargi et al
Chromium for 64-bit macOS - All Codecs - Sunday, 17 September 2017
Compiled under High Sierra GM [17A362a] & Xcode9 GM - SDK 10.12
Chromium 63.0.3219.0 (Official Build) (64-bit)
https://github.com/macchrome/chromium/releases/download/v63.0.3219.0-r502524-macOS/Chromium.app.63.0.3219.0.nosync.sdk10.12.zip
SHA256 7DDDE4573F303B31257589E13158D80D34311313DA7FA3A60E8777D4C39EBF55
The previous version of this build was compiled under SDK 10.13
----------------
While on the topic, Clang as configured in the build templates can and often does generate warning information. Great information for devs looking to squish possible bugs or wanting to meet strict coding compliance, though potentially troublesome for building.
I disable warnings as errors when building. I find warnings tend to be noise more often than not. Actual serious errors like a failed link still will stop the build anyway.
For anyone building, I suggest adding to the build arguments if not already:
treat_warnings_as_errors = false
Chromium 63.0.3223.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 4eb4ec43a3380d17c5bd1c139918d567b5ef35f7-refs/heads/master@{#503834}
Compiler clang (+lld +thinlto)
chrome.zip | SHA1: b35f91979084824afe2c9fe46ab8dd39207b944b
https://drive.google.com/open?id=0B4saVuqumZNZUGRORDMtMnlJYWM
mini_installer.exe | SHA1: 5fa284604b395e3914b21f16738b4c3842047995
https://drive.google.com/open?id=0B4saVuqumZNZdU9ZVUJLdHBpOUk
Thought I copied my benchmark data before turning off that system, but apparently not. Anyway, IIRC, it showed performance gains in most (all?) benchmarks I tested compared to my current public ThinLTO build available at GitHub.
Chromium 63.0.3207 thinLTO WPO
Jetstream - 269.32 ± 3.8748
Speedometer - 196.3 ± 0.60
Chromium 63.0.3223 thinlto wpo (and your new compiler optimizations)
Jetstream - 277.75 ± 2.5391
Speedometer - 211.1 ± 0.47
Getting even faster on OC'd 6600k.
----------------
"Experimental" is the ThinLTO build with modifications to compiler optimization levels.
Intel Core i5-7300HQ, 16GB DDR4, nVidia GTX 1050 2GB
PGO = v63.0.3219.0-r502527-win64
ThinLTO = v63.0.3221.0-r503271-win64
Experimental = 63.0.3223.0-r503834-win
Octane 2.0 (higher is better)
pgo: 35137
thinlto: 38180
exp: 39590
JetStream 1.1 (higher is better)
pgo: 184.38
thinlto: 189.69
exp: 196.30
ARES-6 1.0.1 (lower is better)
pgo: 25.23ms
thinlto: 24.88ms
exp: 24.38ms
SunSpider 1.0.2 (lower is better)
pgo: 226.9ms
thinlto: 230.3ms
exp: 228.7ms
Kraken 1.1 (lower is better)
pgo: 1057.7ms
thinlto: 1047.3ms
exp: 1006.0ms
Dromaeo V8 JavaScript (higher is better)
pgo: 1698.58runs/s
thinlto: 1852.58runs/s
exp: 1906.16runs/s
Basemark Web 3.0 (higher is better)
pgo: 821.24
thinlto: 805.26
exp: 844.79
Peacekeeper (higher is better)
pgo: 5343
thinlto: 5494
exp: 5616
NIK: On NETFLIX I get "Error Code: M7121-1331-P7" while attempting to load any media on the site. Your previous builds (3 builds ago) used to work just fine. Did something change?
I refer people here all the time, thanks Jerry and the good folks that push out builds such as Nik & Rob.
I got curious with my system and did my own tests, here are the results to give back a little something.
Windows 10 x64, Intel Core i7-7700K Stock, 16GB DDR4, NVIDIA GTX 1070 8GB OC.
AppData\Local\Chromium folder deleted between builds/testing to maintain purity, no add-ons ofc.
nik wpo = Nik [wpo|cfg] 63.0.3219.0-win64
rob pgo = RobRich [pgo|vs2017|cfg] 63.0.3219.0-win64
rob multi = RobRich [wpo|thinLTO|clang|lld] 63.0.3221.0-win64
rob exp = RobRich Experimental [lld|thinlto] 63.0.3223.0-win64
Octane 2.0 (higher is better)
nik wpo: 50883
rob pgo: 50505
rob multi: 52418
rob exp: 54200
JetStream 1.1 (higher is better)
nik wpo: 262.38
rob pgo: 260.05
rob multi: 269.11
rob exp: 276.27
ARES-6 1.0.1 (lower is better)
nik wpo: 18.05ms
rob pgo: 18.52ms
rob multi: 18.08ms
rob exp: 18.39ms
SunSpider 1.0.2 (lower is better)
nik wpo: 165.2ms
rob pgo: 163.6ms
rob multi: 152.5ms
rob exp: 152.9ms
Kraken 1.1 (lower is better)
nik wpo: 745.2ms
rob pgo: 759.6ms
rob multi: 731.8ms
rob exp: 740.7ms
Dromaeo V8 JavaScript (higher is better)
nik wpo: 2326.18runs/s
rob pgo: 2294.32runs/s
rob multi: 2552.14runs/s
rob exp: 2544.28runs/s
Basemark Web 3.0 (higher is better)
nik wpo: 1102.35
rob pgo: 1255.66
rob multi: 1135.76
rob exp: 1160.08
Peacekeeper (higher is better)
nik wpo: 6716
rob pgo: 6857
rob multi: 7020
rob exp: 7141
YMMV, for now I'm going to keep using experimental since it seems like you're onto something good, keep it up Rob.
--------------------
For those curious about the benchmarks....
Most of the benchmarks are JavaScript oriented. While highly important, admittedly JS is just one aspect impacting the browsing experience.
Basemark Web and Peacekeeper are the more comprehensive browser benchmark suites on the list. They target rendering, DOM, WebGL, etc. Even if synthetic and discontinued, I still tend to lean towards Peacekeeper as a decent overall browser performance indicator.
17329fccf83134a098084e70a1213564d71cfa6f-refs/heads/master@{#504002}
*** EXPERIMENTAL Device must be Neon compatible (Experts only!)***
Build arguments go here.
See "gn args <out_dir> --list" for available build arguments.
target_os = "android"
target_cpu = "arm"
current_cpu = "arm"
arm_use_neon = true
is_debug = false
symbol_level = 0
is_component_build = true
is_clang = true
ffmpeg_branding = "Chrome"
proprietary_codecs = true
Chromium_Android.zip
https://github.com/macchrome/droidchrome/releases/download/v63.0.3224.0-504002-Android_Neon_32/Chromium_Android.zip
SHA256 55FE47EEC366A1F000E328E8D667F0189A6B55475FAE3C36C93243A9FCE2A019
Feedback appreciated.
----------------
I suspect the "experimental" compiler optimization setup is going to be difficult for me to top right now, though I have some ideas. Now as to when I might feel up to implementing and testing them....
Anyway, what I have done locally in recent days:
1.) I have upped the optimization level for the Native Client Integrated Runtime. It was quick modification, so whatever, though I doubt it is going to do much for most users. Maybe help a little with Flash and/or PDFium performance?
2.) I built the Polly polyhedral model optimizations for LLVM and tossed the corresponding LLVM arguments into Chromium's compiler build configuration. Polly can help with nested loop optimizations; assuming Chromium will even benefit from such optimizations. Suppose I will find out. :)
I just signal that : ScriptSafe
https://chrome.google.com/webstore/detail/scriptsafe/oiigbmnaadbkfbmpbfijlflahbdbdgdf
Prevent many canvas fingerprint.
Tested on : https://browserleaks.com/
More than Canvas Defender ( " I believe " )
mp3, aac and h264
"disable_ffmpeg_video_decoders = true" is enabled by default.
I do not want to offend you.
But the main interest of Builds By Nik Or RobRich ; is compile without WebRTC.
Nowhere else ; we finds this kind Of Chromium release.
Except for 32 bit release.
Only Nik Compile.
But for 64 bit ; what you say is achievable.I think.
It's just ; a remark.
Only Nik Or RobRich ; may decide to do it.
And "Sync • WebRTC • Widevine " 64 bit compiled by Nik; it's not suitable for your use ?
Regardless, thanks to all the contributors on this site for making Chromium accessible to all!
It could be a revision issue, so I will build a new revision and try again soon. Perhaps Friday or the weekend.
I do not think it is a compiler optimization issue, as I am still in what is considered the safe range for optimizations.
BTW, I dropped a quick search. It appears this WebGL+video issue has happened before with Chrome(ium), particularly with 360 videos at FB. Curious, are any other recent builds affected?
Thumbs up!
No sync • No WebRTC • No Widevine • 63.0.3228.0 (505388) • Friday, 29 Sep 2017 32 bit
I am sure it comes from the builds but I don't know why...
Had to run Firefox when it comes to NetFlix
Please check that the computer where you are compiling is not infected by adwares.
@Fred: for monthes, NetFlix no longer works if you use "private browsing". It looks like DRMs are now disabled in private browsing. Did you try without using "private browsing" ?
@2466: chrlauncher downloads, unzip and installs ZIP file itself. In this case, it is not infected by #malware but is a false positive of Avira antivirus.
You can check "chromium-sync.zip" yourself:
- https://www.virustotal.com/#/file/b2dc4d47b19eb60dca8151995293d2005bc7e2626931dc34cfe70b800a801aec
- https://virusscan.jotti.org/en-US/filescanjob/600bt4u3nu
Also, thanks for info about Incognito mode on Netflix (Search "Turn off private browsing or sandbox mode" in https://help.netflix.com/en/node/62)
----------------
New Clang build available. No benchmarks right now, but I have rolled the previous "experimental" build compiler optimizations into the release build, so I expect similar results.
Had to track down a LLVM issue while building. Some type of Clang memory leak or similar in my current LLVM trunk build. Did a rollback to the same LLVM revision Chromium is issuing with the browser revision I was building.
Chrome Cleanup Tool (Formerly Google Chrome Software Removal Tool) will scan and remove software that may cause problems with Google Chrome.
It's portable.
(I do not have yet found the author's repository)
However, there appears to be a slight to moderate performance regression in perhaps rasterization and/or 3D rendering with Peacekeeper and Basemark Web. It could be related to the older LLVM revision I used to successfully build the browser. YMMV on actually noticing it in real world usage.
I just noticed Chromium has hit basically the same LLVM issue with two Linux buildbots, so hopefully it will be resolved soon.
Looks like there might have been some mitigation on the performance regression(s) previously noted, though YMMV as usual.
I have been poking at automatic vectorization, though apparently it is not an option right now when using ThinLTO. I can do without LTO for testing, but AFAIK, getting LTO with autovec currently means a rather time-consuming FullLTO build.
In former versions it was ok.
In Firefox it still works ok.
Facebook's idiosyncrasies do not particularly concern me.
Others, like me, just do not have an immediate use for it.
I have been poking at building with automatic vectorization and various Polly optimizations. IIRC, I have Basemark Web within like 100 points of a ThinLTO build, and that was using a build without LTO.
Confirmed: the mini_installer now builds with the new thinlto build argument.
"allow_posix_link_time_opt" is an invalid gn parameter.
-----------------
Chromium v63.0.3237.0-r507359-Win64
Chromium for 64-bit Windows - All Codecs - Monday, 09 October 2017
Chromium 63.0.3237.0 (Official Build) (64-bit)
Revision 3976de7c0d648ee59b29013a0f6431d3d2dbe879-refs/heads/master@{#507359}
OS Windows
No Sync • No WebRTC • No Widevine - ThinLTO Build (Compiled with clang & lld)
https://github.com/macchrome/winchrome/releases/download/v63.0.3237.0-r507359-Win64/chrome.packed.2017.10.09.7z
SHA256 BB56D2419BFF6675BFEE2A202B757DAD3EC50C18A13D04D3956E70D17780E692
The thinlto build argument sets whole-program-vtables, so the posix link time argument is no longer needed.
Also IIRC from a recent internal build here, jumbo now should be working properly with ThinLTO.
----------------
I tracked down at least the broad cause of the recently noted performance regression in certain graphics benchmarks. It appears to be involved with the ongoing transition of components to Mojo IPC. Kind of interesting since Mojo IPC generally is expected to be faster than Chrome IPC.
Disabling chrome://flags/#enable-mojo-loading resulted in returning my current public ThinLTO build back to my earlier performance numbers in Basemark Web.
Suppose it even could be LLVM related, as I have not yet checked a VS2017 build for comparison.
@2489 I'm using a ramdisk for the whole browser (cache and program files, with chrlauncher). Going strong here.
btw is there any advantage in moving whole browser into ramdisk and not only cache?
I hope you are doing fine? Can you please do a new VS2017 build sometime soon? The one from September is getting a bit outdated.
Thanks so much,
Lorenz
To be exact, complaints about missing source files that are not actually missing. Probably related to building with WebRTC disabled, which can quickly become a significant annoyance. I already have a previous revision file checkout and commit revert in the build process due to it. Now perhaps something else to add.
My build box has a PGO build cooking. Hopefully should be available Monday.
Followup on my 10/14 post about "missing files" when building with webrtc disabled. See the diff for commit 9db4b1582e7bac38d95f0b22e6904d4fa0cf07eb that moves around three webrtc dependencies. Move, add, revert, etc. them back to resolve the issue.
thanks for the possibly upcoming VS2017 build, appreciate that!
Meanwhile I am using your latest Clang build from 15. October, but can´t view
https://www.waze.com/livemap
with it anymore. Any ideas why? Works fine in Firefox.
Cheers,
Lorenz
About the linked site, it appears to be a JavaScript issue. Chromium's JS console says:
"index-3bb97006c07e50f84903fb9088ea06e538e416ec36f419237581cbbaceb98b20.js:6 Uncaught RangeError: Maximum call stack size exceeded"
I am suspecting it is reversion related instead of optimization related, though I will check it with my next build revision to verify.
There is current PiP workbeing done as an web API. There is a recent draft document and a code base, plus a related Chromium flag at chrome://flags/#enable-picture-in-picture, but otherwise, it requires web pages edits to use the API. That is assuming the API still is not in flux for whatever platform, and the video playback methods supports the API.
------------
Finally, an updated PGO build is available. @Lorenz, it appears to be working with Waze. :)
I also rolled in a couple of compiler optimization changes. There was a mild increase in output file sizes. I have not tested for performance differences though, so YMMV for now
http://peacekeeper.futuremark.com
64.0.3242.0 Clang: 5060
64.0.3243.0 VS2017: 5141
Thank you:)
@Anon2504 Could be revision related, or it perhaps could be GPU related as well. I would take a look, but I am not experiencing it here. You might try updating your GPU drivers if possible and/or try disabling GPU video decoding to test:
chrome://flags/#disable-accelerated-video-decode
@Jerry Thanks for the updates. Ya' got email, too. :)
@Anonymous: I had exactly that issue with Rob´s latest Clang build too, with the PGO (VS2017) it´s fine again.
All working good so far :) Thanks nik Much appreciated
Thanks Jerry for your selfless effort offering and maintaining this site
Be well
If Possible for you.Can we have update to 63.0.3239.9?
No sync • No WebRTC • No Widevine 32bit&64bit
Please
https://github.com/macchrome/winchrome/releases
Currently I have been experimenting locally with loop optimization using polyhedral modeling, tiling, etc to potentially improve performance. I might actually issue an experimental build someday, though at the rate I have been going plus needing FullTO for autovec+LTO right now with LLVM.... ya'll might be waiting awhile. o.0
I use Robs builds.
Wait for Nik's next dev build in a few days, can compare to see if its revision thing or Robs build.
About media extensions, lots of underlying components are being transitioned to Mojo IPC. IIRC, there also is a new audio mixer or renderer somewhere in the dev pipeline, but I am thinkting it still was behind a flag at last look. I am on an iPad right now, so I can not verify.
Last stable/fully working build for me is r506675.
Thanks <3
(Sync • No WebRTC • No Widevine • 64.0.3248.0 (510708))
N.B. : on every site I've tried so far, including Youtube and... Facebook. ;-)
https://tools.woolyss.com/html5-audio-video-tester/
Here is another one that works by checking what the browser reports when queried.
https://html5test.com
@Anon2522 I will try to take a further look, but I am not remembering seeing any recent issues here locally with YT. Have you done the usual troubleshooting processes, like clearing any custom about:flag settings?
Next macOS build, I will document the steps. My build system is pretty stable: I just patch and build (and wait for errors).
@Aargl
Good to know and I appreciate the feedback. As long as my build works with uMatrix, HTTPS Everywhere, Switchysharp, CanvasFingerprintBlock, uBlock Origin (+Extra), ScriptSafe, uBO-Scope and Don't track me Google. I'm happy.
@Meconium
My latest build on github is quite "old". I've compiled 64.0.3248.0 and am having problems with youtube: mouse seeking does not work; but cursor key seeking (with the left or right arrow key) does.
@2533
I've never heard of RES - redditenhancementsuite.
Development code by its very nature is intrinsically inconsistent and incoherent; for example, the changes to the webrtc dependencies!
"2017-10-26 16:10:44.133 Chromium[497:4907] *** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug.
[497:59395:1026/161044.157188:FATAL:connection.cc(1517)] SQL compile error no such column: instant_url"
any ideas?
On Firefox i get 0.
Skipped Frames is usually indicative of weak hardware or inefficient browser, so by these results it seems that Chrome/Chromium is having poor performance on Twitch.
Anyone else experiencing this? If you don't know how to check the stats on Twitch, click on the gear icon - bottom right corner > Advanced > Show Video Stats
Folks, I've encountered a problem and I'm not sure if it's my particular installation has gone bad or if it's a bug.
When I right-click anywhere within a page in Chromium, as soon as my mouse cursor comes into contact with the right-click-menu, the menu blacks out and is covered by an image that appears to have part of the address of the site in it. Is this a bug, or is it possibly a problem with my desktop's rendering mode? I'm running within Mate desktop, and installed the Nvidia Legacy drivers last night prior to opening Chromium --so I'm not sure if the problem precedes the driver installation or if it was picked up during that time.
Chromium for 64-bit macOS - All Codecs - Friday, 27 October 2017
Chromium 62.0.3202.77 (Official Build) (64-bit)
- Sync, WebRTC, Widevine
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- stable build
Chromium.app.62.0.3202.77.zip
https://github.com/macchrome/macstable/releases/download/v62.0.3202.77-macOS/Chromium.app.62.0.3202.77.zip
SHA256 56A4380AA57AE9D6CBCF30F9F3708DA39D609D0C91ED6C4B994362EEDB25C7F1
Given it appears my earlier and marmduke's 507359 build are okay, versus my current and apparently nic's current builds, it appears whatever some of ya' are encountering with YT, extensions, etc. is a revision-related issue. I am not experiencing it, so trying to track down a specific commit could be be difficult.
Curious, anyone affected tried disabling Mojo IPC?
chrome://flags/#enable-mojo-loading
@Anon2527 Sync is actually present. There are just no #google-api-keys present in the 'No Sync' builds. Jerry has instructions here on obtaining ad using your own keys if desired.
Chromium does not really have a stable build. I went to https://chromium.googlesource.com/chromium/src.git and chose the latest tag on the current Chrome release branch.
My preference when doing a stable build is to do a generic build: Sync, WebRTC, Widevine. WebRTC can be disabled by using "uBlock Origin" and I suppose sync could be rendered useless by:
launchctl setenv GOOGLE_API_KEY "no"
launchctl setenv GOOGLE_DEFAULT_CLIENT_ID "no"
launchctl setenv GOOGLE_DEFAULT_CLIENT_SECRET "no"
and flags - --disable-sync --disable-sync-backup --disable-sync-rollback --disable-sync-app-list --disable-sync-types.
SDK 10.12 is required for Chromium - particularly if you want to maintain compatibility with OSX 10.9.5
Xcode 9.0 uses SDK 10.13; Xcode 8.3.3 uses SDK 10.12. When using Xcode 9.0, SDK 10.12 has to be specified.
I will write a tutorial on https://github.com/macchrome/macstable
I'm staying with v63.0.3237.0 (507359) winx64 by marmaduke as that's the last working build for me.
Wild guess, could it be the V8 engine?
JavaScript: V8 6.3.276 from marmaduke's vs V8 6.4.150.1 from latest Rob's build?
Chrome Canary Same thing same issues and: JavaScript V8 6.4.143
64.0.3251.0 (Official Build) canary (64-bit) (cohort: Clang-64) (512036)
Been using the Star Wars trailer on youtube to test all builds these last few weeks.
This is what it looks like after seeking.
https://imgur.com/Xx3aydR
Compare with original https://www.youtube.com/watch?v=Q0CbN8sfihY
Can see we miss the ground cracking due to stuttering.
Is the file safe?
False positive.
I use all buid by NIK.
Never problem
What is the difference between the two builds of chromium u have? Chromium_PGO and Chromium_Clang.
What should i use??
Chromium 62.0.3202.77 (Official Build) (64-bit)
Revision 1c03900dc3924e86a2bcdcc984c6da6bdbff118f
- No Sync, No WebRTC, No Widevine
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- stable (branch) build
Chromium.app.62.0.3202.77.nosyc.zip
684279DDA6935C0381C34867EDCBBE04200B679159511FEB374E647E51C078E9
SHA256 56A4380AA57AE9D6CBCF30F9F3708DA39D609D0C91ED6C4B994362EEDB25C7F1
Basic tutorial: https://github.com/macchrome/macstable/releases
Only if you agree and have time
Can you update 32 64 bit to 64.0.3251.0 ; No sync • No WebRTC • No Widevine
Google Chrome 64.0.3251.0 Dev
not sure if there was. i dont use (google) sync, but every fresh windows install (or copy&paste between systems) i had to reinstall all extensions but the settings remain. it would be comfortable to have those preserved (like opera/portable - no fan of opera and similar).
Same problem here.
Since version 63.0.3207.0 all new version break some extensions. (This extension may have been corrupted)
Sometime many, sometime few.
No exception !
Nik dev-sync or nosync, RobRich pgo or clang, Marmaduke win-version and more interesting : even the dev-official from Chromium Authors !
So it seem to be a Chromium problem. The problem occurs sometime for normies’users which unistall and reinstall the concerned extensions.
But the good new is that the last RobRich version 64.0.3252.0 (512215 / dev-clang-nosync) break only one extension on 24 for me. (options, preferences, favorites, everything other is fine)
So I think I will use this last 64.0.3252.0 RobRich version, update, repair and active again all extensions and see if the problem occurs again with future update before investigate.
This message doesn’t really add interesting informations for Nik, RobRich, Marmaduke or Jerry. It's just to try to move the Chromium-schmilblick forward and add a +1 on Anonymous (2547) problem.
Thanks for all your works Nik, RobRich, Marmaduke, Jerry and others contributors.
@Student: Clang is a compiler like Microsoft Visual C++ compiler while PGO is a compiler optimization technique that uses profiling to improve program runtime performance. Both compilers implement PGO.
@2550: I contacted AluisioASG by mail and wait for his answer. His own repository is not updated :/
Anyway, if using one of my builds, I typically recommend the ThinLTO build due to update frequency and general overall performance.
I do not update PGO as often, as it can take hours to build, profile, and relink. I keep it available as an alternative for some where PGO benchmarks higher for whatever reason(s), plus as a comparison for testing ThinLTO builds against.
@Jerry As always, thanks for the site and support! :)
Thank you for all you do.
If you can and have time.
Can you compile modified-clang+lld-wpo-thinLTOlkcr64-bit-windows-Installer 32bit No sync • No WebRTC • No Widevine
Same buidl a Nik.
Just one time for compare.
I don't have 64 bit system.
If not.No Problem
Thank you anyway.
somewhere in the past it was decided to use the super_mac like chrome - obviously vivaldi is using it too, but not opera.
when using chromium as a portable ist loses any extension until i reinstall it - settings were preserved. opera ignores the super_mac and so it is fully portable included extension installations.
>> ince version 63.0.3207.0 all new version break some extensions.
from time to time i experience this myself - but i dont worry about - the next dev release fixed it somehow (i use a final stage with its own profile and a dev stage with its own profile). last break was 63.0.3236.0 - i did not test further because currently i investigate more into firefox 57.
finally again - is it possible to compile a fully functional chromium without using the super_mac again?
(i know very well what super_mac is for, eg: https://www.adlice.com/google-chrome-secure-preferences/)
this was also noted on portableapps.com by John Haller.
I have a new CPU now (AMD Ryzen Threadripper 1950X 16 cores) and have just tested if VS2017 builds are still faster than Clang. Interestingly, Clang is ahead now in terms of performance with http://peacekeeper.futuremark.com/ :
64.0.3243.0 VS2017 5546
64.0.3254.0 Clang 5605
Very nice, so it really was CPU-specific that the VS2017 builds were faster with my previous i7 3770K.
Cheers,
Lorenz
@Anon2559 IIRC, I previously had issues when attempting a 32-bit ThinLTO build. Suppose it is something I could try again.
@Lorenz Thanks for verifying. Nice processor, too. :)
Thank you very much , but if is too complicate.
It's not a necessary to you complicate the life.
Chrome dev is 64.0.3253.3 now.
May be can you .... :)
Thank You
Cheers and thanks for the good work!
I spent tons of hours trying to find this particular version and I didn't find it anywhere. I need it because I want to try something and also because I want to get rid of this stupid material design. 53 and 54 are not a solution because they have some certificate errors and version 55 doesn't have that flag anymore to disable the material design.
I know there is a a version with 120 at the end, but I need the one with 116.
https://www.chromium.org/developers/how-tos/get-the-code/working-with-release-branches
--------------------
I will be pushing an updated ThinLTO build shortly. As a test I have rolled into some additional LLVM features: the new pass manager, NewGVN, and partial inlining. These could be changed or removed depending upon various factors; but anyway, they should be okay for standard browser usage.
--------------------
Below is a ThinLTO build with the same added features as above, plus AVX2 compiler optimizations. Probably no real-world performance difference. I was more or less testing the build environment on my notebook, so this could be an one-time thing. Use CPU-Z (cpuid.com) to verify AVX2 support if needed.
Chromium 64.0.3257.0 (Official Build) (64-bit) | No Sync | No WebRTC | No Widevine
Revision a2d7bb85bbd16caa7bb1a063d85ab6b1e1d74ebd-refs/heads/master@{#513625}
Compiler clang (+lld +thinlto +compiler_optimizations +newgvn +newpm +avx2)
mini_installer.exe | sha1: 3ba172fa7242aa2d22d78b721867dad7cb023e91
https://drive.google.com/open?id=0B4saVuqumZNZWUFnQlJGdnV2N2M
chrome.zip | sha1: 0a2fcbd48c6ba4dd8f29effc080234c8b922a8b3
https://drive.google.com/open?id=0B4saVuqumZNZZjRBZ2hDT1dLejg
Direct link: https://chromium.woolyss.com/f/chromium_win64_52.0.2743.116_r394939_sync.exe
Thank you Anon and Rob. I edited your comment, Rob! ;)
Thank you very much, I've been searching it for weeks but no luck. Thanks for uploading the file for me! :)
Have a good day!
Thanks Rob. Great job.
Just wondering @anon2571, are you windows 10 or 7?
Chromium 64.0.3258.0 (Official Build) (64-bit) | No Sync | No WebRTC | No Widevine
Revision 8d835fcdbf37e0fe0579cb7ff6a5da2c5250a3d4-refs/heads/master@{#513767}
Compiler clang (+lld +fulllto +compiler_optimizations +newgn +polly)
chrome.zip | sha1: 5de35619849a4dee7654ae8845478f270722b016
https://drive.google.com/open?id=0B4saVuqumZNZaDZwelFSRjkzNUE
mini_installer.exe | sha1: 50d2e953ee941053436a0f143b2a915e87141630
https://drive.google.com/open?id=0B4saVuqumZNZcVRfSHprdWtKSGc
It is still a work in progress that I did not plan to release yet, but anyway, it is a Polly+FullLTO build with NewGVN and partial inlining enabled. As an internal test build not originally intended for release it is somewhat generic in terms of Polly optimizations.
Measuring improvements with the applied pollyhedral optimizations and similar could be difficult, as several components affected by Polly are not typically benchmarked: A/V codecs, media filters, SSL library, pdfium, etc.
Benchmarking also could be a "mixed bag" of results even depending upon the specific processor due to various fine tuning aspects, especially with tuning tiling values for processor cache configurations. For example, SunSpider is decently faster on one of my systems and slightly slower on another system compared to a recent ThinLTO build. YMMV, as usual.
Also, are occasional connections to http://redirector.gvt1.com/edgedl/release2/chrome_component/ *.crx3 or alike addresses normal? Most google results mention malware, but it's Google's domain and my pc seems clean. I use only uBlock Origin, Privacy Badger and HTTPS Everywhere.
speedometer quite a bit over the old thinlto wpo builds. From 211 to 220 on my OC'd 6600k.
Someone should try the AVX2 and fulllto polly build on 3d and graphical benchmarks.
@Anon 2575 I don't have those problems on my AMD gpu. It might be driver related. I had to reset my about:flags to get these builds to start though.
I will get toss another build at the build box with an updated Polly configuration, plus check YT this time around. ;)
@Anon2577: about:flags are always reset for me. Totally clean profiles each time. But I agree, could very well be an issue with GPU drivers, since you have no problems with an AMD one.
And I still get freezes in YT after seeking. (513698)
Intel 15.47.02.4815 works here. I currently do not have an AMD GPU to test.
----------------
Updated build and optimization config. For example, I took out cache tiling for now as there are too many different processors out there. Also addressed some possible threading and compiler optimization issues.
Chromium 64.0.3259.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 6b2875367b6e16b3a781293e1f170de161b78ad7-refs/heads/master@{#514032}
Compiler clang (+lld +fulllto +compiler_optimizations +newgn +polly)
mini_installer.exe | sha1: 818b08bedba98d7e83cb76b3b902596a9281568d
https://drive.google.com/open?id=0B4saVuqumZNZVjBIalQwVkRKcDA
As for the typical benchmarks; quick runs of Basemark Web, Peacekeeper, and SunSpider were close to ThinLTO on my Kaby Lake notebook.
Tried your latest build 514032 and it was working fine (youtube worked) with my intel gpu (driver 20.19.15.4531) and then I tried it to run with my nVidia gpu (388.13) and youtube gave me Aw snap. So I switched back to Intel gpu and yt is Aw snaping here too (before switching to nvidia gpu it was working). After clean instalation I cant get it to work, so im going back to previous thinlto build.
Interestingly enough, the both Polly builds now work here with 388.13 for YT with the latest Intel and nVidia drivers.
To clarify my earlier post, Intel driver package 15.47.02.4815 includes the 20.20.16.4749 graphics driver.
Youtube « Aw! SNAP! » with your :
Chromium 64.0.3259.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 6b2875367b6e16b3a781293e1f170de161b78ad7-refs/heads/master@{#514032}
( Note that your link for « chrome.zip » 404’ed )
On :
Windows 8.1 x64
Intel Core i7 4710HQ @ 2.50GHz - DDR3
Intel HD Graphics 4600 (10.18.14.4578) + 2Go NVIDIA GeForce GTX 850M (385.28 (22.21.13.8528))
Will try to update integrated and NVidia graphics cards drivers first…
Youtube « Aw! SNAP! » even with NVIDIA updated to 388.13 (23.21.13.8813) on the configuration above…
I will retry with your 64.0.3258.0 (513698) where YouTube is OK but with lag…
Thank yoo all folk by the way.
This is definitely weird, our results are extremely varied.
May I ask what CPU you're using Rob?
Build box is 2x Opteron 6272, 64GB, GT 730. Personal system is Core i5-7300HQ, 16GB, HD630 + GTX 1050. I have others, but those are my primary systems.
On a more stable front, my build box is working on a fresh ThinLTO build right now.
FYI for anyone using the "use_thin_lto = true" arg to build on Windows. The actual LTO optimizations offered by ThinLTO have been disabled in the stock build config, so unless I am missing something it is basically being used as a multi-threaded linker for now.
I suspect the concern is due to increased file sizes. Naturally I continue to use the LTO optimizations in my ThinLTO builds since I do not care much about file sizes.
As to other builds, I might have a fresh PGO build in the near future for comparison testing.
Setting up brand new profiles doesn't solve the issue, suggesting something is broken in the recent builds, OR there has been a change in the code that the extension makers will have to catch up on. Unfortunate, as for now I have to remain on build 64.0.3242.0.
Thanks for everyone's efforts to bring us these builds.
Thank You for No sync • No WebRTC • No Widevine • 64.0.3259.0 (514062) • Sunday, 5 Nov 2017 .
:)
As always my thanks to Rob, Nik, Jerry etc for their time and work, I wouldn't be using Chromium if not for them.
= Rob: No sync/WebRTC/Widevine • 64.0.3260.0 64-bit (514063) [modified/clang+lld/wpo/thinLTO/lkcr]
Basemark Web (higher is better): 1114.6
Peacekeeper (higher is better): 6967 Points
JetStream (higher is better): 261.87
Octane (higher is better): 50836
Kraken (lower is better): 767.3ms
Dromaeo V8 (higher is better): 2447.69runs/s
SunSpider (lower is better): 161.1ms
Speedometer (higher is better): 221.7
ARES-6 (lower is better): 18.21 ±0.61ms
MotionMark (higher is better): 784.23 ±2.24%
= Nik: No sync/WebRTC/Widevine • 64.0.3259.0 64-bit (514062) [wpo/cfg/lkcr]
Basemark Web (higher is better): 1091.73
Peacekeeper (higher is better): 6721 Points
JetStream (higher is better): 258.94
Octane (higher is better): 49570
Kraken (lower is better): 788.1ms
Dromaeo V8 (higher is better): 2450.63runs/s
SunSpider (lower is better): 169.7ms
Speedometer (higher is better): 211.8
ARES-6 (lower is better): 18.34 ±0.80ms
MotionMark (higher is better): 691.37 ±16.28%
= Firefox Quantum: Developer Edition • 57.0b14 64-bit
Basemark Web (higher is better): 753.4
Peacekeeper (higher is better): 8499 Points
JetStream (higher is better): 260.33
Octane (higher is better): 45553
Kraken (lower is better): 667.1ms
Dromaeo V8 (higher is better): 2361.79runs/s
SunSpider (lower is better): 150.2ms
Speedometer (higher is better): 129.0
ARES-6 (lower is better): 49.21 ±1.46ms
MotionMark (higher is better): 377.01 ±15.68%
- Windows 10 x64 (FCU), Intel Core i7-7700K Stock, 16GB 3000MHz DDR4, NVIDIA GTX 1070 8GB OC (388.13)
- All stock/default & clean profiles (no add-ons) between them & testing as usual to main purity.
Further Testing:
- As for any issues with extensions: I personally use 18 extensions.
All are working fine for me, no corrupted/broken showing in chrome://extensions/, no settings being reset etc.
- As for any issues with Youtube: HTML5, I don't use Flash.
Tested 10 different Youtube videos in both builds above, no Aww! Snap errors etc, no issues at all.
If anything changes I'll be sure to leave feedback here. Feel free to ask me anything if needed, Thanks.
I found the reason for the broken extensions in recent builds. It's this commit from the code.
https://chromium.googlesource.com/chromium/src.git/+/30168b99604c48a32828f26b5acb2674beea1a5d
It changes how extensions injected stylesheets are treated. If the builds are made without this commit, the issue is resolved. Unsure whether this commit will remain or it's just something they are testing out.
@Anon2593 Good find. :) I just noticed there is a related discussion on the commit in an older bug report, too.
The downside is the number of files touched since the commit, so it is no longer a simple single reversion before building.
The upside is it appears there could be a pending patch related to the issue.
https://chromium-review.googlesource.com/c/chromium/src/+/754247
----------------
My build box is back online after OS issues. Fun stuff. Anyway, I hopefully should have some new builds within the next day or two. :)
I've not encountered that particular problem. These are the gn parameters that I use: (args.gn): https://github.com/macchrome/macstable/releases (ignore use_thin_lto = true).
I also built the clang compiler locally: `tools/clang/scripts/update.sh --force-local-build` trying to get thinLTO to compile (to no avail).
I've read the error reports that you've referenced and the problem appears to have been solved. I'll investigate the problem.
That said, I build LLVM externally and use "clang_base_path=" in the Chromium build arguments. That way I can integrate additional features intro the LLVM build, such as Polly support.
https://llvm.org/docs/GettingStarted.html
I build with Visual Studio on Windows, but I assume you could build with Xcode on Mac. Grab the code via SVN, pass the desired generator to cmake, and start the build.
Also, I saw that it has been labeled fix, but I was trying to build the latest tag (62.0.3202.93) for stable when I got the error. Do I need to wait for a new stable tag before the fix will show?
You would need to build at the fix's commit or later, which typically is going to mean master or LKCR.
The really is no stable release with Chromium, so you correlate with Chrome releases. If the next stable lands at a commit range before the breakage, then there is no need for the fix. If it lands at a commit range after the fix, then the fix is included. :)
The Chromium trunk currently is v64. Chrome is apparently v62, so it could be awhile.
Try to build 62.0.3202.89 which correlates with the current Chrome stable.
use_thin_lto is set to false by default, and bear in mind that the args.gn that I use is configured to build all codecs: use a minimal set of arguments and proceed from there.
@RobRich
Thanks for the advice. I've be trying to utilise thinlto with the standard clang checkout!
Otherwise, I doubt you would have any big issues going the separate route if LLVM proves as straightfoward to build with Xcode or similar as it is with Visual Studio.
----------------
Updated PGO build for the people.... err, anyone?.... still using it. Compiler optimizations included. PGO stats below:
0 of 0 ( 0.0%) original invalid call sites were matched.
0 new call sites were added.
291 of 1485948 ( 0.02%) profiled functions will be compiled for speed, and the rest of the functions will be compiled for size
11169164 of 20989730 inline instances were from dead/cold paths
1485936 of 1485948 functions (100.0%) were optimized using profile data, and the rest of the functions were optimized without using profile data
243356099931 of 243356099931 instructions (100.0%) were optimized using profile data, and the rest of the instructions were optimized without using profile data
From what I've read the ToT build of LLVM used by Chromium (officially) only supports ThinLTO on Windows and Linux. I'll try an Xcode build of LLVM.
Presently, when I attempt a macOS thinLTO build it fails with "foo.o is not an object file (not allowed in a library)" errors, which suggests that the thinlto dynamic library is missing and/or a misconfigured build.
@marmaduke Sounds like you are on the right track. :)
I took a quick look at the compiler config, and it appears the proper cflags and ldflags will be passed by Ninja. Just need a LLVM build with ThinLTO support on Mac.
If ThinLTO still breaks, then perhaps try FullTO? FullLTO is monolithic and typically (much) slower to link, but it is older and better supported on some platforms. It would be a quick build file edit to change between the two LTO methods. I can note the specific lines to edit if interested.
No sync • No WebRTC • No Widevine • 64.0.3263.0 (515088) • Thursday, 9 Nov 2017 (both Clang and VS2017): have all icons and graphics missing for me (e.g. The "X" for closing tabs, the addon-logos at the right top, even the "..." for the settings is gone). Since it happens with both compilers, it seems to be related to a general issue within that build. Turning of hardware acceleration fixes the problem - as well does going back to your previous Clang / VS2017 builds.
Thank you,
Lorenz
They are working here. Curious, could you try to a portable version to isolate the build from your existing profile, settings, etc.?
Follow the build instructions at https://github.com/macchrome/macstable/releases/tag/v62.0.3202.77-macOS
Log Messages
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[3112:5188:1110/161233.547:WARNING:angle_platform_impl.cc(51)] : compileToBinary(228): C:\fakepath(65,11-43): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(87,11-43): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
Hmm uh oh =(
----------------
@Lorenz + Anon2613 Updated ThinLTO build available. It is working here on two Win10 systems with the FC update. Hopefully it should be resolved for ya'll. :)
I will try to get a new PGO build out in the next day or two. Not a high priority, though.. As per my usual complaint with PGO, it takes an annoying long time to build.
I've changed the instructions (re-read them); they are generic: checkout the stable revision that you require. The args.gn and the patches are what I used to build - all codecs, no sync, no webrtc, no widevine. Make sure that you are using Xcode 8.3.3 with the respective command line tools; or if you are using High Sierra and Xcode 9.x and the respective/latest command line tools (and want to maintain compatibility with OSX 10.9.5) that you download and stipulate sdk 10.12 in the args.gn.
In fact you could establish a datum: checkout 62.0.3202.77 and see if that builds, and then work from there.
Yes, run the patch from the source directory.
My build environment is HS 10.13.1 (VM under ESXI 6.5u1 on a HP DL380 G6 2x Xeon X5670 72Gb Ram - 16Gb devoted to HS), Xcode 9.1, and SDK 10.12 (and "macports" if that is relevant).
Follow the instructions: use the amended args.gn
ninja: build stopped: subcommand failed." All I am trying to do is to help put out some stable builds so no one else has to build them, but I have yet to get a single successful build (after 14 tries so far). Beyond frustrating how hard this is for a non-developer.
Don't give up; but take a break! The Chrome/Chromium build process is poorly documented. I think it's best that you try to build LKGR (or master), and then try to do a stable build. Over the weekend I will (attempt) to do a stable build. One of the reasons why I refuse to do a regular stable build is because I believe that more people should be willing to build Chromium.
I was basically influenced by Nik's builds, and had to learn from scratch; it was a frustrating process.
Assuming "enable_webrtc = false", I don't know what the cause of the error is, unless you've accidentally included one of the commented out parameters in args.gn - eg. #enable_nacl = true
Curious, are ya'll with missing UI features running AMD video cards? Reason I ask is the builds are working on my systems with Intel and nVidia GPUs. No AMD GPUs here to test right now, though.
@Anon2624 The "Chromium Authors" project development build is about as generic as ya' are going to get. Plus it is often few commits ahead of us third-party builders, thus why I was curious if it perhaps might be working for ya'll having issues.
I am remiss to recommend plugins as "solutions" to browser issues, but try the below plugin as workaround to test. It disables VP9 videos at YT and forces most videos back to H.264/AVC1. Max res/rate available will be 1080/60 instead of 4K assuming that is a concern, but YT content probably will be hardware decoded and work correctly in the meantime.
https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal
BTW, if not already having hardware decoding support, those with AMD and perhaps other GPUs can add the following command line switch to try force enabling VP9 hardware support:
--enable-accelerated-vpx-decode=3
----------------
Yet another public ThinLTO build just pushed. Shaved a few milliseconds off SunSpider on my Core i5-7300HQ notebook. YMMV as usual.
Chromium 64.0.3265.0 (Official Build) (Windows 64-bit) - No Sync | No WebRTC | No Widevine
Revision f6ccfd4e25292e96f6fc735b86a00e65bf646bba-refs/heads/master@{#515704}
Compiler clang (+lld_linker +thinlto +npm +newgvn + partial_inlining +compiler_optimizations)
As far as I know, hardware VPx decode is only supported by Pascal/ Radeon 4xx+(not sure about Radeon cards, I don't have one), on Win10 machines. Anything lower than Win10 just won't work.
Btw, I'm running Win7 x64, Pascal, with C++ Redistributable for Visual Studio 2017 x86+64 installed.
Thanks for the info. I do not follow video format support closely these days. If it plays.... ;)
Chromium with my mobile GTX 1050 on Win10. As per chrome://media-internals details:
https://upload.wikimedia.org/wikipedia/commons/transcoded/f/f1/Sintel_movie_4K.webm/Sintel_movie_4K.webm.720p.webm
video_codec_name vp8
video_decoder FFmpegVideoDecoder
As expected due to the FFmpegVideoDecoder software decoder, VP8 generates "HW video decode not available for profile vp8" in the GPU log.
https://www.youtube.com/watch?v=1RTlB8Hmcw0
video_codec_name vp9
video_decoder GpuVideoDecoder
GpuVideoDecoder for VP9, which along with no GPU log error should mean hardware decoding is supported.
VP8 is an older, less complex format. VP9 is hardware decoded on my primary systems. Long story short, thus why I am not experiencing the issue here.
Nik goes a few steps further to modify the build code to enable H.265 with his builds.
@Anon2631 As noted earlier, I lost track of anons somewhere along the way. Apologies.
The missing UI features still is a quandry to me. I have not seen it here.... yet? o.0 Hopefully not, too.
Since the project dev build is affected for you, I would keep checking the dev builds for the next day or two. If nothing improves, you could have a viable bug report, and even more so iIMO f you can cross correlate the same issue as affecting Chrome Canary.
ffmpeg_branding = "Chrome"
proprietary_codecs = true
enable_hevc_demuxing = true
enable_ac3_eac3_audio_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
Had these in mind.
Until v64.0.3248.0, one extension I use to sync bookmarks between browsers (namely BookMacster Sync 2.1) was loading and working, but became forbidden in v64.0.3262.0 ("not from Web Store" comment — it's not available anymore from there, apparently, but was until recently).
Putting back v64.0.3248.0, the extension loads again without an itch... I bet you all know how to force load an extension, but me not being a dev of any kind, I have a hard time finding a solution... ;-)
Except for that small inconvenience, v64.0.3262.0 runs perfectly everywhere.
Is there any hope my issue gets fixed in a future release?
I'm on an AMD gpu and missing UI icons. Disabled hardware accel and they appeared
@Aargl Download or locate on your system the crx or zip file for the extension. A crx file is basically just a packed zip archive with some extra metadata. Extract its contents to a new folder with 7-Zip.
Alternatively. grab an extension downloader extension, like apparently this one....
https://chrome.google.com/webstore/detail/chrome-extension-source-v/jifpbeccnghkjeaalbbjmodiffmgedin
....and use it to download the desired extension directly as a zip, then conveniently use whatever zip archive app to extract.
Now launch Chromium, go to the about:extensions page, click developer mode, and load the unpacked extension. There could be extensions errors for whatever other reasons, but anyway, that is how to manually load a local extension. :)
Thank you for keeping up good work :)
Curious, are you scanning the mini_installer? Some installers can create as false positives as supposed trojans due to how they work. For example the mini_installer is a silent installer instead of interactive.
https://virusscan.jotti.org/en-US/filescanjob/smvrhcv640
https://virusscan.jotti.org/en-US/filescanjob/k0wtgrshfr
Chromium 62.0.3202.89 (Official Build) (64-bit)
Revision ba7a0041073a5e9928d277806bfe24c325d113e5-
OS Mac OS X
Chromium for 64-bit macOS - All Codecs - Sunday, 12 Novemberber 2017
Chromium 62.0.3202.89 (Official Build) (64-bit)
- NO Sync, NO WebRTC, NO Widevine
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- stable build
Chromium.app.62.0.3202.89.nosync.zip
https://github.com/macchrome/macstable/releases/download/v62.0.3202.89-macOS/Chromium.app.62.0.3202.89.nosync.zip
SHA1 C93657D142965887D4C1B642D3A6D5C600760ECF
BUILD INSTRUCTIONS: https://github.com/macchrome/macstable/releases/tag/v62.0.3202.89-macOS
Follow the instructions. If src/third_party/ffmpeg exsists DELETE it! - do the sync and patch; steps (iv) & (v)
I've taken a lot from the net: just giving back. No donations required.
Chromium 64.0.3266.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 5d7bc54757bc828e06a454c68b4dd9a3ec8f23d9-refs/heads/master@{#515858}
Compiler clang (+lld +fulllto +polly +partial_inlining +newgvn +compiler_optimizations)
chrome.zip | sha1: f5c77b395c732e71b06c4df5b2cf396c3f42fe0d
https://drive.google.com/open?id=1LuHM26eQ7YRevo6CMt6_vS5GPFM6om2H
mini_installer.exe | sha1: 4b6d0e58168777bdd5ec230993af5a90b5688f17
https://drive.google.com/open?id=1UGI-TLujVVbCer0wxDNPERNHtAUOk5Zs
@RobRich
Does this build (64.0.3266.0) contain the fix merged here? - https://chromium-review.googlesource.com/c/chromium/src/+/754247
If yes, then it does not correct the issue breaking extensions caused by the follow item (which you thought it might be intended for). - https://chromium.googlesource.com/chromium/src.git/+/30168b99604c48a32828f26b5acb2674beea1a5d
Unfortunately one still has to make a build without (30168b99604c48a32828f26b5acb2674beea1a5d) in order for it to function properly with certain extensions. Or the extension makers will have to see if they can code around the issue that's been created by these changes, provided it's permanent.
Just a heads up for those who are effected.
BTW, according to a related document I spotted, it appears Chromium is going the direction of prioritized user stylesheets for extensions - the idea behind 30168b9. Existing extension breakage was listed as expected. I am not sure if there will be interim mitigations at the browser level, but regardless, it is looking one should contact specific extension developers to ask about breakages and intentions on resolution.
and all 64.0. builds piss me of because of that laggy youtube, also spell checking doesnt work anymore. at least for me
I can confirm the spell checking not working. Not sure if it a Chromium regression or a Polly optimization issue. Will take a look.
Curious, do you have any extensions affecting YT and/or a/v? Reason I ask is YT finally is working locally for me in my Polly+FullLTO build for the site's current a/v formats.
Either way, the above is pretty much the reason why Polly builds still are experimental. ;) Thankfully I am not out of ideas on fixing and perhaps further improving it. Polly is more or less a personal interest thing for me instead of a serious build effort.
Spell check doesnt work also on other builds, not only on poly.
Netflix still not working with latest stable release since a few months now.
I guess something changed in the Google Chrome open source code
If anyone has figured out a way to make it work again, please share!
Spell check seems to be working selectively. For example, it works in Gmail for emails, but not here for comments. Hmmm.
Great browser thank you!
Compare to previous benchmark results: #comment-2592
= RobRich: No sync/WebRTC/Widevine • 64.0.3268.0 64-Bit (515942) [modified/clang+lld/wpo/thinLTO/lkcr]
Basemark Web (higher is better): 1282.58
Peacekeeper (higher is better): 6968
JetStream (higher is better): 268.20
Octane (higher is better): 53461
Kraken (lower is better): 781.9ms
Dromaeo V8 (higher is better): 2453.35runs/s
SunSpider (lower is better): 168.9ms
Speedometer (higher is better): 122.0
ARES-6 (lower is better): 17.52 ±0.36ms
MotionMark (higher is better): 806.89 ±2.51%
- Windows 10 x64 (FCU), i7-7700K Stock 4.5Ghz, 16GB 3000MHz DDR4, GTX 1070 8GB OC @ 1080p (388.13), 850 PRO SSD.
- All stock/default & clean profiles (no add-ons) between them & testing as usual to maintain purity. YMMV.
Interesting, improvements in most of them when compared to my last results, though not sure why Speedometer results basically cut in half.
Keep up the good work.
Yes, dropping crx onto about:extensions works too. But both solutions work only for the current session: once you relaunch Chromium, there's a gentle warning saying the addon gets disabled for your own safety... As the issue arose only in the two last Marmaduke builds, I'm wondering where is the change? (I mean in source or during compilation, some reinforced compatibility control? who knows...)
When I revert to 64.0.3248.0 (or the current Freesmug), it works just as before, even if it's written in about:extensions that the addon is "not from the webstore".
... And optionally --allow-outdated-plugins to disable browser notifications about outdated plugins -
Not sure what is happening with Speedometer. Could be a revision regression. Will consider it an outlier for now.
@Anon2660 Excellent!
@Aargl Do you have a direct link to the extension? It might just need a version compatiblity range patch, which I (or even you! :) probably could resolve. Then you could notify the developer to update with a quick fix.
I intend to maintain the MacOS stable build. At the moment I'm refining the build process. Give me a few days. The intention is to build (ALL CODECS):
(I) No sync, No Widevine, No WebRTC
(ii) Sync, Widevine, WebRTC
@RobRich
I've built an Apple LLVM (with polly)
- cmake -G Ninja -C /volumes/disk1/clang/llvm/tools/clang/cmake/caches/Apple-stage1.cmake ../llvm
- ninja stage2-distribution
When building Chromium, where do I place the Polly Clang flags: "-O3 -mllvm -polly"?
I've tried //build/config/mac/BUILD.gn:
# Without this, the constructors and destructors of a C++ object inside
# an Objective C struct won't be called, which is very bad.
cflags_objcc = [ "-fobjc-call-cxx-cdtors","-O3","-mllvm","-polly", ]
cflags_c = [ "-std=c99" ]
cflags_objc = cflags_c
cflags_objc += [ "-O3","-mllvm","-polly", ]
But I'm not sure the polly parameters are being used.
C:\depot_tools\chromium\src\build\config\compiler\build.gn
You will need to edit the Clang cflags with the "-O3","-mllvm","-polly", parameters as in your above comment. Start with the optimize_max and optimized_speed subsections, as those are the hottest code sections. Get them working with O3+Polly, then move to the standard optimize sections later if desired. If you want to watch what Polly is doing, add "-Xclang", "-Rpass-analysis=polly", to the cflags.
Note that ThinLTO currently does not support auto vectorization, so Polly does not work with it. As it stands ThinlTO is much more likely to generate better results anyway for a standard build. You still can pass -O3, though, which is a good starting point for compiler optimization assuming you do not care about output file sizes.
Conversely, FullLTO supports autovec, plus I am modifying LLVM and Polly parameters to perform additional optimizations, increase SCoP rates, etc. I have kept the Polly public builds rather conservative. My Polly internal builds currently pass something like 50-60 custom cflags parameters. Hopefully more details to follow in the future.
Thanks!
The Apple flavour of LLVM does not appear to support ThinLTO.
I know there are ThinLTO conditions for Mac in \build\config\compiler\build.gn, but as with some things in the Chromium build config, that does not mean it works as expected.
Are you explicitly using the LLD linker in the gn build args? I suppose the better question is does LLD even link on Mac?
@RobRich
LLD does not link on the Mac.
Read this guy's thesis https://web.archive.org/web/20190303201902/http://compilers.cs.uni-saarland.de/publications/theses/leidinger_bsc.pdf, then settled on the following parameters:
[ "-O3",
"-mllvm", "-polly",
"-mllvm", "-polly-ast-use-context",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-opt-maximize-bands=yes",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-dependences-analysis-type=value-based",
"-mllvm", "-polly-position=after-loopopt",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-rtc-max-arrays-per-group=40",
"-mllvm", "-polly-register-tiling" ]
I'm not really sure of the benefits of Polly: the greatest gain seems to come from compiling a bespoke LLVM. The Apple influenced version
of LLVM (and the default Chromium LLVM) produces efficient code and does vectorization by default.
(Thin)LTO is poorly supported and appears not to be a concern on the Apple Chromium platform.
Well, I've learnt a bit more about the Chromium build process, and reached the conclusion that Google/Chromium/Chrome should stop being so
frivolous: less time designing emojis; and more writing legible and valid documentation.
Polly works with the LLVM autovec, plus Polly has its own stripmine auto vectorizer if you want to try it. Big YMMV on stripmine, though.
If doing a local build, look into setting the tiling values for cache size, cache associativity, fma latency, etc. to match your processor. If doing a public build, you can explicitly disable tiling if desired so you are not tiling for a specific chip. IIRC, the defaults in the source are for a Sandy Bridge i7.
You can remove position and early inliner statements IMO. Polly now runs before the LLVM autovec stage by default, which is supposed to be the "preferred" position. The early inner was for when it ran at the front-end of LLVM.
Take care with computeout=0 as it could take awhile or even run away due to not being bound. The default is 500000, which I have found to be generally okay for most Chromium builds.
For a general Polly build, I tend to lean towards something like the following:
"-mllvm", "-polly",
"-mllvm", "-polly-unprofitable-scalar-accs=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-ignore-aliasing=true",
"-mllvm", "-polly-tiling=false",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-invariant-load-hoisting=true",
"-mllvm", "-polly-enable-polyhedralinfo=true",
"-mllvm", "-polly-check-parallel=true",
"-mllvm", "-polly-check-vectorizable=true",
"-mllvm", "-polly-prevect-width=32",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-Rpass=loop-vectorize",
Prevectorization width has a moderate impact here. I drop minimum loop instruction profitability to 40, which Polly devs suggest in the source for "interesting" interchange and transform opportunties while still preserving some profitability analysis.
The rpass switches show you what autovec and Polly are doing. Can be helpful for monitoring changes, plus you can log the terminal output if desired. I use wtee on Windows. I suspect Mac has the similar tee command like Linux.
BTW, I forgot before but ignore my Xclang statements. I deal with clang-cl on Windows versus you dealing with native clang on Mac. clang-cl is more about MSVC switch compatibilty, thus the need for Xclang to pass some of clang's own switches on Windows.
Still have to switch to FF in order to run NetFlix
Would really appreciate a fix
No formal numbers, but I did toss a couple of JavaScript benchmarks at the build. I noted minimal to possibly modest gains on my modern Core i5 notebook, while the gains looked more impressive - at least IMO - on my older Opteron build box.
Chromium 64.0.3271.0 (Official Build) (64-bit)
Revision 9fb91d70045741cdcbfad8df694abb5845000fbb-refs/heads/master@{#517198}
Compiler clang (+lld + fulllto +extended_compiler_optimizations)
chrome.zip | sha1: ab8c0fe9074d1e46be006c14119cde5b41ba7e93
https://drive.google.com/open?id=1KdfCHvzC9irTPRVIRaK-keRAEU0ziygb
mini_installer.exe | sha1: 1b0280c5bc641273e07ca31fe873cbb8b2d70a0f
https://drive.google.com/open?id=1KB70cgXez9ZwvV_jW6JEgIV4RFFcaJsY
ThinLTO currently does not support autovec, but I might eventually roll a couple of the other optimizations into my ThinLTO build.
----------------
@Fred + beast-usa I will do a local build with Widevine to try maybe seeing what is happening with Netflix. Might be a day or two assuming how I feel.
Widevine tends to work best with the stable builds.
(a)
third_party/widevine/cdm/widevine_cdm_version.h
+#include "third_party/widevine/cdm/widevine_cdm_common.h"
+#define WIDEVINE_CDM_AVAILABLE
+#define WIDEVINE_CDM_VERSION_STRING "@WIDEVINE_VERSION@"
OR
+#define WIDEVINE_CDM_VERSION_STRING "undefined"
OR
+#define WIDEVINE_CDM_VERSION_STRING "1.0.123.456" //find current version from json file.
(b)
Obtain current Widevine files from Chrome stable and place in respective position in the equivalent Chromium stable. (For testing purposes!)
Should work, but might require a revised browser header.
Basemark Web 3.0 (higher is better): 1203.19 - https://web.basemark.com/result/?4I0a1c23
Peacekeeper (higher is better): 7015 - peacekeeper.futuremark.com/results?key=FLnW&resultId=14670496
JetStream 1.1 (higher is better): 264.01 ± 4.1280
Octane 2.0 (higher is better): 51314
Kraken 1.1 (lower is better): 753.6ms +/- 0.8%
Dromaeo V8 (higher is better): 2449.42runs/s - http://dromaeo.com/?id=269790
SunSpider 1.0.2 (lower is better): 168.1ms +/- 1.0%
Speedometer 2.0 (higher is better): 127.3
ARES-6 (lower is better): 17.88 ±0.28ms
MotionMark 1.0 (higher is better): 790.37 ±25.87%
Performed with default fresh profile no add-ons, previous benchmark & PC specs here: #comment-2658
Figured it would be a mixed bag, especially on a modern processor. I noted better percentage improvements in informal SunSpider, Kraken, and SunSpider testing on my older Opterons than my Kaby Lake i5. I should dig up my old Pentium T-whatever notebook to see about performance on older Intel processors.
I am going to roll in Polly next to see about maybe improving some of the more intensive operations. Wish ThinLTO supported autovec and Polly, as waiting on a FullLTO build can be annoying. Not as bad as PGO, but still time consuming.
Chromium 62.0.3202.94 (Official Build) (64-bit) - Stable
Revision 937db09514e061d7983e90e0c448cfa61680f605-[refs/heads/master@{#499098}]
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- official build
- stable build
- O3 Optimised (including ffmpeg)
No Sync • No WebRTC • No Widevine
Chromium.app.62.0.3202.94.nosync.zip
https://github.com/macchrome/macstable/releases/download/v62.0.3202.94-r499098-macOS/Chromium.app.62.0.3202.94.nosync.zip
SHA1 25F829FD765CFA1CB558894FE8C638B31FCA4593
Sync • WebRTC • Widevine
Chromium.app.62.0.3202.94.sync.zip
https://github.com/macchrome/macstable/releases/download/v62.0.3202.94-r499098-macOS/Chromium.app.62.0.3202.94.sync.zip
SHA1 3C4273A708940DED78FC4AD2F8E92AEAAE1F097A
=========
If demand will update. The "stable" branch will always be built with the default development tools.
The "dev" branch will be built with SDK 10.13, a custom built compiler, and experimental optimisations; this branch might not be compatible with OSX 10.9.x: use the stable branch or the earth/browser shattering lump of lard known as Firefox 57 (RIP).
@Jerry: It could be nice if you add the LiberKey build ;)
If referencing PGO, it is more or less an occasionally update - like once a month - performance comparison build. Most likely will find ThinLTO to be the more performant of the two builds.
Polly+FullLTO is an experimental build at best. I like trying out various permutations in Polly to find optimization opportunities and hopefully performance improvements, but as for now, my Polly build is more of a personal interest. I use FullLTO for link time optimization as ThinLTO currently does not support building with Polly.
Somewhere on the upcoming agenda migth be working on LLVM scheduling optimizations and similar. I have done a little preliminary work already, and as expected, some operations appear to respond better to latency than throughout and others vice versa. It could be awhile before I have something ready for testing, but in the meantime let's see if my above sledgehammer-like approach to optimization works out okay enough.
The fanboy technical press might be in awe of Quantum's improved superduper features such as speed, concurrency and sandboxing; but I suggest that the average user is not. I've been using Firefox for years and through the use of various plugins have tailored Firefox to my precise requirements. Firefox Quantum breaks the majority of plugins that I use. Prefbar does not work; NoScript does not - but uMatrix is better anyway!; and the main "thing" that really irritates is Quantum's inability to do dynamic switching of PAC proxy files.
I cannot make the leap from Firefox 56.0.2 to 57: browser fuctionality and consistency should not be sacrificed for imperceptible (notional) technical improvements. Hence, the reason why I've been getting to know Chromium. Chromium is far from perfect, but it can be built from scratch and its imperfections improved.
Technicalities aside, pre Quantum Firefox is the best (pre-built) browser.
Until Firefox Nightly can faithfully replicate the functionality of 56.0.2 there is no need to upgrade. I know that the onus is on the plugin authors to make their products compatible with Quantum. Equally, Mozilla should have considered its existing user-base and not taken it for granted. Google has deep pockets and can promote Chrome to its heart's content: I've never seen Firefox actively promoted.
This icon appear when you make a search within a webpage in Chromium
https://support.google.com/chrome/answer/95440
Sorry for answering so late, I didn't want to fill the comments with marginal concerns about extensions, you've got enough work with development, I bet. ;-)
But as you're kind enough to propose it, I'd be happy to learn what part to edit — might be useful for other extensions, maybe...
About notifying the developer to update it is useless as they don't support that old version and the new version doesn't run on my version of MacOS (10.9.5)
I've put the extension on ln.sync.com/dl/13d3aa550/g4qfkh9c-cvtjb93w-dsqtj322-5zpumx5v
But frankly, if you don't have time, it's not a problem. :-)
@Anon2660
Adding --allow-outdated-plugins with Terminal doesn't seem to work in OSX: Chromium loads but still the warning about loading addons in dev mode... — in fact, the point is not that it's outdated but "not from Chrome Web Store" any more. ;-)
@Marmaduke
On the whole, I agree about FF57: it's faster on some sites, slower on others and the death of our beloved addons is a real PITA — even if some of them often were the main reason for slow-downs.
Basemark Web 3.0 (higher is better): 1159.16
Peacekeeper (higher is better): 7045
JetStream 1.1 (higher is better): 266.78 ± 8.5619
Octane 2.0 (higher is better): 53162
Kraken 1.1 (lower is better): 762.4ms +/- 1.3%
Dromaeo V8 (higher is better): 2452.75runs/s
SunSpider 1.0.2 (lower is better): 168.6ms +/- 2.4%
Speedometer 2.0 (higher is better): 124.6
ARES-6 (lower is better): 17.62 ±0.20ms
MotionMark 1.0 (higher is better): 775.22 ±20.86%
Performed with default fresh profile no add-ons, previous benchmark & PC specs here: #comment-2672
I did not expect much improvement, but it was worth a shot. The reality is much of Chromium already is optimized quite well IMO, so anything much beyond the immediate benefits of LTO are proving to be a few percent either way at best.
----------------
@Aargl Took a little learning curve on my part. Chrome extensions are a little different than (older) Firefox extensions, so it apparently was not a date range issue that I could show ya' how to fix in a couple of minutes. What I did find was a couple of introduced errors in the code due to changes in Chrome over the years.
One was a sync XMLHttpRequest that has been deprecated. I simply changed it to async request. The other was related to debugging features in the code. I disabled the debugging path and dropped a related code snippet. No guarentees if the fixes actually work as expected, but my local Chromium build now loads the extension and no longer complains about errors.
https://drive.google.com/open?id=1nfntDDDKCMCwvKQ2Q0t7B5h7x41vR9iU
You will have to download, extract the ZIP archive, and manually load the unpacked extension as discussed earlier. Like I said, definitely a huge YMMV on the quick fixes, but good luck. :)
Thanks
I still do a VS2017 build for PGO, but I have not been updating it regularly since ThinLTO typically outperforms it. Some of us have been using it as a comparison build for performance testing.
I just implemented a trial of a build cache for VS, so I might toss a PGO build at it. If build times could be reduced to something more reasonable, I might start updating PGO more often. Right now PGO takes hours to build, profile, and relink. Monolithic-style linking instead of the code compiling is the real underlying issue, though, and VS really could benefit from a parallel linker like ThinLTO IMO.
I have Netflix working locally. Now to see about getting a workable solution rolled into an actual build. Also, thank ya' Jimmy for tracking down the includes and defines for us. :)
As to another recent request, my build box is working on a 32-bit build. Clang+LLD with compiler optimizations, though currently without LTO.
Oh yeah, I turned the Clang optimization levels for building Chromium back down to more sane, yet still higher-than-stock optimized levels. There was just was not enough (if any?) measurable performance difference with my previous r517751 build, plus there was a slight chance of the non-conforming fast math optimizations breaking or at least changing expected floating-point calculations. Not worth it IMO.
A couple of casual benchmark runs returned pretty much expected results compared to other recent ThinLTO builds anyway.
----------------
The specially requested 32-bit build using Clang+LLD is now available.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v64.0.3276.0-r518611-win32
Thanks for trying! — although I still have the warning about dev mode, but as long as I can use the extension, it's ok. ;-)
----------------
Quick FYI. As Jimmy suggested, it bascially took a signed Chrome component for me to get Netflix working locally in testing, which AFAIK means it can not be distributed except by Google.
I've got a philosophical question for you: when I discovered Chromium a few months ago, an apparently very documented user at Macupdate.com (on FreeSMUG's Chromium page) declared to me that only the FreeSMUG build is safe and that using a different build (I was mentioning marmaduke's) might expose the user to "privacy loopholes or data leaks; your online banking for example, etc." — I think any software you download is a risk anyway, if you take that suspicious road... Why would you trust any browser and give it your bank account info, in the first place? ;-)
So is there a well-argued answer to give that user? Is FreeSMUG's build safer than Marmaduke's, on privacy matters? etc.
In a broader sense, consider practically any software supplied via an open source repository, download hosting site, etc. Assuming it was not built directly by the first-party developer(s) of the software, then what third party built it? What was the motivation for the third party? Most of the time end users just assume it is "safe" because they "trust" the repository, site, etc. at which the software is being hosted.
Ultimately and perhaps even more directly to a key aspect of the inquiry, much software is "use at your own risk" anyway - including many first- and third-party builds of proprietary and open source software. Even EULAs on expensive enterprise-class software can have interesting disclaimers.
Now back a word I used earlier. I like to think there is a level of *trust* involved. Admittedly, whether one trusts another is certainly a personal decision to make. From my perspective as a third-party builder, I make builds available because I am casually interested in things like open source, software optimization, etc. I try to routinely push updated builds, accept viable feedback, and attempt to help answer questions if/when possible; thus potentially working towards establishing greater trust with end users. Still I get it is each person's own decision to use or not use whatever build. If someone were to not trust my builds for whatever reason, then I can accept that position without feeling disrespected.
I would not trust ANY build (official or otherwise) of Chrome or Chromium with my banking details. Furthermore, I do not trust the Mac platform it self. The output of Little Snitch and Hands Off! (in advance mode) is very informative.
Now, do I trust FreeSMUG's Chromium? I've absolutely no desire to use FreeSMUG's Chromium so the question of "trust", security, etc.., is not an issue or even a consideration.
I build Chromium from source: patch the code where necessary (to enable CODECS) and adjust the build parameters. Do I trust my own build? Of course I don't! I'm familiar with Eloston's "ungoogled" and as such with the inherent untrustworthiness of Google's Chrome and Chromium. Active measures are required to mitigate Chrome/Chromium's short-comings, including: parameter adjustments; firewalls; selective use of plugins; PAC files; url filtering; and, packet sniffing.
It is incumbent on the computer/software user to familarise his/herself with all aspects of computer security.
Is FreeSMUG's build safer than Marmaduke's, on privacy matters, etc? Don't know, don't care! The consumer is sovereign: inform yourself.
Long story short, I had a PGO build using Clang+LLD instead of Visual Studio. The upside is the general idea is workable. The downside is it did not profile the renderer process, which is important for optimization. I will keep casually poking at it, but to clarify, it is not a priority issue.
Looking at the next serious step in optimization, eventually I would like to get PGO properly working with my ThinLTO build.
I used to be into the hardware overclocking scene. Even authored a published book about it many years ago. Guess the same approach has carried over into my software building. Recent example is my poking at LLVM build optimizations to perhaps speedup building Chromium.
It is long out of print and completely outdated these days. Actually it was almost outdated by the time it hit print given how fast things were moving in the hardware marketplace at the time. o.0
Otherwise I was an editor and/or writer for SysOpt, TechIMO, EarthWeb, Internet.com, Sharky, Hardware Central, etc. My content ranged from consumer-class hardware reviews to enterprise-class architectural analysis. Somewhere along the way I drifted away from writing and into various other dot com roles.
Also for clarification that bug was also in the official Chromium release so it wasn't due to Rob's builds or anything. Either Google fixed YouTube or the Chromium team fixed something. I dunno which one it is but I'm glad the bug is gone!
Also can confirm that the VS2017 build performs slightly slower than the Clang build.
Chromium 64.0.3281.0 (Official Build) (64-bit) - SDK 10.12
Revision b263ecdddb6137b8e5b9d7c7267da31d1ae91769-refs/heads/master@{#520049}
No Sync • No WebRTC • No Widevine • Non-Polly Optimised
Chromium.app.64.0.3281.0.nosync.nopolly.zip
https://github.com/macchrome/chromium/releases/download/v64.0.3281.0-r520049-macOS/Chromium.app.64.0.3281.0.nosync.nopolly.zip
SHA1 01F935F61440C66F6A6EAEBB876199FA0E00DB0F
Chromium.app.64.0.3281.0.sync.zip and Chromium.app.64.0.3281.0.nosync.zip have been Polly optimised - courtesy of RobRich:
"-mllvm", "-polly",
"-mllvm", "-polly-unprofitable-scalar-accs=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-ignore-aliasing=true",
"-mllvm", "-polly-tiling=false",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-invariant-load-hoisting=true",
"-mllvm", "-polly-enable-polyhedralinfo=true",
"-mllvm", "-polly-check-parallel=true",
"-mllvm", "-polly-check-vectorizable=true",
"-mllvm", "-polly-prevect-width=32",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-Rpass=loop-vectorize",
There is some "weird" coding regarding AddStream:
content/renderer/pepper/pepper_media_device_manager.cc
content/renderer/media/media_stream_device_observer.h
There are multiple ways to go about it, but as of yesterday here are my modifications to get "enable_webrtc = false" building.
git revert --no-commit 26dbd9b3b9c99ae956d29e4d248de3e9dbe9044c
git revert --no-commit 8e4615e18605e9bab1f0389ff93d56dbeed95a22
git revert --no-commit 9765503d41052108b01cf942d8e686c074f9d8c3
git revert --no-commit 6a34edfca277487d225e6c629c6ce2058bf12972
chrome/browser/BUILD.gn
add back at ~1795:
"//third_party/webrtc/modules/desktop_capture",
"//third_party/webrtc_overrides",
"//third_party/webrtc_overrides:init_webrtc",
chrome/browser/extensions/api/desktop_capture/desktop_capture_base.cc
@ ~119
current:
#if defined(OS_CHROMEOS)
screen_list = base::MakeUnique<DesktopMediaListAsh>(
DesktopMediaID::TYPE_SCREEN);
#else // !defined(OS_CHROMEOS)
screen_list = base::MakeUnique<NativeDesktopMediaList>(
content::DesktopMediaID::TYPE_SCREEN,
webrtc::DesktopCapturer::CreateScreenCapturer(
content::CreateDesktopCaptureOptions()));
#endif // !defined(OS_CHROMEOS)
change to:
#if defined(OS_CHROMEOS)
screen_list = base::MakeUnique<DesktopMediaListAsh>(
DesktopMediaID::TYPE_SCREEN);
#else // !defined(OS_CHROMEOS)
webrtc::DesktopCaptureOptions capture_options =
webrtc::DesktopCaptureOptions::CreateDefault();
capture_options.set_disable_effects(false);
screen_list = base::MakeUnique<NativeDesktopMediaList>(
DesktopMediaID::TYPE_SCREEN,
webrtc::DesktopCapturer::CreateScreenCapturer(capture_options));
#endif // !defined(OS_CHROMEOS)
@ ~142
current:
#if defined(OS_CHROMEOS)
window_list = base::MakeUnique<DesktopMediaListAsh>(
DesktopMediaID::TYPE_WINDOW);
#else // !defined(OS_CHROMEOS)
// NativeDesktopMediaList calls the capturers on a background thread.
// This means that the two DesktopCapturer instances (for screens and
// windows) created here cannot share the same DesktopCaptureOptions
// instance. DesktopCaptureOptions owns X connection, which cannot be
// used on multiple threads concurrently.
window_list = base::MakeUnique<NativeDesktopMediaList>(
content::DesktopMediaID::TYPE_WINDOW,
webrtc::DesktopCapturer::CreateWindowCapturer(
content::CreateDesktopCaptureOptions()));
#endif // !defined(OS_CHROMEOS)
change to:
#if defined(OS_CHROMEOS)
window_list = base::MakeUnique<DesktopMediaListAsh>(
DesktopMediaID::TYPE_WINDOW);
#else // !defined(OS_CHROMEOS)
// NativeDesktopMediaList calls the capturers on a background thread.
// This means that the two DesktopCapturer instances (for screens and
// windows) created here cannot share the same DesktopCaptureOptions
// instance. DesktopCaptureOptions owns X connection, which cannot be
// used on multiple threads concurrently.
webrtc::DesktopCaptureOptions capture_options =
webrtc::DesktopCaptureOptions::CreateDefault();
capture_options.set_disable_effects(false);
window_list = base::MakeUnique<NativeDesktopMediaList>(
DesktopMediaID::TYPE_WINDOW,
webrtc::DesktopCapturer::CreateWindowCapturer(capture_options));
#endif // !defined(OS_CHROMEOS)
Wow, you are far too diligent!
diff -Naur org\chrome\browser\BUILD.gn new\chrome\browser\BUILD.gn
--- org\chrome\browser\BUILD.gnMon Oct 23 13:52:13 2017
+++ new\chrome\browser\BUILD.gnMon Oct 23 14:41:25 2017
@@ -1747,6 +1747,9 @@
"//third_party/metrics_proto",
"//third_party/re2",
"//third_party/smhasher:cityhash",
+ "//third_party/webrtc/modules/desktop_capture",
+ "//third_party/webrtc_overrides",
+ "//third_party/webrtc_overrides:init_webrtc",
"//third_party/widevine/cdm:headers",
"//third_party/zlib",
"//third_party/zlib:minizip",
@@ -3961,11 +3964,7 @@
"media/webrtc/webrtc_text_log_handler.cc",
"media/webrtc/webrtc_text_log_handler.h",
]
- deps += [
- "//third_party/webrtc/modules/desktop_capture",
- "//third_party/webrtc_overrides",
- "//third_party/webrtc_overrides:init_webrtc",
- ]
+
}
if (!is_chrome_branded) {
*******
PATCH: chrome/browser/extensions/api/desktop_capture/desktop_capture_base.cc
Comment out lines 123 to 126 and 151 to 154
*******
*******
content/renderer/pepper/pepper_media_device_manager.cc
if (success)
GetMediaStreamDeviceObserver()/*->AddStream(label, device)*/;
*******
I really think that The Chromium Authors should respect the enable_webrtc flag.
uBlock is able to block WebRTC.
Chromium is built on multiple other platforms with Clang, so the goal was getting the Windows build working with Clang as well. ;)
Another reason is Google is a contributor to the open-source Clang project.
----------------
Glad to see the Windows builds are back to Clang on Win by default. Excellent! :) Hope it sticks this time.
Quick note. The WPO build arg currently does nothing with Clang as long as the MS linker is still being used. Then again it does not really matter much anyway IMO, as the default LTO config even when explicity setting LLD with ThinLTO is /opt:lldlto=0 right now due to file size concerns. If file sizes are not an issue, one can comment out the line (which I do) in the compiler build config to get LTO optimizations working when using the ThinLTO build argument.
----------------
Speaking of LLD, I need to look into turning on CFI as a replacement for CFG used by the VS linker. I know the CFI build argument is there, but it has been awhile since last trying it, especially with ThinLTO enabled. Could be something for an upcoming build.
----------------
I have an updated *experimental* Polly+FullTO build available for those interested.
Chromium 64.0.3280.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 7bd06facab4413a6e14c6dfb447db17e0f08e888-refs/heads/master@{#519227}
Compiler clang (+lld +fullto +polly +partial_inlining +compiler_optimizations)
chrome.zip | sha1: b7655b2b7c88becc210279260dfc93c62bac3ce8
https://drive.google.com/open?id=1VgV96mFmYPsqvRQS7aP7Xqn2Bv8tv1hY
mini_installer.exe | sha1: 077cf136ccc77bbf29ab05fd95f56cbe2e807309
https://drive.google.com/open?id=1TLZbifWVI9Hh1ZGtCjTUY2I3JHvf7uVT
Various Polly and LLVM options for the publc build are listed below. Hightights include enabling the experimental loop distribution and loop versioning components in LLVM, as Polly is dealing with loop interchange. All Chromium optimizations targets built at -O3. NACL targets built at -O3. FullTO with whole program vtables enabled.
"-mllvm", "-enable-partial-inlining",
"-mllvm", "-enable-loop-distribute",
"-mllvm", "-enable-loop-versioning-licm",
"-mllvm", "-enable-simple-loop-unswitch=true",
"-mllvm", "-reroll-loops=true",
"-mllvm", "-extra-vectorizer-passes=true",
"-mllvm", "-adce-remove-loops=true",
"-Xclang", "-vectorize-slp",
"-Xclang", "-vectorize-loops",
"-Xclang", "-Rpass=loop-vectorize",
"-mllvm", "-polly",
"-mllvm", "-polly-tiling=false",
"-mllvm", "-polly-unprofitable-scalar-accs=false",
"-mllvm", "-polly-ignore-aliasing",
"-mllvm", "-polly-pattern-matching-based-opts=true",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-invariant-load-hoisting=true",
"-mllvm", "-polly-opt-maximize-bands=yes",
"-mllvm", "-polly-enable-polyhedralinfo=true",
"-mllvm", "-polly-check-parallel=true",
"-mllvm", "-polly-check-vectorizable=true",
"-mllvm", "-polly-prevect-width=32",
"-mllvm", "-polly-opt-max-constant-term=-1",
"-mllvm", "-polly-opt-max-coefficient=-1",
"-mllvm", "-polly-run-dce",
"-Xclang", "-Rpass-analysis=polly",
Just did a quick test here. YouTube and Jerry's video testing list are working on my notebook; at least for the build's supported formats. System has a Kaby Lake Core i5 with GeForce 1050 graphics.
https://tools.woolyss.com/html5-audio-video-tester/
Chromium 64.0.3280.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 7bd06facab4413a6e14c6dfb447db17e0f08e888-refs/heads/master@{#519227}
Compiler clang (+lld +fullto +polly +partial_inlining +compiler_optimizations)
On :
Windows 8.1 64-bit
Intel Core i7 4710HQ @ 2.50GHz39 °C
Haswell 22nm
Intel HD Graphics 4600
NVIDIA GeForce GTX 850M (388.13)
Extensions, Options, Youtube Lag, etc. everything works fine for me…
@Anon2712 Try the usual if the issue persists with other builds. Clear flags, update GPU drivers, etc.
Win 7 x64, ivy bridge, nvidia pascal
@Anon2712 I did spot a possibly related bug report for Chrom(ium) in general. If nothing else helps with green screen videos, try adding --disable-nv12-dxgi-video to the command line.
https://en.wikipedia.org/wiki/Control-flow_integrity
I personally don't have any opinion or preference specific to either, but I was just curious about it since Chrome has switch default Windows compiler to clang now. As long as the browser is fast/efficient and stable, that is what matters most to me. Thanks.
And thats annoying. Also spell check still doesnt work.
Using robs latest clang build.
I've already disabled Auto-fill and "Manage Password" in settings. Never get this popup in Chrome.
@kronos Looks like you might previously have saved passwords. If none of them are important to you, you can try going to "Clear browsing data" and clearing the passwords.
I've just installed this Chromium, never saved any password, the password list is empty. I'm running the Stable x64 Nik's build on Windows 10 x64
I followed your suggestion and tried clearing the password, but it still shows the popup. Any other suggestion?
Taking a shot here, but also try manually forcing the following browser configuration flag to disabled. Copy and paste the URL, force the setting, then click relaunch.
chrome://flags/#enable-manual-fallbacks-filling
It solved the problem, thanks for your help!
@Jerry Ya' got email. Basically to disable the CFI tag for now. Thanks in advance! :)
A refresh is then needed to proceed with normal video playing.
@Danfun64 The only way I could get it to work with Netflix was briefly testing with the signed version of Widevine, which is distributed for Chrome (not Chromium) under very specific licensing, as obtained from Google's own download servers. Given the terms of the license, it is not something third-party builders can package with Chromium. Translation? Sadly, there does not appear to be a viable fix at this time.
Then I run the installer to update my previous Chromium 62 installation (also Nik version, no-sync), but after that my Chromium doesn't work anymore.
It gives me "Aw, snap" error page and all webpage doesn't render correctly.
I thought I could update Chromium by simply running the installer, but seems like it breaks my Chromium.
Is there any way to fix this? Any chance to save my old configuration?
Dev still works, but I have issues with reddit enhancement suite so I'd rather not use it...
What could be wrong?
Any about:flags set or content filtering extensions enabled?
Thank you for your feedback.
I removed the latest stable version 63 of Nik because it is really buggy. I contacted him.
Sorry for the inconvenience!
I tried to run the previous v62 installer, but it won't downgrade my Chromium. Do I need to uninstall v63 first? Will I lose all my configuration?
Thanks
@kronos: It is not difficult to downgrade Chromium because user data and application are always in different places.
- Installer (.exe): Follow my tutorial about #older-version (Same way for Nik and RobRich builds!)
- Archive (.zip): Replace all the files from the installation directory by the new ones.
- Portable (chrlauncher): Remove the "bin" folder of chrlauncher. Then re-launch chrlauncher.
for the "No sync • No WebRTC • No Widevine" of 62.0.3202.94 (499098) the date "Thursday, 7 Dec 2017" is not correct. This one was released a month ago. That date better matches "Reference: Current stable version (Google Chrome): 63.0.3239.84 (508578) • Wednesday, 6 Dec 2017"
Best regards
I found it interesting that Stable branch Google Chrome 63 release has remained a PGO build (VS 2017). They were intending on switching to clang but I guess decided not to with stable branch yet.
In the meantime, try adding " --disable-d3d11" to the command line. Chromium should fall back to D3D9 for hardware acceleration.
I made a shortcut to change profile directory, but whenever I try to open a html file it runs the profile and settings from AppData directory...
https://defaultprogramseditor.com
For example, go to file type settings and edit the default open context menu command for HTML, HTM, etc. files to point to chrome.exe with whatever command line switches. I suggest using the registry backup feature in the app before editing the associations.
Some guy contacted me saying that audio was not working with Twitter video. I don't do social media! would someone who uses Twitter please test.
In an effort to solve the guy's problem, I've enable AC3 decoding - which indirectly (I think) has enabled AAC multichannel: would someone with a (HDMI) multi-channel set-up please test:
https://www2.iis.fraunhofer.de/AAC/multichannel.html
I am curious, if you use the chromium-sync.exe installer for example, where does it install? User profile or Program Files?
Thank you!
Does anyone specifically have experience with Chromium on Windows with Group Policy templates?
On my primary notebook Chromium is installed under the expected user profile appdata directory as far as Windows and the Chromium mini_installer are concerned, but the default Chromium directory is symbolically linked to a directory on a separate Optane drive where the files actually reside.
Please.
Is possible to have update for 32 bit No sync • No WebRTC • No Widevine • 65.0.3291.0 (523025) ?
guys, your work is greatly appreciated!
Chromium 65.0.3294.0 (Developer Build) (64-bit) | No Sync | No WebRTC | No Widevine
Revision a7a0c21c4aaf3cc53bfaa96ec59e1e7b3bba30fa-refs/heads/master@{#523774}
Compiler clang (+Polly +compiler_optimizations)
chrome.zip | sha1: 85dd4858095467dffc4535f58b984b3ff670fc59
https://drive.google.com/open?id=12Q_E5QMFq8UWM4ZnM9oB9ajl3yj-tJAv
mini_installer.exe | sha1: d5929af37a717507d96d39acfe46a557c0ea5ccc
https://drive.google.com/open?id=1orIrFi7GMQok1Zk3u6qy30iJvJ2HTQjG
Targeted optimizations include -O3 for hot code, though -Os for remaining code to keep file sizes within reason as it is not a lightweight build. o.0 FullLTO is not enabled due to annoyingly long build times. As usual, it is an *experimental* build. YMMV.
If anyone else using Polly is looking at the -Os optimization level with a question mark, these days Polly will work with other levels offering autovectorization instead of just -O3 as indicated in the older documentation. :) I still have the habit of passing -vectorize-loops and -vectorize-slp anyway, and it is not a bad idea IMO since I have seen autovec disabled for whatever reason(s) even it was expected to be enabled.
I was finally able to spend a few minutes cleaning up and updating the Polly config based upon a skim through recent source code. I likely will start enabling standard tiling for future generalized Polly builds since the default tuning should be okay for many modern processors.
"-mllvm", "-adce-remove-loops",
"-mllvm", "-costmodel-reduxcost",
"-mllvm", "-enable-deferred-spilling",
"-mllvm", "-enable-interleaved-mem-accesses",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-mergeicmps",
"-mllvm", "-enable-mssa-loop-dependency",
"-mllvm", "-enable-partial-inlining",
"-mllvm", "-enable-pipeliner-opt-size",
"-mllvm", "-exhaustive-register-search",
"-mllvm", "-expensive-combines",
"-mllvm", "-extra-vectorizer-passes",
"-mllvm", "-inline-threshold=1000",
"-mllvm", "-join-globalcopies",
"-mllvm", "-join-splitedges",
"-mllvm", "-loop-prefetch-writes",
"-mllvm", "-optimize-regalloc",
"-mllvm", "-regalloc=greedy",
"-mllvm", "-reroll-loops",
"-mllvm", "-slp-vectorize-hor-store",
"-mllvm", "-split-spill-mode=speed",
"-mllvm", "-unroll-allow-partial",
"-mllvm", "-unroll-allow-remainder",
"-mllvm", "-unroll-remainder",
"-mllvm", "-unroll-revisit-child-loops",
"-mllvm", "-unroll-runtime",
"-mllvm", "-unroll-runtime-epilog",
"-mllvm", "-unroll-runtime-multi-exit",
"-mllvm", "-use-wide-memcpy-loop-lowering",
"-mllvm", "-vectorizer-maximize-bandwidth",
"-mllvm", "-x86-experimental-vector-widening-legalization",
"-mllvm", "-polly",
"-mllvm", "-polly-allow-dereference-of-all-function-parameters",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-optree-normalize-phi=true",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-tiling",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
----------------
My symbolic directory link setup just resulted in a sandboxing error. The quick fix was simply moving Chromium back to its default directory for now. Something to look at later. Anyway....
Octane Score: 34638
JetStream: 164.79 ± 1.5436
Speedometer 2.0: 64.17
Marginally better than your normal dev builds, however, I noticed some crashes with sites using JWPlayer to server video content. One chrome.exe process is pinned to 25% CPU usage and requires a kill task via task manager, otherwise it's just frozen. But other than that, normal browsing, you're all good.
I suspected there could be some (or even many) issues, as I was compile testing primarily for build breakage instead of browser usability with those numerous LLVM options. Good to see usability is not too bad. The options should be dramatically paired down for an actual public Polly build, which should improve usability.
It is one of the quicker ThinLTO builds in recent times acccording to a few benchmarks I casually ran. Plus I still need to evaluate other options, such as tweaking register allocation, before going public with them in ThinLTO.
BTW, the sandboxing error with using Chromium via a symbolic directory link is resolved, too. Think it was due to a NaCL workaroud I had applied with the previous Polly build.
Basemark Web (higher is better): 1129.73
Peacekeeper (higher is better): 6849
JetStream (higher is better): 259.85± 2.9727
Octane (higher is better): 52625
Kraken (lower is better): 769.7ms +/- 0.7%
Dromaeo V8 (higher is better): 2411.35runs/s
SunSpider 1.0.2 (lower is better): 178.2ms +/- 1.7%
Speedometer 2.0 (higher is better): 119.4
ARES-6 (lower is better): 21.37 ±0.30ms
MotionMark (higher is better): 762.66 ±2.77%
Previous benchmark: #comment-2688
I too have noted some performance regressions in recent weeks with various builds; ThinLTO and otherwise.
I cranked up LTO agressiveness to max to hopefully help.
The -Os code paths should not matter much, but I will reeval to verify. I was trying to reign in code size a little along the colder code paths, but I can go back to -O3 across the board easily enough if needed be.
I still would like to get PGO working with Clang+LLD, but as of this week, it continues to not profile the needed renderer process(es). I still have another idea or two about PGO, but it is getting around to them as I feel up to it.
Ok. i will wait. I hope you relsove errors.
Thank's anyway.
Looks like I will go back to bulding all targets at -O3. I will try to get a new release out in the next day or two.
ALL GOOD :) Thanks nik :) Thanks Jerry :) Much Appreciated :)
Hv a gd wkend
https://www.virustotal.com/#/file/e2093b98c43fac6384530e25a782b6784560a7aca5539a39397a8453b77f02c1/detection
Appears to be a false positive, it happens at least since v61. No idea why Baidu engine still considers those builds have ties to WisdomEyes.
Also, if you'd have checked other earlier builds including zip, sync and 32bit flavors, you'd find a couple other random detections from different engines.
Basemark Web 3.0 (higher is better): 1219.85 https://web.basemark.com/result/?Qe3HeSn
Peacekeeper (higher is better): 6971 peacekeeper.futuremark.com/results?key=FRPj&resultId=14916717
JetStream 1.1 (higher is better): 262.79± 5.4952
Octane 2.0 (higher is better): 52518
Kraken 1.1 (lower is better): 762.3ms +/- 0.7%
Dromaeo V8 (higher is better): 2418.34runs/s
SunSpider 1.0.2 (lower is better): 177.4ms +/- 0.9%
Speedometer 2.0 (higher is better): 120.1
ARES-6 (lower is better): 21.29 ±0.38ms
MotionMark 1.0 (Large) (higher is better): 787.50 ±20.30%
Previous benchmark: #comment-2780
------------------
New Polly+FullLTO build. Actually it is an internal build tiled for Intel Skylake, Kaby Lake, and similar; though it still should perform fine on most modern processors. YMMV of course.
The myriad of extra LLVM tweaks are gone for now, so usability should be okay. Loop unrolling is disabled in LLVM as a test. Polly deals with loops anyway, so I decided to "feed" it plenty of them :)
It still is far more an experimental build than an actual perforamnce build, but Peacekeeper scored close to a recent ThinLTO build in a quick run. Tested on my Core i5 7300HQ notebook with 16GB DDR4, GTX 1050, etc.
Chromium 65.0.3297.0 (Official Build) (64-bit) - No Sync | No WebRTC | No Widevine
Revision 7452277311e15a3459b4fb6fa428840c6afde4df-refs/heads/master@{#524613}
Compiler clang (+polly +fulllto +compiler_optimizations)
chrome.zip | sha1: 5ca45e9d831c53103d64d873f002ecf77954be80
https://drive.google.com/open?id=1Ll_OI2CzRSJf5J5EqwfU6zCNrHrTYjtt
mini_installer.exe | sha1: aac2ad460e52fed6ae106e47c7a869ed8d1a7e67
https://drive.google.com/open?id=1x9bO2sLbWWPhBu26EcYEjNmWjBI_6aHc
"-mllvm", "-polly",
"-mllvm", "-polly-allow-dereference-of-all-function-parameters",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-ignore-aliasing",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-prevect-width=16",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-target-2nd-cache-level-associativity=4",
"-mllvm", "-polly-target-latency-vector-fma=4",
"-mllvm", "-polly-tiling",
"-mllvm", "-polly-2nd-level-tiling",
"-Xclang", "-fno-unroll-loops",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
Previous Polly Build
Octane Score: 34638
JetStream: 164.79 ± 1.5436
Speedometer 2.0: 64.17
Current Polly Build
Octane Score: 35095
JetStream: 167.33 ± 2.3433
Speedometer 2.0: 72.78
Current thinlto Build
Octane Score: 35183
JetStream: 168.24 ± 1.3657
Speedometer 2.0: 71.47
Odd, thinlto seems to be similar/if not marginally better than polly, but polly feels snappier in stuff like video content seeking...etc. By the way, good news, that JWplayer issue from last polly build is gone. For normal browsing, so far polly is as stable as thinlto. :)
You very well could note a slight difference in a/v performance. Much of the a/v components like ffmpeg, vpx, etc. rely heavily upon loops; and Polly is designed to optimize loops. Similar situation for JavaScript, SSL, sandboxing, some of the GPU subsystem, etc.
Well, actually JavaScript is kind of a special case. Despite expectations of Polly helping, V8 already is so optimized that Polly thus far have done little to nothing for optimizing JS performance. Win some, lose some. ;)
Many Thank You for No sync • No WebRTC • No Widevine • 65.0.3299.0 (524662) !!!
I just pushed an updated ThinLTO build a few minutes ago. Hopefully it resolves the issue for ya'.
- Intel Core i7 4710HQ @ 2.50GHz
- Intel HD Graphics 4600 + NVIDIA GeForce GTX 850M (388.13 / 23.21.13.8813)
No problem to read PDFs here (local or remote) with penultimate version 65.0.3296.0 or last version 65.0.3299.0
Also :
➜ No Youtube « 𝑨𝒘! 𝑺𝑵𝑨𝑷! » or lag.
➜ No green screen on videos.
➜ No extension (local or chrome store) problems
➜ No problem with 2D ou 3D (google maps…)
➜ All settings are preserved with update.
For me — at least — everything is fine with the lastest dev-clang-nosync / 65.0.3299.0 /524909 ★ RobRich version…
Thanks all folk for for works and above all to share it !
thanks for the great efforts as always. Since a while I am having issues viewing offers by Groupon Germany, all their offers make Chrome "Aw, Snap!" after the page has been loading for a while. Please check this example:
https://www.groupon.de/deals/wachbergschanke-dresden-3
Is this just my Chrome config or related to the Clang build? I have just upgraded to 65.0.3300.0 (525175) • Wednesday, 20 Dec 2017 and the issues persists (has been going on since about a month or two).
Thank you,
Lorenz
Chromium 65.0.3299.0 (Official Build) (64-bit)
Revision 83d37523e3af93d816f70c81f37b5ac1ab7b66c5-refs/heads/master@{#524693}
OS Windows
No Sync - No WebRTC - No Widevine
Boostrapped Clang - LLD Linker - FullLTO - Polly Optimised
chrome.packed.2017.12.20.LTO.AC3.7z
https://github.com/macchrome/winchrome/releases/download/v65.0.3299.0-r524693-Win64/chrome.packed.2017.12.20.LTO.AC3.7z
SHA1 3F25F35C4AD907BACF1C09CE98FD28692D285195
I have a public build based upon it currently cooking since the internal build is specifically tiled for Skylake, Kaby Lake, etc. Hopefully the performance holds with the standard tiling I opt for public releases versus the processor-specific tiling I prefer for internal testing on a particular system.
----------------
Quick question. Anyone still using the VS2017 PGO build(s)?
I do not mind continuing perhaps an occasional VS2017 *basic* build if there is a real need by someone, so it would be a good time to let me know, but I have little reason to continue tossing hours of system time at PGO building with Chromium now having officially transitioned to Clang on Windows.
Chromium 65.0.3300.0 (Official Build) (64-bit)
Revision 05c0006e3a511fa6f71257c65c7a804fbd7f495d-refs/heads/master@{#525330}
Compiler clang (+lld +polly +fulllto +compiler_optimizations)
chrome.zip | sha1: ba88d1e201ef41b49fae1afb57284ab51b713d15
https://drive.google.com/open?id=1-LwJm0pq3fPPjkhOL2uof1bDnZD5GZ6k
mini_installer.exe | sha1: 2740f8636d2fb10f1e68f455ae5a2668aa46411d
https://drive.google.com/open?id=1amsatSU2qyp8Ti90HvWeIrdOCx17_zo5
"-mllvm", "-polly",
"-mllvm", "-polly-allow-dereference-of-all-function-parameters",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-ignore-aliasing",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-prevect-width=16",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-tiling",
"-Xclang", "-fno-unroll-loops",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
----------------
VS2017 PGO is discontinued. I have notified Jerry. If anyone needs a basic VS2017 build - other than PGO ;p - for a specific reason, let me know. I can submit it here in the comments on an as needed basis.
Looking forward, ThinLTO still is my primary build effort, but I am considering adding Polly+FullLTO to my GitHub account as well. Polly+FullLTO performance and usability are finally stabilizing to the point of being viab e enough for a daily-use build IMO.
Basemark Web 3.0 (higher is better): 1283.64
Peacekeeper (higher is better): 6876 peacekeeper.futuremark.com/results?key=FRx1&resultId=14946322
JetStream 1.1 (higher is better): 249.75± 0.62156
Octane 2.0 (higher is better): 51790
Kraken 1.1 (lower is better): 772.8ms +/- 0.8%
Dromaeo V8 (higher is better): 2405.09runs/s (Total)
SunSpider 1.0.2 (lower is better): 177.5ms +/- 1.1%
Speedometer 2.0 (higher is better): 121.7
ARES-6 (lower is better): 21.29 ±0.28ms
MotionMark 1.0 (higher is better): 794.32 ±8.48%
Previous benchmarks: #comment-2788
Similar trending here with Basemark, MotionMark, and Speedometer.
Can you test for me what happens if you go to:
https://catalog.update.microsoft.com/
I get : "This site can’t be reached"
The webpage at https://catalog.update.microsoft.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY
However, when accessing a sub-site directly there, it works: https://www.catalog.update.microsoft.com/support.aspx
Cheers:)
If not already, try disabling all extensions to help diagnose the issue.
Check for component updates, especially CRLset and Signed Tree Heads:
chrome://components/
Make sure this flag if present is at default:
chrome://flags/#tls13-variant
----------------
Speaking of security, ThinLTO and Polly now feature Control Flow Integrity (CFI) exploit mitigation enhancement. There could be a tiny performance impact, but I am not noticing it in a couple of casual tests. CFI in LLVM is quite streamlined.
https://en.wikipedia.org/wiki/Control-flow_integrity
----------------
Polly is now available at GitHub, including a fresh build. :)
https://github.com/RobRich999/Chromium_Polly
On your last release available here : https://github.com/RobRich999/Chromium_Clang/releases/tag/v65.0.3301.0-r525689-win64
Chromium 65.0.3301.0 (Official Build) (Windows 64-bit) - No Sync | No WebRTC | No Widevine
Revision e28cfc7674edef7a95782243f679bec2610cf654-refs/heads/master@{#525689}
Compiler clang (+lld_linker +thinlto +npm +compiler_optimizations +cfi)
chrome.zip :
Is not ➜ v65.0.3301.0-r525689-win64
But you mistakenly packed ➜ v65.0.3300.0-r525175-win64
See :
@Lorenz : no problem here on https://catalog.update.microsoft.com with 65.0.3300.0 (525175 / win64)
I did not log the traffic, but https://catalog.update.microsoft.com/ probably is some type of IIS configuration issue with the particular subdomain, directory, etc. I suspect it at least should be returning a HTTP 301 redirect or similar, but apparently it is not serving up a currently valid SSL protocol for HTTPS to serve the reply to the browser's request.
-----------
Since my build box was not busy for awhile today:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v65.0.3302.0-r526000-win32
Features ThinLTO, CFI, compiler optimizations, etc. :)
Do not expect my regular return to 32-bit builds like I once did, as I have no immediate use for Chromium 32-bit these days, but I do not mind occasionally pushing them here via the comments.
Again, thanks!
Fresh ThinLTO builds without CFI:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v65.0.3303.0-r526153-win64
https://github.com/RobRich999/Chromium_Clang/releases/tag/v65.0.3303.0-r526153-win32
Chromium 65.0.3303.0 (Official Build) (Windows 64-bit)
- Compiler clang (+lld_linker +thinlto +npm +compiler_optimizations)
Basemark Web 3.0 (higher is better): 1134.82 https://web.basemark.com/result/?4IZewaKL
Peacekeeper (higher is better): 6929 peacekeeper.futuremark.com/results?key=FSNS&resultId=14973520
JetStream 1.1 (higher is better): 249.64 ± 4.3437
Octane 2.0 (higher is better): 51662
Kraken 1.1 (lower is better): 766.4ms +/- 0.9%
Dromaeo V8 (higher is better): 2394.92runs/s
SunSpider 1.0.2 (lower is better): 179.2ms +/- 1.8%
Speedometer 2.0 (higher is better): 122.7
ARES-6 (lower is better): 21.46 ±0.43ms
MotionMark 1.0 (higher is better): 781.94 ±2.36%
_____
Chromium 65.0.3303.0 (Official Build) (Windows 64-bit)
- Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
Basemark Web 3.0 (higher is better): 1181.45 https://web.basemark.com/result/?4IZhL7nd
Peacekeeper (higher is better): 6922 peacekeeper.futuremark.com/results?key=FSNe&resultId=14973746
JetStream 1.1 (higher is better): 249.19 ± 3.7598
Octane 2.0 (higher is better): 51493
Kraken 1.1 (lower is better): 771.1ms +/- 0.6%
Dromaeo V8 (higher is better): 2405.11runs/s
SunSpider 1.0.2 (lower is better): 177.8ms +/- 1.5%
Speedometer 2.0 (higher is better): 121.9
ARES-6 (lower is better): 21.05 ±0.19ms
MotionMark 1.0 (higher is better): 776.75 ±2.80%
___
Merry Christmas to everyone.
Updated Polly+FullLTO build available.
Of particular note I have been able to greatly simplify the Polly build configuration. Subject to change of course.
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
Merry Christmas, Happy Holidays, etc. :)
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
chrlauncher shows (null) for new version, as in this issue: https://github.com/henrypp/chrlauncher/issues/79
@Joe: It works. Did you retry?
Thanks nik for your effort and time. A good year of safer browsing with your stable chromium is a plus for the good peace of mind. Awesome and much appreciated.
Thanks to all other contributors and your super work. Many here use it everyday!!! Much appreciated :)
May we all, humanity, grow up abit more and have safer and more meaningful 2018.
Wishing you ALL THE BEST in the New Year. Peace :)
https://chrome.google.com/webstore/detail/scriptsafe/oiigbmnaadbkfbmpbfijlflahbdbdgdf
Happy New Year to all ; Jerry and Nik !
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-dependences-computeout=100000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
The portable-version of RobRich shows an update to version "3310", but after installing it is Version 3306.
Quick FYI on a performance-related tangent while posting. Update KB4056892 is live for Win10. Drop a web search if unsure about what security issues it addresses. Long story short for most end users, systems with Intel processors *might* experience mild performance regressions. Older Intel procs without "process context identifiers" (PCID) support could incur marginally higher impacts. As usual, there could be edge cases showing greater differences.
Mainstream Intel processors from Westmere (IIRC) and up have PCID support, which can help soften the performance impact from deploying the security patch. Westmere shipped back in 2010, so modern chips like the mentioned 6th-gen Skylake and above should experience less performance impact versus much older Intel processors.
Similar situation with recent Linux kernel updates released for the issue.
----------------
Spectre probably affects AMD, Intel, and ARM processors. AFAIK there are no shipping patches for it.... yet? It is a more complex attack vector and more difficult to mitigate, though it reportedly affects a wider range of processor architectures.
----------------
Additional info and a FAQ on the processor security issues.
https://meltdownattack.com/
Linux and Windows have patches for Meltdown, so moving on to Spectre.
https://support.google.com/faqs/answer/7625886
There is Linux kernel work in progress to address Spectre.
https://lkml.org/lkml/2018/1/4/174
LLVM has introduced a hardening technique for x86 procs. The linker option for dynamic binaries currently appears to target Linux ELF binaries instead of Windows COFF binaries, though.
https://reviews.llvm.org/D41723
GCC is working on similar.
http://git.infradead.org/users/dwmw2/gcc-retpoline.git/shortlog/refs/heads/gcc-7_2_0-retpoline-20171219
https://www.chromium.org/Home/chromium-security/ssca
v65.0.3312.0-r527039-win64
"-mavx",
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-dependences-computeout=100000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-max-ops=200000000",
"-mllvm", "-polly-optree-normalize-phi=true",
"-mllvm", "-polly-prevect-width=32",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass=loop-vectorize",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
version=$(plutil -extract CFBundleShortVersionString xml1 -o - /Applications/Chromium.app/Contents/Info.plist | plutil -p - | sed -e 's/"//g')
echo $version
cd /Applications/Chromium.app/Contents/Versions/$version/Chromium\ Framework.framework/
ls -ld Versions Versions/A
chmod go+x Versions Versions/A
ls -ld Versions Versions/A
Can this please fixed in build environment? TIA
been using No sync • No WebRTC • No Widevine • 63.0.3239.132 (508578) • Friday, 5 Jan 2018 for the day now - ALL GOOD so far :)
Much appreciated
EVERY download fails with "Virus scan failed". On every download an access to client4.google.com is made which is blocked by our firewall by policy.
In advanced settings I am missing the checkbox for disabling the "online Google virus check".
On Linux Fedora the distro's Chromium package works fine.
There's no way to submit an issue to the chromium project without a google account.
Now I post a comment here as last try...
I would need 51.0.2704.106 with Sync WebRTC Widevine 64-bit because I can disable DirectWrite.
I know it's an old version and I'm aware of all its security issues.
With DirectWrite enabled, text is blurry and everything is harder to read for me. Please
What CPU are you running on your daily desktop? Have you experimented with tuning for that specific CPU (eg, -mtune=znver1 for Ryzen)? Or -mtune=intel (I know that's a GCC flag, not sure if that one overflows to clang as well). Also, do you know what level stack protector is default for Chromium? If it's just -fstack-protector, would you consider a build with -fstack-protector-strong?
Thank you for your great work and support dear developers and users.
@tx-chromium: Did you check with a new Chromium version? Which dev version? official? Which OS?
What happens if you try to access https://clients4.google.com/chrome-sync/time from your browser?
@Anon2851: I have got it. Unzip it with 7-Zip archiver if you prefer to install it via the ZIP content (= no auto install).
https://chromium.woolyss.com/f/chromium_win64_51.0.2704.106_r723_sync.exe
chrome://flags/#distance-field-text
chrome://flags/#enable-font-cache-scaling
chrome://flags/#lcd-text-aa
@Anon2852 I have tuned LLVM and Polly for Skylake, of which Kaby Lake is derived. On the LLVM side, there was not much of a difference compared to the stock x86-64 tuning. Polly might be a percent here or there based upon the specifics of the tiling configuration.
My build box is offline right now, but IIRC, there is no specific call to change tuning of stack smashing protectors in the general compiler config. I suppose there could be finer-grained control via function-level calls in the code. I will take a look into passing a custom compile-time ssp cflag if possible.
--------------------
Took a look. Chromium is passing "-stack-protector 2" at build time. Level 2 maps to sspstrong in LLVM. :)
--------------------
The occasional 32-bit ThinLTO build as previously mentioned.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v65.0.3315.0-r527556-win32
@RobRich I'll try those flags. Thanks!
Thank you for No sync • No WebRTC • No Widevine • 65.0.3315.0 (527543) . 32 bit
Works very good
There are technical reasons, primarily related to output code sizes, as to why O3 is not always appreciably faster than O2. That said, it anyone have significant performance regressions to note, just let me know. :)
Speaking of performance, I did note an impact in browser benchmark scores with the Windows processor security patch being rolled out. The test system includes a modern Intel Kaby Lake running Win10, thus supposedly among the expected least affected types of Intel configs. There is the possibility systems with older Intel processors and OSs might even notice some real-world performance differences when browsing.
Updated Polly build available. Like my latest ThinLTO build, I have migrated this Polly build to O2 for all optimized targets. See my previous post for reasoning, and I am open to feedback if there are notable regressions.
Processor AVX support is not a specific requirement unlike last time. I will look at revisiting SIMD tuning on vectorization later. Regardless, a quick run of Basemark Web 3.0 returned the highest score (IIRC) I seen on my Intel Kaby Lake test system since the Windows processor security patch landed.
Updated Polly build available. I have migrated Polly builds from the Microsoft stdlib C++ standard library to the LLVM libc++ implementation.
https://libcxx.llvm.org/
I will have to think about it, especially with the FullLTO build times involved, but Polly could become my primary build in the near future.
Running the build on two Windows 10.0.16299.192 boxes here. Current flags in use:
--flag-switches-begin --autoplay-policy=user-gesture-required-for-cross-origin --site-per-process --enable-features=ScrollAnchoring --disable-features=D3DVsync,EnableManualFallbacksFilling --flag-switches-end
@meconium The first part appears to be the usual warning about API keys missing, though I build without API keys, so it should not be happening. Are you are not supplying your own API keys, perhaps?
Windows 8.1 x64
Intel Core i7 4710HQ @ 2.50GHz - DDR3
Intel HD Graphics 4600 (10.18.14.4578) + 2Go NVIDIA GeForce GTX 850M (385.28 (22.21.13.8528))
Looks like the transition to libc++ should be viable, at least for my build purposes. :)
I had no time to reset flag, next version i will clean installation and will report back. And no, I do not supply my own API keys, Ive see that message for the first time.
Thank you!
About the second part, I did a very quick run through some flags. It could be one of these crashing the page loads:
chrome://flags/#enable-resource-prefetch
chrome://flags/#enable-nostate-prefetch
Try resetting one or both to default assuming you have them configured.
Btw, a less important note, your github says 32bit on the release notes when the build is 64bit for polly. =P
About the random crashing, curious, running any extensions?
----------------
If I had to take a quick guess, I would think maybe an userscript running under Violentmonkey. Consider trying temporarily disabling Violentmonkey via chrome://extensions to test assuming the issue persists.
However, I noticed lags/slowdowns when opening/closing new tabs.
chrome://flags/#enable-fast-unload
----------
I did not realize libc++ was not being properly pulled into my local LLVM repository, so despite my setting the calls in the build config, it is not being used after all. Oh well.
Appears I might have to do libcc++ as a standalone component of LLVM to get it actually working. Something to add to the list. ;)
thanks for the continued great work with your super-speedy-builds, I appreciate it! I am having a odd issue since a while though, I am getting no sound on just SOME YouTube videos, for example this one:
https://www.youtube.com/watch?v=Lu1180bxts4
Picture is fine, but no sound, just complete silence.
However, this video for example (without restarting Chrome or whatever), the sound is just fine:
https://www.youtube.com/watch?v=yILwIrIziaI
Do you know why this might happen?
Thank you,
Lorenz
Control Panel > Hardware and Sound > Sound > Playback tab > Right-click the default device and hit 'configure speakers' > changing it from "7.1" to "Stereo"
I went ahead with pushing out an internal build to public. I was testing compiler optimizations on file sizes versus performance, so it is not my usual public build, but it might help with anon2877' issues if revision related. I will get a more typical public build cooking in a day or two.
@Lorenz Glad to see ya' fixed it. :)
IIRC this started to happen with v65 of Chromium. I've been using Rob's builds, everyone he releases (Experimental, Polly, etc) and some work fine while others won't.
I hope it's a revision thing. 2018...anything with the word "speculative" tends to go to the dogs =.=
@Anon2883 Similar thoughts. I had to set the to default as well starting a few revisions ago.
- https://www.hackread.com/37k-chrome-users-downloaded-fake-adblock-plus-extension/
- https://www.icebrg.io/blog/malicious-chrome-extensions-enable-criminals-to-impact-over-half-a-million-users-and-global-businesses
The GPU process hung. Terminating after 15000 ms.
GpuProcessHostUIShim: The GPU process crashed!
What GPU does the system have? Running the latest drivers?
https://wiki.debian.org/Chromium
Alternatively, I suspect the #ubuntu build probably could work on Debian as well.
Chromium 65.0.3324.0 (Official Build) (Windows 64-bit) - No Sync | No WebRTC | No Widevine
Revision 868062045852303b6536137c48eb2ca1c55d4119-refs/heads/master@{#529752}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
chrome.zip :
Is not ➜ v65.0.3324.0-r529752-win64
But you mistakenly packed the Clang version ➜ v65.0.3323.0-r529363-win64 ( 970eec130315d91b6013ab8bb38fbac0af572cf2-refs/heads/master@{#529363} )
Thank Rob !
Chromium No sync • No WebRTC • No Widevine • 65.0.3315.0 (527543) 32-bit by Nik
Since now want always download, my AV block it and said trojan.
What is this and what can i do ?
[EDIT: Dangerous link removed by Jerry - 22 January 2018]
It's because of a filter in uBlock origin.
Just delete it.
The GPU process hung. Terminating after 15000 ms.
GpuProcessHostUIShim: The GPU process crashed!
[1412:7376:0121/004741.224:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(47,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(51,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:7544:0121/004741.231:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(46,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(50,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:7376:0121/004741.240:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(46,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(50,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:7376:0121/004741.250:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(50,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(54,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:7544:0121/004742.182:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(29,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(33,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:7544:0121/004743.065:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(65,10-34): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(87,10-34): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[1412:7544:0121/004755.447:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(56,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(60,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
[1412:4744:0121/004949.750:ERROR:mf_helpers.cc(14)] : Error in dxva_video_decode_accelerator_win.cc on line 1608
[1412:4744:0121/004949.750:ERROR:mf_helpers.cc(14)] : Error in dxva_video_decode_accelerator_win.cc on line 715
[1412:4744:0121/004949.750:ERROR:gpu_video_decode_accelerator.cc(369)] : HW video decode not available for profile vp8
[1412:7544:0121/004949.790:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(57,8-56): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(61,8-26): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
BTW, while on the topic, my current ThinLTO build can apparently return a WebGL warning in about:gpu as well, though it does not crash the GPU process so disregard as an annoyance IMO.
What happens if manually disabling hardware video decoding?
chrome://flags/#disable-accelerated-video-decode
Thank you for No sync • No WebRTC • No Widevine • 66.0.3326.0 (530613) 32 bit.
Works very well !
Chromium 66.0.3330.0 (Official Build) (Windows 32-bit) - No Sync | No WebRTC | No Widevine
Revision fdf9afc3bc7becbc37863b9f516c1b7fbfd00de6-refs/heads/master@{#531327}
Compiler clang (+lld_linker +thinlto +compiler_optimizations)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v66.0.3330.0-r531327-win32
I'll install your 3330 build and see if that fixes it... If not, then Chromium broke hardware rasterization again on older cards.
Impressive.And works at a very high speed. Works well without problems.
Thank You.
Scrolling down a little on the page, I get this:
"2. Stable Chromium version
In fact, Chromium has a stable version. ^^
Example: The current stable version on #linux is 63.0.3239.132."
Note: 63.0.3239.132. is the latest stable version number for Windows as as well.
On the top of the page, you get this:
"1. Chromium for 64-bit Windows only
Reference: Current stable version (Google Chrome): 63.0.3239.132 (508578) • Thursday, 4 Jan 2018
Installer • Archive • Portable"
This implies there is a portable version of the official Woolyss Chromium binary... But I couldn't figure it out how to get the portable version from the link in the top section of the page (1. Chromium for 64-bit Windows only/Reference: Current stable version (Google Chrome): 63.0.3239.132 (508578) • Thursday, 4 Jan 2018/Installer • Archive • Portable)
However, scrolling a little down on the page, there is another portable version:
"Portable
No sync • WebRTC • No Widevine • 65.0.3303.0 • Monday, 25 Dec 2017
Packaged in the PortableApps.com format by Versatile Apps, it can work as standalone software."
As you can see, this is not the latest official stable version as it is mentioned multiple times on the page (63.0.3239.132.), but a different one (65.0.3303.0). It also isn't a Woolyss project; it's just a link to an outside project.
To sum it up:
The whole https://chromium.woolyss.com/ page is not quite self-explanatory from a user experience standpoint.
Which is the latest stable portable Chromium version for Windows (63.0.3239.132.) most recommended by the Woolyss project and which of the so many links on the whole page should I click to get it?
Maybe the discussion would benefit from installing a free, lightweight forum engine, such as Discourse. You be the judge if this comment section with almost 3000 comments is the way to go, or, perhaps there are better options.
There are various builders, and some builds could be behind project development. I suggest simply using Nik's latest stable build if wanting the closest approximation here to the current Chrome public release. There is a portable version of Nik's build, too.
With 4 tab opened. no extensions. used 78% of my 3Go RAM available in my OS 32 ; 1Go is for the system.
Stay only 570Mo
It's too bad. Your release uses too RAM in 32bit. For use like we want.
For CPU is great works without any problem Intel 4 core 2.7 GHz. use less cpu.
Thank You.
----------------
@Anon2915 I probably can help you. I usually build the code for performance, but it appears I am going to need to take code size into consideration for 32-bit builds as well.
I will work on getting a new build out. In the meantime, you might also want to try automatic tab discarding to possibly help with memory usage.
chrome://flags/#automatic-tab-discarding
Thank you.
With this flag enable ; works perfect for my ressource. ( I win use of 750MB less of Ram )
Use the same RAM of Build Nik : No sync • No WebRTC • No Widevine • 66.0.3326.0 (530613)
:-)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v66.0.3331.0-r531775-win32
Perfect with updated build.
chrome://flags/#automatic-tab-discarding set default.
I keep the economy of 750/800MB of RAM.
With no loose performance. The build stay very fast.
Can use for daily use.
Great.
Thank You.
:-))
Curiously for me, except for graphics benchmark MotionMark and Speedometer, the Clang (3330 x64) version seems more powerful than the Polly (3331 x64) version.
But hey, it would actually need to do several benchmarks to be sure (I only make one test of each)...
I need to re-check Peacekeeper : the difference is too large to be correct…
But as you like to say : YMMV !
And in daily use there is no visible difference. At least, for me…
I will compare your last Clang with last Nik version 3326 especially for html5/codecs capacity.
—————————————————————
Windows 8.1 x64
Intel Core i7 4710HQ @ 2.50GHz - DDR3
Intel HD Graphics 4600 (10.18.14.4578) + 2Go NVIDIA GeForce GTX 850M (385.28 (22.21.13.8528))
—————————————————————
Clang 3330
---------------------
✔️ Octane 2.0 ➜ 32972
✖️ MotionMark 1.0 ➜ 229.98 ±34.11%
✔️ Basemark Web 3.0 ➜ 607.47
✖️ Speedometer 1.0 ➜ 164.7 ±0.88
✖️ Speedometer 2.0 ➜ 85.5 ±1.5
✔️ JetStream 1.1 ➜ 164.31 ±2.3185
✔️ ARES-6 ➜ 27.63 ±0.79ms (because lower better)
✔️ SunSpider 1.0.2 ➜ 268.6ms ±2.1% (because lower better)
✔️ Dromaeo (v8) ➜ 1567.62 runs/s
✔️ Peacekeeper ➜ 5213
✔️ Kraken JavaScript Benchmark (version 1.1) ➜ 1268.1ms ±0.7% (because lower better)
—————————————————————
Polly 3331
---------------------
✖️ Octane 2.0 ➜ 32455
✔️ MotionMark 1.0 ➜ 389.66 ±2.92%
✖️ Basemark Web 3.0 ➜ 563.27
✔️ Speedometer 1.0 ➜ 147 ±17 (because lower better)
✔️ Speedometer 2.0 ➜ 85.3 ±1.2 (because lower better)
✖️ JetStream 1.1 ➜ 159.45 ±6.0741
✖️ ARES-6 ➜ 27.89 ±0.42ms
✖️ SunSpider 1.0.2 ➜ 277.8ms ±2.8%
✖️ Dromaeo (v8) ➜ 1540.58 runs/s
✖️ Peacekeeper ➜ 2627
✖️ Kraken JavaScript Benchmark (version 1.1) ➜ 1301.1ms ±0.8%
—————————————————————
Note Polly also optimizes various components rarely, if ever tested by benchmarks, like ffmpeg, vp8/9, ssl, etc. That is why some comment Polly feels "faster" or "smoother" depending upon the type of sites being visited.
Am I wrong or are all updaters based on the portable version?
If I want to update an installed version do you have to keep coming back to the website to check for updates.
As far as I can see chocolateley updater is for the sync version.
Thanks for No sync • No WebRTC • No Widevine • 64.0.3282.119 (520840) • Friday, 26 Jan 2018
Much appreciated for your time and effort :)
I'd like to share a trick I had a hard time finding — I suppose most of you know it but as I couldn't find it anywhere, and actually found it by myself ditching one file after the other in a profile, it might be useful to someone... ;-)
So here it is: I wanted to downgrade from Marmaduke's former 65 lkcr to current 64 stable, all was working quite fine except I had 3 warning windows every time I launched Chromium. I just had to ditch the file named "Web Data" inside the profile! :-)
I haven't found anything missing or acting strangely after that... Is there anything that could be affected by ditching that file?
Thanks for No sync • No WebRTC • No Widevine • 64.0.3282.119 (520840) 32bit.
And thank you very much for keeping us always updated.
Your Chromium 66.0.3330.0 (Official Build) (Windows 32-bit) - No Sync | No WebRTC | No Widevine ; is a one shot ?
Or you will do new releases ?
Thank You. Best Regards
I build lkcr (dev) with a custom clang compiler and Polly optimisation: which works OK on my system. Would you be a bit more specific with your problem.
I seldom receive feedback on my builds so I take it for granted that people are satisfied with them. On my subsequent dev builds, I'm going to drop support for OSX 10.9.x: I will be building with SDK 10.13 (and probably drop Polly.)
I had no issue with your builds (except once with Facebook, if you remember ;-) ) and generally put a comment here after trying them for a few days.
As you recently seemed to add a stable channel to the lkcr, I thought it might be better for me to downgrade from your lkcr channel to the stable one — not because of a particular issue, "just in case"... :-)
So the 3 warning windows I had then, every time I launched Chromium, had nothing to do with your build, they just say "your profile comes from a newer version, it might not work properly", I forgot to specify that, indeed.
Many thanks for your great work, I'd probably use Chromium a lot less without your builds!
Great! :-)
@Anon2940: It is CLANG. Thank you for your report.
@user_: No. You cannot compile chromium with old settings, material design.
@Mumu: Thank you for your benchmark! ;)
@Blue: I understand this page is not easy for a new Chromium user. There is a lot of info. However, I hope it is easier than the official website. Sure, I need to improve it. It is an "all-in-one" page because it is easier for me to maintain it and check its dead links. There will never be third-party discussions engine like Discourse or Disqus on this site. I like the system of anonymous comments, managed by myself. Currently, I test asynchronous requests for the comments and another site design for a better user-experience.
A special thanks to each developer, mainly to Nik, RobRich, Marmaduke and Henry++. These guys compile Chromium (or updater) for us freely on their spare time.
I have android 7.0 nougat on Samsung galaxy s8+ and the latest chromium but i have an issue where my chromium browser shows red flashing rectangle around my browser window. Why this is happening? I didn't change a single setting.
"Did you check with a new Chromium version? Which dev version? official? Which OS?"
As I said: Windows. I downloaded also current version 64.0.3282.119 from your site but downloads are still failing because clients4.google.com is still accessed. And there is no setting to disable the Google access.
"What happens if you try to access https://clients4.google.com/chrome-sync/time from your browser?"
What you would expect if something is blocked by a firewall: clients4.google.com refused to connect. ;-)
I've noticed a little glitch when you're in fullscreen mode on Youtube (with both stable and lkcr): each time you move the mouse to the top-end, the menu bar appears briefly - which is not the case with Firefox. ;-)
I'm on MacOS 10.9.5.
Firefox has been going down-hill as late, so one should not expect such cutting-edge functionality.
Works as designed!
I'm sorry I have to contradict you: at least on my OS version, on any video in fullscreen mode (not only Youtube), the menu appears for say 1/10s when you move the mouse/cursor at the top of the screen and then disappears — and it doesn't come back until you move the mouse again in the same way.
I've checked with a clean profile, I'll try to check on a clean session to see if anything else interacts.
Maverick is usupported (by Apple) as of September 2016, iTunes ended in August 2017.
Guessing, I would say the problem is a graphics driver|overlay issue; or at worst an SDK regression issue: which means that the problem cannot be resolved.
I'm using High Sierra 10.13.3 and my only issue with Youtube is the inability to navigate the play-bar bar with the mouse: have to use the cursor keys.
chrome://extensions -> Load unpacked extensions...
No, I haven't tried Chrome.
As you can imagine, I'm still using Mavericks because I've got a bunch of indispensable applications that won't run in 10.10+ (namely Avid Pro Tools 10, which would cost an eye to update).
Thanks anyway.
I've just tried Chrome on another drive with a rather clean OS 10.9.5 and it has more or less the same issue.
So your builds have nothing to do with it, indeed. Sorry for the trouble.
Link: https://www.wilderssecurity.com/threads/chromium-privacy-focused-builds.389051/page-10#post-2735678
WOW! simply awesome
whats the difference from adjusting in chrome:flags ?
be interested in your preferred policy changes (if you are willing to share here when you have your completed policy list)
TIA :)
Is it safety to download and use Chromium from this site? (sourceforge) I mean could be in this Chromium any scam spyware or keyloggers? How I can control that?
Sorry if my words too rude
many has been using from here for years :)
you can always download and scan file on your AV
and then again online at virustotal.com to double check
The stable (sync) version is actually; sync, webrtc and widevine. I've tested generic Widevine and it works. I'm unable to test if Netflix works.
On the Dev version Widevine is not a priority.
Thanks for No sync • No WebRTC • No Widevine • 64.0.3282.140 (520840) • Sunday, 4 Feb 2018 - 64bit
So far ALL good :) Much appreciated for your time and effort
chrome://settings/searchEngines
ADD...
Search engine: anynameyoulike (- set as default)
Keyword: null
Query URL: http://%s
Remove the other search engines (Right click)
Thank you for help.
But don't work.
Chromium continued to add serch engine in " Other search engines "
The only solution I find far away is an extension : https://chrome.google.com/webstore/detail/dont-add-custom-search-en/dnodlcololidkjgbpeoleabmkocdhacc
But I’m looking for something better like a flag…
Thank you.
For the link ( bugs ) and the extension.
But this extension ; does not work anymore.
"Please let me know how to take it off; it does not show in my control panel;
thanking you in advance;
if you are on Windows - GOTO C:\Users\XXX\AppData\Local
delete the folder chromium and ALL is gone
you can clean install again if you wish
If you have a registry cleaner - maybe you want to use that too but should not affect new install
in fact you can install over with higher version straight up
and keep all your same configurations/settings/profile (unless some new thing is added on the new build)
Thank you for
Sync • WebRTC • Widevine • 66.0.3343.0 (534979)
No sync • No WebRTC • No Widevine • 66.0.3343.0 (534979)
32 Bit :)
Revision 388ba4fcfc02afe84dccc6e3f16ba409371036eb-refs/heads/master@{#535983}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
v66.0.3345.0-r535983-win64
Your Chromium 66.0.3330.0 (Official Build) (Windows 32-bit) - No Sync | No WebRTC | No Widevine ; is a one shot ?
Or you will do others releases ?
Thank You. Best Regards
Doesn't look good in VT (I just checked, now it has 8 detections* instead of 7 shown on screenshot in forum post). On side note, 32-bit builds usually get more flags than 64-bit, no idea why.
* https://www.virustotal.com/#/file/b606a577b19a648e6243f3aae9bf8f5c87f6beff02343c1eacfdd9c5b880e1ec/detection
ALL GOOD
Thanks nik for your time and effort Much appreciate :)
Thanks Jerry
Happy chinese new year to all :)
Thank You For:
Sync • WebRTC • Widevine • 64.0.3282.168 (520840)
No sync • No WebRTC • No Widevine • 64.0.3282.168 (520840)
32bit :)
@Anon2978: Welcome.
----------------
Just pushed an updated ThinLTO build. Did some optimization changes. Peacekeeper and Basemark Web 3.0 should be back to decent numbers, as tested on my Intel Kaby Lake system even with the Intel 1/8/18 microcode and Windows patches for Meltdown and Spectre applied.
Revision 91ce9aa2ca57beed6cb1f819438d483688f22c85-refs/heads/master@{#537010}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
v66.0.3349.0-r537010-win64
Ok Many thanks
I will wait with hope ;)
No sync • No WebRTC • No Widevine • 64.0.3282.168 seems perfect, so far.
Right now, Nik's stable 32bit nosync 64.0.3282.140 installer has gained another VT flag, from 8 to 9 detections total (AegisLab, Avast, AVG, Avira, CAT-QuickHeal, McAfee-GW-Edition, Qihoo-360, Symantec, Webroot)
Current stable version 64.0.3282.168, 32bit nosync installer: 4/67 detections https://www.virustotal.com/#/file/b5728c60513b021c62329bf68748d3ce5ca2c374c577626df49145f42d552cc7/detection
Same version, 64bit installer: 0/66 detections https://www.virustotal.com/#/file/9e625b3040cc918e779ff4b65e18c2ec1de7739622cc2f76afec3eb905a20372/details
It means the packer for EXE version is detected by few antivirus as a malware but I think it is a false positive.
Preferably the installer version, not archive or portable.
- https://github.com/henrypp/chromium/tags?after=v56.0.2924.87-r433059-win32 (sync? win64? yes)
- https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/ (sync? maybe. Revisions near 403382)
----------------
Updated Polly build available. There have been some recent updates to Polly, ISL, etc. in LLVM. I did a few checks, and I was able to implement a standardized Polly configuration.
Chromium 66.0.3351.0 (Official Build) (Windows 64-bit) - No Sync | No WebRTC | No Widevine
Revision 0fe5265959e1da13c1521fd7f5f6275a3b83c614-refs/heads/master@{#538181}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
v66.0.3351.0-r538181-win64
@Dan: 64 or 32-bit? Read #comment-2989
Following up about migrating to the standardized Polly config, I have found keeping Polly conservative works nicely for my purposes in casual usability and benchmark testing. I have considered moving my standard Clang builds to Polly, but FullLTO can take a long time to link since it is not multi-threaded like ThinLTO. Ideally, maybe ThinLTO eventually will support autovec and Polly some day.
Thanks for the comment look up. I just turned off my antivirus to install and it seemed to work. Am still getting that the author couldn't be verified though. 63 stable never gave me that error. Thanks again.
Sync • No WebRTC • No Widevine • 64.0.3282.168 (520840) • Wednesday, 14 Feb 2018
OS X 10.11.4
I have set this option:
Menu → Settings → Advanced → Privacy & Security → Content Settings → Cookies → Uncheck Keep local data only until you quit your browser
But still, each time Chromium restarts I have to login everywhere again, it won't remember any sessions, especially annoying with youtube and vimeo as they the cookie that unsets "autoplay video" is missing once again.
Here is also a recent bug report on stack overflow for Chrome:
https://superuser.com/questions/1290531/chrome-keeps-locking-me-out-of-accounts
I am currently working on the engine to improve that.
Chromium 66.0.3354.0 r538832 (Official Build) (Windows 64-bit) - No Sync | No WebRTC | No Widevine
Compiler MSVC 2017 (PGO +compiler_optimizations)
I am not returning to actively doing VS2017 PGO builds, especially since the Chromium project has migrated to Clang/LLVM anyway. I was more or less just testing recent Visual Studio updates and the current environment config on my build box.
No sync • No WebRTC • No Widevine • 64.0.3282.186 (520840) • Saturday, 24 Feb 2018 - 64bit
so far ALL good :)
Thanks Jerry - This site and all is already great still look forward to greater 'engine' for greater improvements
admire your selfless and free service to us :)
hv a gd wkend ppl
The chrlauncher opens, but no download. Clicking on Download update does nothing.
@RobRich: Thank you crazy dev! :)
@Anon3008: Big thx. gd wd 4 u 2 ;)
@Rudolph: Exactly. Thx. I opened an issue at https://github.com/henrypp/chrlauncher/issues/95 and contacted directly Henry++
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
Chromium 66.0.3356.0 r539049 (Official Build) (Windows 32-bit) - No Sync | No WebRTC | No Widevine
Compiler clang (+lld_linker +thinlto +npm)
Given the circumstances, a "point" stable release is not worth the effort.
If have trouble later. I post here.
Best Regards.
(pardon my French humour... :-D)
ThinLTO is the more mature of the two, and it should be somewhat closer to where Chrom(e/ium) appears to be heading on Windows - well, likely minus some of the compiler tweaks and probably the ThinLTO optimization level I am using since they increase the output code size.
Polly builds represent a personal "pet project" of mine. Polly builds might not always return the absolute highest benchmark results compared to my ThinLTO releases, but Polly also optimizes many browser components not typically benchmarked like a/v formats, encryption, etc. Sometimes it is more about the overall performance experience than specific benchmark numbers. ;)
Chromium for 64-bit Windows - All Codecs (inc. AC3/AAC Digital Surround) - Saturday, 03 March 2018
Chromium 67.0.3361.0 r540739 (Official Build) (Windows 64-bit)
No Sync - No WebRTC - No Widevine
(No desktop capture: use cursor keys to navigate Youtube)
I recently rolled a Polly build that took edits to multiple build and source files to disable WebRTC without (hopefully) breaking anything else, and after my build box just attempted rolling a fresh Polly build, disabling WebRTC already is broken yet again with probably even more edits now needed.
I can either continue with the WebRTC headaches and *eventually lose interest in building Chromium altogether*, or I can mitigate the situation and come to the realization that the 'enable_webrtc = false' build argument apparently is either exceedingly low priority or potentially too broken to resolve. Hopefully I am wrong and it will be fixed someday.
I simply installed the WebRTC Leak Prevent extension in the meantime. Set the extension's policy to 'Disable non-proxied UDP (force proxy)' to disable WebRTC IP reporting for most users. Verify IP blocking is working via the various WebRTC leak check sites.
On to a more positive topic, I am currently revisiting compiler optimizations while awaiting a link time optimization (LTO) fix. I suppose there is a chance I might find another percent or few of performance at the compiler stage. :)
Before I forget, a link to the WebRTC Leak Prevent extension I mentioned.
https://chrome.google.com/webstore/detail/webrtc-leak-prevent/eiadekoaikejlgdbkbdfeijglgfdalml?hl=en
Quick benchmark FYI. Futuremark is discontinuing Peacekeeper on March 16, 2018.
https://peacekeeper.futuremark.com/
I will call this a "baseline" Polly build. It is my usual Polly build config minus FullLTO for now due to the LTO situation. Next up is revisiting the compiler optimizations. I am starting at a sub-800 score in Basemark Web 3.0 on my usual test system. Could be a fun challenge.
For a Widevine bonus, Netflix even works for a pleasant change. If anyone does not want Widevine for some reason, just delete the WidevineCdm directory. ;)
Chromium 67.0.3361.0 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | Widevine Enabled
Revision 2eb7677b864fceb47375fff31d026bfa532e7872-refs/heads/master@{#540766}
Compiler clang (+lld_linker +polly +compiler_optimizations)
chrome.zip | sha1: c9f2f122bf25fb75ecc3e9f573216b148f48fa4f
https://drive.google.com/open?id=1MgaQPEgWyzBftw8mNczAFwDE30hA3iNt
mini_installer.exe | sha1: a237212bc05302324fb87a7a76bc76dc6f0aa838
https://drive.google.com/open?id=1tnn2dr6AKHDzubqtH0cFbxE9uACZorxM
Your Polly version 67.0.3361.0-540748-win64 is broken here… After a few second it totally close without any warning…
But don’t touch anything, I need to investigate to be sure the problem don’t come from me or Chromium itself.
Anyway, I will try your Polly 67.0.3361.0-540766.
I don’t have time to make benchmark because you update versions more quickly than I benchs !! Impressive you geek !
For the f**king WebRTC note that my ad-blocker « uBlock₀ » can disabled it : https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address
But everything is in this page thank to Jerry ! I quote him in chapter’s « 6. Extensions »
« uBlock Origin is pattern-based filtering, while uMatrix is matrix-based filtering which gives you more control over the filtering process. You can add filters to your ad-blocker via FilterLists »
Please folk, it’s 2018 !!
It is totally unacceptable nowaday to still be on Adblock or Adblock Plus !
https://en.wikipedia.org/wiki/Adblock_Plus#Controversy_over_ad_filtering_and_ad_whitelisting
There is a 100 times more effective ads’n’tracks blocker developed by a disinterested autistic bro totally honest impartial and incorruptible !
https://github.com/gorhill/uBlock/releases
And it will make life easier to Rob if you switch because he will not have to fight with the WebRTC bug anymore !
----------------
To the compiler tweaks, seems I did not start quite at true baseline. I was half asleep when poking at the code earlier. ;p Anyway, already over 800 with an internal test build, and there should be room for a little more. Hope to have an updated Polly build ready to push later today.
I also hope that the build argument gets fixed. Otherwise, it's just stupid to have it there anyways...
Thanks Rob for your continued hard work!
I have got problem with the two last Polly chromium 67 Rob’s version. I’m investigating…
But everything is fine with your 67.0.3362.0-540770.
Thank you and please never abandons us 💋 !
-------------------
ERRATUM !
I Got the problem of instant close without warning with Nik’s version and Official’s version too. Your ok Rob, my problem don’t come from your optimizations but from my system or Chromium 67…
It seems to be again the problem when I run Chromium from a ramDisk… I already got the problem few months ago with version 62.0.3186.0 …
If anyone can run a portable version (Henry++) of the last Nik or Rob chromium fully in a ramdisk (bin & profile) to confirm…
On my side, I will try in Win 7 VM before filling a bug…
Sync is actually there. I just do not supply Google API keys for it to work. Jerry has a section further up the page on how to obtain and use you own API keys to enable Sync if desired. :)
Just checked, and my latest build crashed out overnight. Probably from using jumbo to build. Just restarted without it. Should have a fresh build today.
-------------------
After a few more changes, I now have an updated Polly build available. LTO still disabled. The build appears stable, plus Netflix works.
I might can squeeze a little more out of the compiler optimizations, but it is coming down to like 1-2% either way with most changes. I am running standard Polly on most optimized code targets, but I am leaning heavily on a customized Polly configuration for the hottest code targets.
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-delicm-max-ops=200000000",
"-mllvm", "-polly-dependences-computeout=100000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-num-threads=32",
"-mllvm", "-polly-optree-max-ops=200000000",
"-mllvm", "-polly-opt-max-constant-term=-1",
"-mllvm", "-polly-opt-max-coefficient=-1",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-vectorizer=stripmine",
"-mllvm", "-polly-prevect-width=16",
"-mllvm", "-polly-run-dce",
Chromium 67.0.3362.0 r540770 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | Widevine Enabled
Compiler clang (+lld_linker +polly +newgvn + partial_inlining +compiler_optimizations)
I grabbed this version: wpo cfg all-codecs lkcr 64-bit windows - Archive - Sync - WebRTC - Widevine - 67.0.3362.0 (540770)
and unpacked it into %LOCALAPPDATA%\Google\chromium. It uses the default chromium profile folder (%LOCALAPPDATA%\Chromium\User Data - see https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md).
The last session was restored but all content in the browser windows was messed up. I could see/read the triple dot menu (and interact with it), the tab titles, and bookmarks, but the browser windows were messed up. I could even copy text from a page (even though I couldn't see any text).
I closed chromium, renamed the profile directory, and relaunched. It was a new profile but it also mis-rendered. Trying to follow Google's instructions (https://www.chromium.org/developers/creating-and-using-profiles) to launch with a different profile didn't seem to work - Windows 7 would just strip off the original target (pointing to chrome.exe) and leave behind the path I input for the profile. However, when I used --user-data-dir=temp_dir it created a new folder underneath chrome.exe's folder and chromium launched with no issues. Copying the old profile folder to underneath the temp_dir resulted in no issues.
After poking around a bit, I realized I'd set flags for my day-to-day (messed up) profile that wouldn't have been copied to the temp_dir because they're above the Default directory. I added one flag at a time and relaunched chromium until I hit the culprit: --enable-zero-copy.
Editing the Local State and removing that from the original profile cleared everything up. Couldn't find an issue reported with this, so I was wondering if you'd seen this behavior and whether you think it could be triggered by a compile or optimization instead of a change in chromium source.
Can someone share a good method for creating shortcuts to alternate profiles that are not sitting underneath chrome.exe's folder? Perhaps using a relative path adding -- "%1" at the end?
- v67.0.3362.0-r540770-update1-win64 est 5.81% better than v67.0.3362.0-r540770-win64 in Basemark Web 3.0
and
- v67.0.3362.0-r540770-update1-win64 is 6.78% better than v67.0.3362.0-r540770-win64 in Basemark Web 3.0
@Anon3048 & Rob : Everything work fine on SSD or RamDisk since I simply made a totally new profile and import every options, bookmarks, extensions…
So I will stay on v67.0.3362.0-r540770-update1-win64 for the moment : my best overall score since chrome 42…
I do not thank you Rob ! I caught the benchmarks race bug from you !
----------------
No probs to note with a SSD here, either. I run Chomium on a 32GB Optane drive for my notebook. I have a NTFS symbolic link between the original install directory and a a directory the SSD so I can use the mini installer.
----------------
FYI. Benchmarks might move around a little in the next few releases. I am still tweaking Polly and targeted optimization levels.
I also have been experimenting with register allocation and machine instruction scheduling again, though I am not sure if the effort is worth the return. Find a couple of percent in one component, and lose a couple of percent in another component. lol I am not going to start down the slippery slope of actual component-level tuning, except for maybe something truly significant like V8 if there is a substantial return.
----------------
Hopefully LTO will be resolved soon. My bug report for LTO has been noted by project devs.
----------------
ThinLTO is back online. :) I will try to get a public build pushed on Wednesday.
With a brand new profile, 9 extensions only, options and favorites imported and the binary v67.0.3362.0-r540770-update1-win64 and everything in RamDisk my Chromium in real-world usage is exceptionally responsiveness !
Animations, Ajax, JS ... Everything is instantaneous ! And as I spend 80% of my PC time on a browser, it's really nice ...
————————————
Windows 8.1 x64
Intel Core i7 4710HQ @ 2.50GHz - DDR3
Intel HD Graphics 4600 (10.18.14.4889) + 2Go NVIDIA GeForce GTX 850M (390.77 (23.21.13.9077))
Rob / Polly / v67.0.3362.0-r540770-update1-win64
————————————
----------------
I just pushed a fresh ThinLTO build. :) It should appear soon.
WebRTC is enabled as per previous comments. Widevine is disabled as it was breaking the build process. Anyway.
I carried over various recent compiler tweaks, set all optimized code targets to -03, pushed inline expansion for the hottest code targets, etc. I have a couple of more ideas for future ThinLTO builds, too.
Basemark Web 3.0 scored 882.5 on my test system.
[Extended notes: FullLTO is disabled for this build due to a related build error.]
From your last build ;)
I got the problem regardless of ramdisk or ssd too.
I solved the problem by create a totaly brand new profile and copy / import chromium settings, favorites (export / import) et export / import settings from each extension one by one.
As far as now I got no more crashes.
So it seem the problem come from incomptibility between old profile (63, 64, 65, 66) and new binary (67)…
----------------
The build is stable on a couple of different systems here. I will keep a lookout for issues, though.
Like Mumu found, I am kind of wondering if there is a not a slight profile difference in recent revisions.
My build box is doing some ThinLTO stuff right now. Still chasing 900 in Basemark Web 3.0 on my test system. ;)
I will revisit the Polly config later today and maybe push a fresh build tonight or tomorrow.
I wonder... while we're waiting for v65 stable on Mac, can we consider the lkcr builds Marmaduke made 2 months ago as stable? (namely v65.0.3310.0-r526469)
---------------------
Here it is! :-D
Thank you Marmaduke!
I crashed Saturday. Going to take a look at Polly today, so probably will push a public build tonight.
Chromium 67.0.3369.0 r542403 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | Widevine Enabled
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
Little mistake,
chrome.zip (103 MB) in Polly 67.0.3369.0-r542403-win64 is the wrong chrome.zip : you pasted the Clang chrome.zip (67.0.3366.0-r541999-win64)
@Anon3072 : fisrt for 10 seconds ! ;) :D
---------------------
Updated Chromium build with Polly optimizations available.
Chromium 67.0.3369.0 r542442 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | Widevine Enabled
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
I cleaned up the Polly config, and it probably is where it is going to be for awhile.
Like usual, it is not likely to outright win benchmarks compared to ThinLTO, but it certainly feels fast IMO.
- PGO builds are discontinued. I will delete the API link, ASAP.
- RobRich said to me that he is not sure how long the project even intends to continue supporting
Visual Studio builds. Next step in getting away from VS probably is migrating to libc++.
https://bugs.chromium.org/p/chromium/issues/detail?id=801780
Thank you RobRich for info...and your all work! ;)
- I see an issue with my comment system. Thanks for report @Mumu.
Being realistic it does not even always compile. I need to verify the issue persists, but I have a bug report submitted on Widevine compilation errors right now.
Chromium 67.0.3370.0 r542992 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | Widevine Enabled
Compiler clang (+lld_linker +libc++ +polly +fulllto +compiler_optimizations)
I try to keep a relatively even playing field since I deal with so many builds and revisions. The prominent flag I typically set is to disable v-sync for performance benchmarking as most of my displays are refresh limited to 60-75Hz.
It is not performance related, but strict site isolation is a potential mitigation enhancement for the recent meltdown and spectre attack vectors since each site's code would be limited to its own render process.
Of recent additions to flags, there is the new viz display compositor, though I have yet to evaluate its performance.
Thanks for the 67.0.3366.0 build
working well for me
I am working on a new ThinLTO build right now. I am incorporating the open source libc++ library since the latest Polly build confirms it works, plus I am attempting to tryout additional LTO optimizations recently added in LLVM.
but I have to say it again...
Please check your Chromium 67.0.3373.0 Clang build. It's like a 67.0.3370.0 Polly build.
Not sure on the Spotify issue. I can say if you need Widevine support, Nic's stable build probably is the best place to start.
Widevine with dev builds can be a "hit or miss" proposition. Case in point, Widevine is not even currently building with recent checkouts.
Unfortunately, now (probably due to how chrome has screwed around with flash settings. Again.) ytmnd's no longer play sound. Since I can't auto allow flash anymore, I can only add it to the allow list. Still doesn't work.
Maybe someone can replicate an issue I'm having with x86+x64 builds of 65.0.3325.162. The Telegram web app cannot save media (it uses blob urls). While the media is downloaded it seems to not be decrypted(?). Visually it appears to open a new tab which closes immediately. Media saving can sometimes be successful by clicking the download button rapidly. Strange to say this is not an issue with the portable build.
thanks for all these efforts, now even 2 builds that you are doing all the time, crazy! Totally appreciate it!!
Have you tested your latest clang WPO build against the Polly one? Which one is faster in all your tests?
Thank you,
Lorenz
I have not done heavy benchmarking between the two builds in recent times.
Past trends tend to suggest ThinLTO probably does slightly better on most popular benchmarks, while personal usage suggests Polly "feels" as fast or faster in typical everyday scenarios.
I typically use Polly, but I keep building ThinLTO for others since it is the more mature of the two builds. At some point I might transition totally to Polly.
https://forexsb.com/forum/topic/7273/ea-studio-up-to-3x-faster-with-chrome-compared-to-firefox/
Especially have a look at the YouTube video I´ve posted there, absolutely amazing! Thanks so much for all the hard work :-)
@RobRich: your build is very fast and seems to be faster than all web browsers on the market! :) Big thanks.
@RobRich: I can only second what admin said, hope you´ll keep it up forever - big thanks!!
I should be picking up a dual-proc Opteron server this week. Only eight cores total for now, but I got for under $35 with 40GB of memory already installed. :) There is a *chance* I might take a look at an optimized Linux build. If done, it would be for Debian and similar platforms.
Alternatively, if perhaps wanting to launch incognito mode when opening Chromium, you can pass a command-line switch.
Are you using a Multi-stage PGO compiler?
https://llvm.org/docs/AdvancedBuilds.html#multi-stage-pgo
Multi-stage PGO as presented is about optimizing LLVM using profile data from an underlying build. In theory it should speed up LLVM, but as noted, it could take some serious build time to accomplish.
I would like to get PGO working under LLVM for building Chromium, but I can not get the renderer process to generate profile data. Other processes? Yes. The one I need? Not so much. After much frustration, I kind of shelved the idea until if/when the project catches up with it.
is not active anymore), it stops it´s calculations and CPU usage drops to 0. When maximizing the window again, it continues just fine. I see the same behavior with Firefox too. Is this some industry-standard thing? Can it be changed with a hidden setting Chrome possibly? Thanks so much :-)
chrome://flags/#expensive-background-timer-throttling
Do you (or anyone else) know of a way how to use a web-app offline? I am not always online and still would like to use a web-app (I think it is HTML5 or JS, not exactly sure, it´s this one: https://forexsb.com/expert-advisor-studio-app ). Is this somehow possible by "downloading" it or caching it? Have no experience with that... Thanks :-)
I completed the first stage of the PGO compiler build with just one link error on the very last step. I decided to try and rectify the link error the next day. The subsequent day to (my dismay), I realised that I had not saved my build notes. I will try another time.
In fact, it would be nice if Google/Chrome/Chromium would supply a PGO optimized compiler replete with Polly and Sanitizers; thus, saving a lot of grunt work.
https://www.askvg.com/how-to-enable-disable-background-tabs-throttling-feature-in-google-chrome-and-opera-web-browsers/
@Marmaduke Yeah, I know. Chromium's bundled LLVM checkout is nice, but it lacks a few things; noticeably Polly for my purposes.
To be honest I am not sure PGO is going to speed LLVM compile times as much as desired unless you intend to roll multiple builds over an extended period of time with the same revision.
While I have not attempted build LLVM itself with PGO, I have built LLVM with WPO (/GL) in VS2017 a few times, and each time I could not tell much difference when subsequently building Chromium. Admittedly I did not look at the ninja build logs for timestamps, but it certainly did not feel faster by any immediately noticeable difference.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v67.0.3376.0-r544204-win32
Either honour the "enable_webrtc" flag or get rid of it! The illusion of choice is no choice.
Does the right hand know what the left is doing, and are you able to walk and chew gum at the same time?
My suggestion? Install the WebRTC Leak Prevent extension. Set to disable non-proxied UDP. Enable for incognito mode if desired. That should stop WebRTC IP tracking for most users.
Likewise, uBlock Origin also can deal with WebRTC, as noted here by the extension developer awhile back.
Widevine is whole other issue right now. As of my last attempt to build with it enabled, Widevine was returning multiple build errors. I have a bug report filed with the project, though it has yet to garner much attention - perhaps if/w/hen Widevine stable breaks.
https://github.com/andryou/scriptsafe/releases
I've just done a Windows webrtc all-codecs build 67.0.3377.0: hevc and xvid no longer work! I will investigate the issue. But, fear that Chromium is morphing into the mediocrity that is Chrome: if that is the case I suggest that The Chrome Algorithm Simians drop the pretense that Chromium is open-source and concentrate on their proprietary advertising vehicle known as Chrome.
Mozilla might be in the doldrums; but at least they are not smug and complacent.
I use Chromium as my daily browser. No plans to change that here.
1. Download "No sync" portable builds.
2. Launch Chromium without any extension.
3. Test WebRTC IP leak at https://browserleaks.com/webrtc, https://www.privacytools.io/webrtc.html and https://ipleak.net/
Results:
• #win64-stable-nik "No sync" → WebRTC IP leak? no.
• #win64-dev-nik "No sync" → WebRTC IP leak? no.
Works very good! Too bad WebRTC enabled ;)
Chromium for 64-bit Windows - All Codecs (inc. AC3/AAC Digital Surround) - Tuesday, 20 March 2018
Chromium 67.0.3377.0 (Official Build) (64-bit)
Revision faebdb6d4f0f5e6458c9092e223e53d40de12e28-refs/heads/master@{#544331}
OS Windows
No Sync - WebRTC - No Widevine
https://github.com/macchrome/winchrome/releases/tag/v67.0.3377.0-r544331-Win64
SHA1 24033A3381156C9D92EE9A3AAEE94DDDC2FB6813
ps: the 32-bit version is delaying because hdd's is dead due to PSU burnt down, i need to rebuild the system :P
Been using for the last few hours - All good So far - Super Effort!
Thanks nik :)
Thanks Jerry :)
Disable WebWTC
These are my MAC Notes, which I used for Windows:
============================== There is a Windows equivalent (paste outside of conditional)
vi third_party/webrtc/rtc_base/platform_thread_types.h
#elif defined(WEBRTC_POSIX)
typedef pid_t PlatformThreadId;
typedef pthread_t PlatformThreadRef;
#endif
...
typedef pid_t PlatformThreadId;
typedef pthread_t PlatformThreadRef;
=======
vi third_party/webrtc/rtc_base/criticalsection.h == CRITICAL SECTION ==
Line 88: // Fail ON ERROR - COMMENT out
119: // Fail ON ERROR - COMMENT out
======
vi content/renderer/pepper/pepper_media_device_manager.cc
117: base::ThreadTaskRunnerHandle::Get()->PostTask(
COMMENT OUT Function (if required)
==========
webrtc_logging_private *** COMMENT OUT *** Search !!!
vi chrome/browser/extensions/BUILD.gn
vi chrome/common/extensions/api/BUILD.gn
===========
===========
Chromium for 64-bit Windows - All Codecs (inc. AC3/AAC Digital Surround) - Tuesday, 20 March 2018
Chromium 67.0.3377.0 (Official Build) (64-bit)
Revision faebdb6d4f0f5e6458c9092e223e53d40de12e28-refs/heads/master@{#544331}
OS Windows
No Sync - No WebRTC - No Widevine
https://github.com/macchrome/winchrome/releases/tag/v67.0.3377.0-r544331-Win64
SHA1 A3DFE0D6357A98096728FE16EA77719BEAAE0756
Thank to all dev too.
^ Simple: SPEED. RobRich's builds are SO extremely fast compared to the standard dev builds, you won´t believe your benchmarks. Go and try ;-)
----------------
Note to users, I am not likely to go back to disabling WebRTC for public builds. As of last check, one of the the latest developer considerations is perhaps outright removing the "enable_webrtc=" build argument altogether, which likely will further complicate matters if done.
----------------
@Anon3132 Lorenz pretty much covers it. I change the optimization levels for certain build targets, add some advanced compiler register allocation settings, apply ThinLTO link time optimization, etc.
My Polly build, which I post in the comments as an experimental offering, goes even further. I slam the optimization levels across the board due to how the Polly loop and data-locality optimizer works, plus replace ThinLTO with monolithic FullLTO due to needing autovectorization support for Polly.
----------------
I have actually had my build box turned off for awhile, so it has been more than a couple of days for a new build. o.0 Anyway, I will try to push new builds this weekend. :)
----------------
On the Linux front, I received my eBay *$34* 8-way Opteron server with 40GB of memory. Verified it runs Xubuntu out of the box. I am waiting on a correct hard drive caddy, plus I need to modify the failed storage controller battery with a 4.8v NiMH pack to get write back mode working again.
Can just suggest tou you to come back on you decison to not always disable WebRCT in all your build.
WebRCT is usless.
And Nik buid one version with WebRCT for those how need this.
Thank you again.
Best regards.
The implementation of FFMpeg in the Dev version of Chromium has changed; but FFMpeg remains consistent for a particular release cycle. Next stable build I will check the code.
if I stay on the last good-copy of No sync • No WebRTC • No Widevine and NOT UPDATE from then on
would I be free of WebRTC?
WebRTC is useless and constantly breaks the normal flow of system :(
Thanks.
As mentioned previously, uBlock (which is pretty much used universally) has the ability to block webrtc so at least there is options for it. Shouldn't be that big of a deal.
Wow! I'm just waiting for the proverbial to hit the fan when "WebRTC=false" is deprecated. Dangling pointers and such.
Given the inability of the "The Project" to the manage the project. I have about as much confidence in them as Lewis Hamilton has in the Mercedes F1 strategic management team.
Sync • WebRTC • Widevine • 67.0.3369.0 (542742) • Sunday, 25 Mar 2018
https://bugs.chromium.org/p/chromium/issues/detail?id=800653
https://bugs.chromium.org/p/chromium/issues/detail?id=811678
What an abject admission of incompetence and failure.
@Dustyn: i can't check it because i don't use it (and it doesn't have test page without sign in), sorry :\
I kind of expected it, thus part of why I went ahead with enabling WebRTC in my builds.
----------------
ThinLTO will be a little behind schedule. Building with libc++ currently is broken. I suspect it will be resolved soon since it is also breaking a project buildbot. I have a Polly build without libc++ cooking in the meantime.
The occasional 32-bit ThinLTO build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v67.0.3383.0-r546391-win32
Works perfectly !
There is no backdoor or other malware (as far as I know) inside Nik's stable archive (nosync version).
I only used nik's stable nosync for years now
and I always match its SHA and then scan in VT before installing
I have never encounter a problem or even false positive
The false positive from Norton you mention is annoying to say the lease (being a ex-norton user myself)
In Norton, You can GOTO Scan option and choose File Insight
and right click to change the status to Safe if you want (I used to do it everythng I upgrade)
You will see the false positive in on chrome.exe (nothing to do with nik) and others
If you install any other browser-type that uses chrome you get the same false positive.
Anyhow to be sure you can check here
https://www.virustotal.com/#/file/5f3cdfbc334a53c9f3ac936dd72172ab55a202f5d6e46d6e387e10455dd889a4/detection
Hv a gd wkend :)
happy Easter :-) You said:
"RobRich28 Mar 2018, 17:47
Lorenz, there was a JS performance regression for a build or few. Might want to try again just to verify."
And I have just done a big shootout indeed! It´s funny, the fastest version I have tested (by far) for the EA Studio App and how fast it generates trading systems, is "No sync • No WebRTC • No Widevine • 65.0.3325.181 (530369) • Thursday, 22 Mar 2018". Now that came by surprise, but i´ve repeated the test several times and the outcome is the same, it´s about 10% faster than v67.0.3383.0-r546391-win64. However, I´ve also tested Nik´s 3383 build against yours and there are no speed differences (equally fast). So it seems to come down to that the current official Chrome build is faster in terms of Javascript (at least for my usage-scenario) as they possibly might be testing things in V8 in the dev builds that slows things down - what do you think? Big surprise for me, but also a 10% speed-up. Oh and it smoked MS Edge finally too (Nik build of latest stable that is).
Cheeers :-)
I again have been working on LLVM tweaks, and I was able to garner a few hundred more points in Octane 2 on my Opteron build box. Hope it holds or improves with my next public build.
I thought that almost all false positives were triggered by mini_installer's silent install properties. What could be causing them in a zip with nothing but commonly used Chromium components?
Plus, some advice for those who check VT: if there's no detections, but the submission is less than one-two weeks old, it's good to retry the scan after few more days, so the scanning engines would catch up with any possible new threats.
also as Lorenz mention - it seems chromium developers are putting alot more 'interesting' stuff in some of the latest build - better days ahead??? :D
which makes this site, kindly sponsor by Jerry, SO AWESOME
with many great minds gather to share good info and good build for the general user :)
hv a good wkend :)
I was able to increase Octane 2.0 scores by up to a few hundred points on various systems using some advanced LLVM options. Link time optimization is via FullLTO so autovectorization is working as well.
Chromium 67.0.3386.0 (Official Build) (64-bit)
Revisioncc0ee6e2747366c3636bc85a35c3ec22b53c3570-refs/heads/master@{#547374}
Compiler clang (+lld +libc++ +fulllto +compiler_modifications)
chrome.zip | sha1: 764bdcf064d9575b8115613768210d26055764c8
https://drive.google.com/open?id=1uWeCt1M-cSwNvKqRTU7dTM9PiWN06fWv
mini_installer.exe | sha1: 0b2c0243c56ff62894ab35d4e13169056cfa3e29
https://drive.google.com/open?id=1QTiKm8qSnFxkE551IzU04DxkLQc6ToyC
btw #547374 works fine!
wow, thank you for the efforts, so much appreciated! I have just tested it, but "unfortunately" Nik´s "No sync • No WebRTC • No Widevine • 65.0.3325.181 (530369) • Thursday, 22 Mar 2018" still beats it by a good margin. It is even visible by eye that it generates new trading systems faster. After a few minutes, there is already a drift of about 400 more systems (Nik´s = 1900, yours = 1500 after 2 minutes) and it increases over time...
Maybe you should really give the current stable release a try with your compiler tricks, I would be happy to test if Nik´s and your way to compile Chrome 65.0.3325.181 would make a performance difference in my trading app.
Thank you,
Lorenz
- - - - - - - - - - - - -
Windows 8.1 x64
Intel Core i7 4710HQ @ 2.50GHz - DDR3
Intel HD Graphics 4600 (10.18.14.4578) + 2Go NVIDIA GeForce GTX 850M (385.28 (22.21.13.8528))
- - - - - - - - - - - - -
https://chromium.github.io/octane/
https://web.basemark.com/
(x) ➜ Octane 2 ranking…
[y] ➜ BaseWark Web 3.0 ranking…
Clang - 67.0.3383.0 (546391) x64
(4) Octane 2 ➜ 32356
[4] BaseWark Web 3.0 ➜ 520.03
Polly - 67.0.3383.0 (546391) x64
(1) Octane 2 ➜ 33297
[3] BaseWark Web 3.0 ➜ 525.06
Clang - 67.0.3386.0 (547374) x64
(2) Octane 2 ➜ 32658
[1] BaseWark Web 3.0 ➜ 568.45
Nik Stable NoSync - 65.0.3325.181 (530369) x64
(3) Octane 2 ➜ 32592
[2] BaseWark Web 3.0 ➜ 549.59
@Mumu: Appreciate the numbers.
Thank you for new build :
Sync • WebRTC • Widevine • 67.0.3386.0 (547390) • Sunday, 1 Apr 2018
No sync • No WebRTC • No Widevine • 67.0.3386.0 (547390) • Sunday, 1 Apr 2018
Need to confirm : wait for others opinions.
Maybe you are thinking r547374? It is on my Google Drive, posted a few comments back, as it is a FullLTO build without Polly.
My builds currently are delayed somewhat due to a Google login issue. I have not had much chance to look into it, but I did note someone else has filed an error report to which I added my own experience. I hate to push a build with an issue potentially affecting Gmail, YouTube, etc. I am going to run a fresh baseline build shortly to see what happens.
One possible idea to achieve your desired result would be install a portable version, then create a link to the portable version in the "C:\Users\Public\Desktop" directory, which should put a shortcut on all system users' desktops. You might need to enable "Show hidden files, folders, or drives" in folder options to view the directory.
@voidxor As a very long-time user I've always used the archived versions and never had issues setting Chromium as the default system browser that's not to say no one won't, just adding my experience in regards to it.
(I did have issues back on Windows 7 & 8.1 but Windows 10 hasn't given me issues with defaulting Chromium).
I've recently fresh installed Windows 10 Spring Creators Update RTM from a bootable USB onto a formatted SSD and downloaded Robs archive build, extracted and could set it as default browser without having to use the mini_installer.
Screenshot:
Speaking of builds, I have a couple of options. Wait until the Gmail, YouTube, etc. (Google login) issue is fixed, or go ahead with pushing public builds. Clicking back from the error page usually gets around it, but it is annoying nonetheless.
More info:
- https://bugs.chromium.org/p/chromium/issues/detail?id=829220
- https://productforums.google.com/forum/#!topic/gmail/KsMA6hbCy04;context-place=forum/gmail
« Chromium is not supported, only Chrome. They are not identical browsers. »
Chromium 67.0.3393.0 (Official Build) (64-bit)
Revision d12fd0fd1b3e31bc034c6f4b3762c37f2c81fd3a-refs/heads/master@{#549357}
Compiler clang (+lld_linker +libc++ +thinlto +compiler_optimizations)
chrome.zip | sha1: 765543434d1a19fc11e656a6fac5e821e064e4b5
https://drive.google.com/open?id=1GgdazLiWCDGUixY5A0DM80L-6CpeQWCt
mini_installer.exe | sha1: 3a8782884ead7b37e36c137ef47742ea702c3f8f
https://drive.google.com/open?id=1uHsmCF85lZnbuxv3Eisj3bbLkiCBKaE9
If the issue is not resolved soon, I am going to start pushing public builds anyway. It might get fixed if/when a project dev encounters the issue. In the meantime, those encountering the error feel free to post an error report at the the following links.
- https://bugs.chromium.org/p/chromium/issues/detail?id=829220
- https://productforums.google.com/forum/#!topic/gmail/KsMA6hbCy04;context-place=forum/gmail
The indicated browser flag is only related to the Google login system. I have used it today with various Google services and have no issues to note from an usability standpoint. YMMV on a security standpoint, as I have seen no documentation on how Dice works.
"Dice is a new experiment in which Chrome is aware of the accounts in the Google authentication cookies."
https://peter.sh/experiments/chromium-command-line-switches/
Appears to do some client-side account(s) management when logging into Google services.
Thanks @RobRich.
Unless something else changes, I am going to leave it disabled until whatever the underlying issue is resolved, too.
Start Menu -> Settings -> Apps -> Default apps -> Web browser (the only three options are "Microsoft Edge", "Internet Explorer", or "Look for an app in the Store").
I tried going into Chromium's settings too, then Default Browser, and Make Default, but that just opens the same Windows 10 settings screen.
I looked at your screen shot, yet still don't understand why Windows would "see" Chromium if the archive distribution is merely unzipped to a directory on the C: drive (as opposed to installation, which would register it in the Windows registry). Thanks.
Thanks,
Aurora
@Aurora Attard, there have been sporadic reports of false positives from anti-virus vendors for some of the Chromium builds on here (I've gotten them myself from time to time). If you want to be sure, however, I would upload the file to a site like https://www.virustotal.com to see what other anti-virus vendors have to say.
Either way, it probably is a revision issue. I will try to roll another Polly build later today.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v67.0.3395.0-r549950-win32
https://github.com/RobRich999/Chromium_Clang/releases/tag/v67.0.3396.0-r550416-win64
I will start a Polly build in a few. Might be later on Friday before it is posted, though.
About Chromium v49
Is there any way to force the operation of the Windows 2000 SP4 operating system?
@Eden It has been quite a long time, but I think v49 requires various WinXP APIs.
Win2k is going to be a hard case for even a semi-modern browser. Opera 12.x comes to mind. It is well outdated from feature and security standpoints, but IIRC, it still handles most popular websites okay enough for basic use.
LevelDate and TimeSourceEvent IDTask Category
Error4/13/2018 6:11:17 PMHitmanPro.Alert800Anti-Malware"Malware found:
Mal/Zbot-M
C:\Users\X\AppData\Local\Chromium\Application\chrome.exe
Mitigation MalwareBlocked
Platform 10.0.17133/x64 v739 06_9e
PID 8704
Application C:\Users\X\AppData\Local\Chromium\Application\chrome.exe
Description Mal/Zbot-M
SHA256:d9d8e08bb2da4cf7a0521da934aeac15d053cff057d0a5bf40178669457ea621"
Note I had Jerry pull the libc++ tag as building with it is currently broken. I will revisit if/when fixed by the associated devs.
My downloads from there are showing different SHA-1 hashes and 32bit 67.0.3395.0 -549950 revision build
@Anon3221 Sure enough, likely a false positive based upon heuristic scanning. I can not speak for whatever extension(s), but from the core browser perspective, my build box is rather isolated from unknown apps plus gets the usual routine security audits for malware and similar.
Brief FYI of what DICE is.
https://chromium.googlesource.com/chromium/src/+/f422573bdacaed65c521ce713d33377eca9030c8
Chromium for 64-bit macOS - All Codecs - Sunday, 15 April 2018
Chromium 68.0.3398.0 (Official Build) (64-bit)
Revision4204e85d87563d5d028182d7ec5c1f64697cc17c-refs/heads/master@{#550900}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- official build
No Sync • No WebRTC • No Widevine • Polly Optimised
Chromium.68.0.3398.0.nosync.polly.app.zip
https://github.com/macchrome/chromium/releases/download/v68.0.3398.0-r550900-macOS/Chromium.68.0.3398.0.nosync.polly.app.zip
SHA1 D6132207863551A885E6442612F2E8D0CBBDF958
No sync • No WebRTC • No Widevine • 66.0.3359.117 (540276) • Wednesday, 18 Apr 2018 (64bit)
seem ALL GOOD :)
Thanks Jerry too
Both your efforts and time are sincerely much appreciated :)
If so, what would be the difference henceforward between Chromium_Clang channel and Chromium_Polly channel ?
----------------------
Chromium_Clang
v68.0.3399.0-r551408-win64
Compiler clang (+lld_linker +thinlto +compiler_optimizations)
----------------------
Chromium_Clang
v68.0.3400.0-r551871-win64
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
----------------------
Chromium_Polly
v68.0.3398.0-r550920-win64
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations)
----------------------
Going forward there will be no more Chromium_Polly development channel, as Chromium_Clang is now built with Polly and FullLTO. :)
I probably will delete the old development channels for Polly and PGO at some point.
----------------
I have deleted the old Polly and PGO repositories. Started a new miscellaneous repository for 32-bit builds, experiments, etc.
----------------
New 32-bit build available. I have migrated it from ThinLTO to FullLTO.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3400.0-r551871-win32
I currently use chrlauncher to update and launch Nik's stable No sync • No WebRTC • No Widevine version.
If I also want to run Nik's LKCR version would installing another instance of chrlauncher and making another profile folder be sufficient to keep the 2 chromium browsers (i.e. stable and LKCR) separate and operate without issues?
Thanks in advance!
@Clamp: Yes, you can run 2 versions of Chromium side by side. The simplest way is to use 2 chrlauncher ("Portable" versions, here). All will be separated. No conflict. Compare chrome://version in each browser.
im on nik's stable and seems to me
extension does not update on chromium automatically - it needs to be done manually
on u.o you can backup your personal settings and filter
from chromium - extentions - ublock - option - settings (scroll donw to bottom) - back up to file and then restore from file (from the copy you saved)
yes ublock 1.16 also crash on my end - dont they test it out first?! rolling back
I was using chromium v65 when it happened, so i tried updating to chromium v66, but it didnt help.
Thats the point, ublock origin extension crashes, therefore it is not started and it cannot start, therefore i cannot go to its settings, therefore i cant just use ublock origin settings menu to get my filters. I can try to "reload" the extension, but that doesnt help, it instantly crashes again. Therefore, i need to find where ublock origin is holding user filters and get them manually. I suspect it holds them in some weird place, or even encrypts the filters list.
I usually scroll with middle click on pages and experience stuttering (while scroll) that appeared in last 3 builds. In flags, I have smooth scrolling turned off (flipping it on doesn't fix it). This issue is new, neither Nik's stable build has it, nor one of you builds up to the stated ones.
I already searched google, but wasn't able to find anything related, maybe someone here can confirm, to rule out it's a problem on my side. Also I hope this problem is not too minor or exotic to mention or look into.
All the extension settings and others are in C:\Users\XXX\AppData\Local\Chromium\User Data\Default
I usually keep a good copy of the chromium Default folder and just paste it over in time when needed (make sure chromiun is closed and not running at background)
or you may want to wait until the next version comes in and automatically install over
maybe your filter and settings will still be there
when I manually update and test 1.16 i had to uninstall (since there was no install over option that i know of) so everything was gone for me
so as long as it was not uninstall there's maybe a chance
if you have other browser ie firefox which uses ublock, and the filters are the same, you can just backup u.o from there
and when the good copy of u.o is ready for chromium, you can restore using the copy from firefox
thats all i can think of
anyway good luck :)
Chromium 68.0.3403.0(Official Build) (64-bit) - DEV Build
fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd-refs/heads/master@{#552589}
OS Windows
No Sync - No WebRTC - No Widevine - Polly Optimised
chrome.68.0.3403.0.polly.packed.7z
https://github.com/macchrome/winchrome/releases/download/v68.0.3403.0-r552589-Win64/chrome.68.0.3403.0.polly.packed.7z
SHA1 3ADF455D4526B8F1BC0F95A768E3D6A8A966F912
====
If colour hue adjust: chrome://flags/#force-color-profile
On https://tools.woolyss.com/html5-audio-video-tester/ the @Marmaduke Polly Chromium version 68.0.3403.0 (#552589) has a lot more functionals videos formats than the last Rob's Polly Chromium version 68.0.3401.0 (#552203) for very slightly lesser benchmark performance (invisibles differences in real world usage)
To @Marmaduke : Can you explain to Rob or public explain (if you want) how you do to integrate your codecs in your Windows Chromium Polly that allows the use of a very large number of video formats?
To @Anon3240 I got the scrolling problem too, it’s a revision-related issue.
I’m currently on a bisection to find since which version the problem occured too report a bug.
Forgot : you miss-packaged the wrong « chrome.zip » for Chromium~Clang 68.0.3401.0 (#552203) - win64.
It seem you took the « chrome.zip » of the Chromium~Misc 68.0.3400.0 (#551871) - win32 instead…
fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd-refs/heads/master@{#552589}
OS Windows
No Sync - No WebRTC - No Widevine - Polly Optimised - lld-link - FullLTO
chrome.68.0.3403.0.polly.lto.packed.7z
https://github.com/macchrome/winchrome/releases/download/v68.0.3403.0-r552589-Win64/chrome.68.0.3403.0.polly.lto.packed.7z
SHA1 FD96B501C77D78E4E7BB8C0C2696472EC8141A3E
====
@Mumu: Initially, I followed NIk's guide: https://github.com/henrypp/chromium and https://lexxai.blogspot.co.uk/2016/09/chromium-ubuntu-x265-hevc.html
The main problem with the incorporation of additional CODECS is keeping up with FFMpeg's changes and its implementation. I wrote a tutorial for MAC; but within days it was out of date, so, I took it off-line. In order to produce a Polly build, you must compile (FullLTO is my preference) the latest LLVM/Clang. Basically, what I am saying is that custom Chromium builds have to be actively maintained.
Nik (Codecs) and RobRich (Polly) are the Windows specialists. I compile/build Chromium for Windows for personal use (and to aid in the production of Chromium for the Mac).
The new and last build « chrome.zip » version 68.0.3404.0 (#552599) win64 miss the local (langages) folder… So it crash…
I can make it run by copying the local folder from the last build before (68.0.3400.0 / #551871 / win64) but I had some bugs + I seem I need a account like if this build use API Google key…
Not sure but I think this build need a re-check…
Thank you anyway for your works of course !
I took the local folder from the official Chromium branch (https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/552599/) and everything work fine !
So, you just need to update your last Polly by addind the missing local folder for your version #552599
So all the bugs I got come from this missing folder…
I'm hoping it's not a useless flag someone forgot to take out...I hate the new layout of chrome://extensions
Chromium for 64-bit macOS - All Codecs - Sunday, 15 April 2018
Chromium 68.0.3398.0 (Official Build) (64-bit)
Revision4204e85d87563d5d028182d7ec5c1f64697cc17c-refs/heads/master@{#550900}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- official build
- ld64 351.8 - XCode 9.3 (default linker natively supports LTO)
No Sync • No WebRTC • No Widevine • Polly Optimised • Full LTO • CFI
Chromium.68.0.3398.0.nosync.polly.lto.app.zip
https://github.com/macchrome/chromium/releases/tag/v68.0.3398.0-r550900-macOS
SHA1 14704A22B0ABC8520E75937A5EF7D35958DC7CC0
====
The intention is to make - Polly Optimised • Full LTO • CFI the template for the stable build, would appreciate it if someone would
benchmark the three versions of the "no sync" build.
Graphics Feature Status
Canvas: Hardware accelerated
CheckerImaging: Enabled
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Hardware accelerated
Rasterization: Unavailable
Surface Synchronization: Enabled
Video Decode: Hardware accelerated
Viz Service Display Compositor: Disabled
WebGL: Disabled
WebGL2: Disabled
'''
thanks in advance
But there is no flag and no userChrome.css to deal with.
So we can do anything with your or my UI problems…
Sorry Anon3265, but you can report this to chromium team and hope someone agreed with you…
I suspect chromium/chrome doing like windows 7 to windows 8 :
Make something polyvalent for desktop and mobile at the same same time but ending with an ugly unusable browser…
I really thinking about switching to firefox…
----------------
Updated 32-bit FullLTO build now available.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3406.0-r553318-win32
CFI:
chrome://gpu/
https://github.com/macchrome/chromium/releases/download/v68.0.3398.0-r550900-macOS/gpu.mhtml
Compile parameters:
cflags = [ "-O3","-flto","-mllvm", "-polly","-mllvm", "-polly-unprofitable-scalar-accs=false","-mllvm", "-polly-detect-profitability-min-per-loop-insts=40","-mllvm", "-polly-ignore-aliasing=true","-mllvm", "-polly-tiling=false","-mllvm", "-polly-stmt-granularity=scalar-indep","-mllvm", "-polly-invariant-load-hoisting=true","-mllvm", "-polly-enable-polyhedralinfo=true","-mllvm", "-polly-check-parallel=true","-mllvm", "-polly-check-vectorizable=true","-mllvm", "-polly-prevect-width=32","-Xclang", "-vectorize-loops","-Xclang", "-vectorize-slp","-Xclang", "-Rpass-analysis=polly","-Xclang", "-Rpass=loop-vectorize"]
ldflags += ["-flto","-fvisibility=hidden", "-fsanitize=cfi" ]
====
BTW, some of those Polly settings are now defaults, changed, and/or unneeded. Polly is still a moving target.
You can see my current Polly config here:
https://github.com/RobRich999/Chromium_Clang
Here are my current LLVM tweaks as well, if you are interested. YMMV.
"-mllvm", "-enable-deferred-spilling",
"-mllvm", "-enable-implicit-null-checks",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-misched",
"-mllvm", "-use-cfl-aa-in-codegen=both",
"-mllvm", "-vectorizer-maximize-bandwidth",
I understand the polly concept, but not its implementation: such as, which are the best parameters to use.
"-mllvm", "-polly", = invokes Polly
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40", = tells Polly to work with loops as small as 40 instructions
"-mllvm", "-polly-invariant-load-hoisting", = attempt to hoist invariant loads out of the loop
"-mllvm", "-polly-optree-normalize-phi", = replace PHIs (SSA/IR) with their incoming values
"-mllvm", "-polly-precise-fold-accesses", = fold memory accessess
"-mllvm", "-polly-precise-inbounds", = higher precision for inbounds assumptions
"-mllvm", "-polly-run-dce", = Polly's internal dead code elimination
"-mllvm", "-polly-vectorizer=stripmine", = prevectorization routines
"-Xclang", "-Rpass-analysis=polly", = output Polly scop info to display
Then for V8, since it routine exceeds default zone analysis for DeLICM.
"-mllvm", "-polly-delicm-max-ops=0", = unlimited zone analysis for problematic scalar dependences
I suggest not setting unlimited delicm globally, as it can push some of media-related source files into the hours (days?) each to build.
I stick to it as long as they don’t make the same compact bookmark toolbar than firefox !
All good - been online for a good hour or so no problem encountered thus far
Thanks nik :)
Thanks Jerry :)
Much appreciated for the great work and time - Hv a gd wkend
"-mllvm", "-adce-remove-loops",
"-mllvm", "-addr-sink-new-phis",
"-mllvm", "-addr-sink-new-select",
"-mllvm", "-aggressive-ext-opt",
"-mllvm", "-combiner-global-alias-analysis",
"-mllvm", "-condsider-local-interval-cost",
"-mllvm", "-costmodel-reduxcost",
"-mllvm", "-da-delinearize",
"-mllvm", "-enable-aa-sched-mi",
"-mllvm", "-enable-cond-stores-vec",
"-mllvm", "-enable-deferred-spilling",
"-mllvm", "-enable-implicit-null-checks",
"-mllvm", "-enable-interleaved-mem-accesses",
"-mllvm", "-enable-ipra",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-misched",
"-mllvm", "-loop-prefetch-writes",
"-mllvm", "-force-precise-rotation-cost",
"-mllvm", "-regbankselect-greedy",
"-mllvm", "-vectorizer-maximize-bandwidth",
"-mllvm", "-polly",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass-analysis=polly",
Plus for V8:
"-mllvm", "-polly-delicm-max-ops=0",
Thank you very much. For your build in 32 bit.
Someone have a tip for uBclok Origin 1.16.2 stop crash in Nik buid : No WebRTC 68.0.3399.0 (551299)
With 67 No WebRTC crash too..
gorhill don't care and don't want fix it.
For him uBO is for use with Chromium same build number of Chrome.
So I added my own lament (https://bugs.chromium.org/p/chromium/issues/detail?id=838282) , hoping that Chromium’s devs’ will take pity on an old lady and go back from this suicidal idea of making such a hideous favorites bar !
Note : uBlock crash is fixed in every Nik and Rob version with 1.16.2 version. Note that I only test with fresh install (not update)
@Mumu Thank you very much too. For info. But i'm interersting by fix for update not fresh install.
Too bad I will use Scripsafe or try this extension for see :
7 Times Faster: https://chrome.google.com/webstore/detail/7-times-faster/bcidahcpjehlemnbmeaepadalhjofnmp
Execution of installers are blocked by Windows 10
Quick *plug* I made a (self running) PowerShell script to keep Chromium updated. Get it form GitHub: https://github.com/mkorthof/chrupd Maybe someone finds it useful. It has has options for editor, channel and can add a Scheduled Task.
A big thanks to all of you! ;)
@Pierre: Do you use Windows Defender?
@Marius: Thank you for your work and sharing. I added your #updater ! ;)
-------------------------
An optimized build for Linux. Should work with Debian, Ubuntu, and similar. I suggest gdebi if needing a local deb package installer.
Chromium 68.0.3417.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision d8de8d344e4ae611abcf5178b4bef8d84f4911fb-refs/heads/master@{#555149}
Compiler clang (+lld_linker +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3417.0-r555149-linux64
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3417.0-r555158-win32
I can't download the latest 66.0.3359.139, downloads stopped at 70% and couldn't be resumed.
Mine is still Version 65.0.3325.181 (Official Build) (64-bit). In last 2-3 days, I had problems opening any Google pages (youtube, search). I had no issue with FF / Opera using the same connection.
https://bugs.chromium.org/p/chromium/issues/detail?id=800653
We live in interesting times: all the Google code monkeys want to do is to checkout Grindr and Tinder.
Thoughtless talentless morons.
Not much better for the tinder case : https://www.theguardian.com/technology/2017/sep/26/tinder-personal-data-dating-app-messages-hacked-sold
I will not go into the Facebook case...
Yes, very interesting times…
I return to Firefox. Quantum Beta 61 just release today. Good luck with Chromium my friends!
if now its webRTC, whats next?
its never about webRTC or that, its about control and who has 'power to enforce' the new world product to fit the new agenda
May hv to stay with the last good copy of no-webRTC
is waterfox better than firefox? firefox seems to have a few 'issues' lately
and waterfox has break off with ff so they say
hv a gd wkend ppl
Revision 8f49bff3b0aadec93b59c0d8966dfce6085f37a6-refs/heads/master@{#555869}
Compiler clang (+lld_linker +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3419.0-r555869-linux64
-------------
Chromium 68.0.3420.0 (Official Build) (Windows 32-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 00eb06c3827b91f6b9221fa566a891b01fb7e92b-refs/heads/master@{#556041}
Compiler clang (+lld_linker +fulllto +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3420.0-r556041-win32
It is getting annoying maintaining all the various extra LLVM flags when something breaks, especially if the performance difference is minimal at best outside of benchmarks anyway, so they are gone for now.
So for those interested, all optimized code targets are at -O3, and Polly is configured as below.
"-mllvm", "-polly",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass-analysis=polly",
your innovation spirit is admirable :)
- https://www.ghacks.net/2015/08/18/a-comprehensive-list-of-firefox-privacy-and-security-settings/
- https://github.com/ghacksuserjs/ghacks-user.js/
Optimized code targets for the Polly+FullLTO build are at -O3 and "-mllvm", "-polly" as applicable.
----------------
FYI. The commit to remove the webrtc build flag landed today.
----------------
@new_user It is not incompetence or ill will, but more of code consolidation IMO. If one component already provides something, the idea is why duplicate the code in another component when it can be cross utilized instead.
I built Firefox awhile back. It is straightforward enough to build. My build did not pickup my additional flags in a custom mozconfig file, but admittedly, I did not spend much time poking at it. I might revisit later.
Yeah !
I don’t know really why but i get little more stability and performance with ThinkLTO than Polly on my system…
So — for my case only — I upvote for a return of the thinkLTO build ;)
That is good news. Makes my life much easier.
Having said that: while the Google troop are forlornly recreating the works of Shakespeare, I wiil (foolishly) try to subvert their efforts.
How the hell wiil the White Helmets be able to post their mock chemical attacks, and Bibi be able to entertain us with his comedy Ikea bookshelf of Iran's nuclear secrets?
Chromium is too intertwined with Chrome. 'He who pays the piper calls the tune'
I want to talk to the organ grinder (Chromium), not the monkey (Chrome)!
Revision 672cc57f93fb23198daf242d123fb4686f47dbe9-refs/heads/master@{#556381}
Compiler clang (+lld_linker +fulllto +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3424.0-r556381-win32
----------------
Chromium 68.0.3424.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 8373deab43ade25295225bcbb56a05c6e28c949c-refs/heads/master@{#556452}
Compiler clang (+lld_linker +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3424.0-r556452-linux64
so which version is the LAST good copy of NO-webRTC?
@jerry & dev - pls advice when it is the LAST FINAL no webRTC copy and when it is becomes effective.
THANKS IN ADVANCE :)
Thanks for all your effort and time :) Much appreciated
I used a customized mozconfig file to enable basic -O2 optimizations and disable some options like the crash reporter, version updater, and maintenance service. I also eventually got the installer to build.
Firefox 62.0a1 build 20180507230735 installer
SHA1: 25709bbe51d2e1c5a253299f1d685050ded76ce2
https://drive.google.com/open?id=1_d4kUzsw99IhGCELs8lHjFMTxp_3yYdE
Consider the build just a proof-of-concept. I am not sure there will be any further releases. If I do, I might setup a repository at GitHub.
UO is better than nothing but its not as good it seems -
https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address
Chromium's Kanye West:
"Remove enable_webrtc and treat it as always true from now on.
enable_webrtc=false has been broken for months and no one has noticed,
so let's get rid of this complexity. WebRTC will now be a part of
Chromium until the serpent Nidhoggr ascends into the sky and ushers
in Ragnarök."
Alas, poor Yorick! I knew him, WebRTC...
we want NO-webRTC back!
Ha :D Looks like new world order is already silently activated?!
I'm being lazy and perhaps a bit arrogant: Google are incapable of delivering an initial "stable" stable release or subsequent stable "stable" release (of Chrome).
In answer to your question: when the next revised stable release is released, or if I lose the war of attrition within the next few days.
Where feasible, I'll continue to build the Stable branch with "webrtc=false" (where necessary). But, alas, future releases of the DEV branch will have webrtc enabled by default.
I suppose the next logical step for Chromium/Chrome is to make Java-script compulsory!
Chromium for 64-bit Windows - All Codecs (inc. AC3/AAC Digital Surround) - Tuesday, 08 May 2018
Chromium 68.0.3425.0 (Official Build) (64-bit)
Revision 25f7b20ec517e326d0f0023882a0a1ff2223e1a0-refs/heads/master@{#556726}
OS Windows
No Sync - WebRTC - No Widevine - Polly Optimised - lld-link - FullLTO
chrome.packed.68.0.3425.0.webrtc.lto.7z
https://github.com/macchrome/winchrome/releases/v68.0.3425.0-r556726-Win64/
======
Combination of uBo and ScriptSafe (browserleaks.com)
WebRTC Leak Test
WebRTC Support Detection
RTCPeerConnection✔True
RTCDataChannel✔True
ORTC (Microsoft Edge)×False
IP Address Detection
Local IP Addressn/a
Public IP Addressn/a
IPv6 Addressn/a
WebRTC Media Devices
Device Enumeration×False
Has Microphone×False
Has Camera×False
Audio-Capture Permissions ×False
Video-Capture Permissions ×False
Media Devicesn/a
=======
Like Alphabet and ultimately Chrome, WebRTC is great no loss.
Do you know where the official moves the files?
https://storage.googleapis.com/chromium-browser-snapshots/index.html
- https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/403380/ (official, dev, unstable),
- or re-compile the stable version (49.0.2623.112) yourself,
- or use the nik build: https://github.com/henrypp/chromium/releases/tag/v49.0.2623.112-r403382-win32 (unofficial, stable)
32-bit Windows: https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3426.0-r557214-win32
Someone has the same problem?
Big thank you to all contributors and the site admin for your work :)
Yes, WebRTC basically can return your IP info if queried, but your browser's usual HTTP headers return IP info and a wealth of other data anyway. The potential privacy concern is WebRTC providing IP info if located behind a VPN or anonymous proxy, so if either apply, block the WebRTC query (among other things) with an extension. If neither apply, then it is pretty much "whatever" IMO.
1. The current autocomplete issue affecting bookmarks now has a couple of active bug reports. Hopefully it be resolved soon.
2. Bookmarks on about:newtab are not working in my latest Win64 build. If you have the bookmark bar enabled, you are not affected anyway. Otherwise, I will file a bug report if the issue persists for another build or two.
3. My latest Win64 build, which will go public in a few minutes, is back to ThinLTO. There apparently has been some work on ThinLTO, as it is now measurably outpacing Polly+FullLTO in various tests, particularly in JavaScript performance. Polly+FullLTO is being shelved for now, though it could return to my misc builds repository as an experimental build in the future.
4. With Polly being shelved, my build box should have enough time to churn out regularly updated 32-bit ThinLTO builds again, assuming anyone is interested. Just let me know.
I often thought it might be quite convenient if it was possible to create more than one incognito session at once, like a new private tab/window wouldn't share browsing data with other private tabs/windows that are already open.
I know that one of you guys use OSX 10.9. Chromium has recently removed OSX 10.9 dependent code, so be prepared for changes in v68+
I'm currently looking at adding additional CODECS to Firefox; but, I find the build system to be arcane: Chromium's is much more elegant!
I don't think Firefox is as (natively) extensible as Chromium. My initial impression of Firefox's build process is that it is crude. I've much to learn.
My issue is clang-cl, which is a drop-in VS cl.exe replacement. Looks like build file modifications are going to be required to get it working, at least with my configuration. I might just wait until VS2017 building is working again.
A question : in your stable version, do you apply the security patches which exist in Google Chrome, cf here :
https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html
(Difference between Google Chrome and Chromium current versions)
Luckily, there's a bunch of apps that continue running on Mavericks while advertised as 10.10+, whether without doing anything (Postbox 5.0.20 & 6.x) or by editing the info.plist file (Opera is one of them).
So when Chromium stops being an option, we still have Firefox, Waterfox, Vivaldi, Opera (for the time being) — only mentioning those that are regularly updated.
Seem there is an update on ungoogled-chromium ➜ https://github.com/Eloston/ungoogled-chromium/releases
Something like : ( ungoogled-chromium | 66.0.3359.139-1 | Eloston | 9 days ago )
But your API return : ( ungoogled-chromium | 65.0.3325.181-2 | squalus | 3 weeks ago )
Source : https://www.murielfrenchcouture.fr/autres/Chromium.php
=====================================
Chromium for 64-bit macOS - All Codecs - Saturday, 12 May 2018
Chromium 68.0.3429.0 (Official Build) (64-bit)
Revision 3fd9a73f1e93ce041a4580c20e30903ab090e95c-refs/heads/master@{#558128}
OS Mac OS X
only for macOS 64
with codecs (h264, h265, flac, xvid, etc..)
WebRTC (The ability to disable WebRTC has been removed from Chromium)
official build
ThinLTO
CFI
https://github.com/macchrome/chromium/releases/v68.0.3429.0-r558128-macOS
What I find it strange is that I don't remember seeing this while using Chrome, only with Chromium.
I'm using the No sync • No WebRTC • No Widevine build.
- info: https://chromium.googlesource.com/chromium/src/+/lkcr/docs/servicification.md
- source code: https://cs.chromium.org/chromium/src/services/data_decoder/manifest.json?sq=package:chromium&dr=CSs
The autocomplete issue affecting bookmarks is still present, but a possible commit causing it has been found and the bug report has been assigned to a developer.
Bookmarks on about:newtab are back working as of my r558159 build.
Do you (or others) have any idea why this service appears on Chromium, but not on Chrome?
I don't see it, only the 64bit version seem to have been compiled.
Regards
online for a good hours or so - So far ALL GOOD :)
Thanks nik & Thanks Jerry
All your work and time is much appreciated :)
p/s pls let us know when its the last good copy of NO webRTC. Thank you kindly
In reponse about (2nd paragraph of #comment-3246)
Here a quick comparaison of how codecs works with differents Nik, Marmaduke, Rob or Squalus version (see Note) :
https://www.murielfrenchcouture.fr/autres/Chromium/codecs.html
Note :
1/ I used Jerry’s tool here : https://tools.woolyss.com/html5-audio-video-tester/
2/ If a codec is not tested that means it works in every browsers.
3/ I can NOT test NetFlix, Twitter, Facebook, Intagram, Streaming, etc. because I don’t use any of these BluePilled malware but if someone got problem with one version or another with NexFlix or so on, please feel free to post your problem here.
@mumu: Nice overview! ;) I also updated "ungoogled-chromium" on my api after your previous comment.
- https://www.murielfrenchcouture.fr/autres/Chromium.php
- https://www.murielfrenchcouture.fr/autres/Chromium/codecs.html
@no more widevine: Yes I know. Here, developers and most of users do not use this plugin at all. So, this is not our priority. Chromium does not support Widevine natively.
@Pierre: Yes, the security patches are the same in Google Chrome and stable Chromium, for the same version obviously.
@WildByDesign: Completely agree with you. Builds are always greatly appreciated. Cheers devs! ;)
so far all good no problems :)
Thanks nik + Thanks Jerry :)
Thank you both kindly
----------------
r559605 includes additional LLVM tweaks dealing with register allocations. For the curious:
"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-deferred-spilling",
I also enabled string tail merging during linking. It should bring browser binary file sizes down a little, though the archive and installer downloads might actually be a little larger due to compressibility of the resulting files. Anyway.
And your are totaly right : it even worst that there is no flag to turn off this horror while there is 12 flags (padding, etc.) to customize the omnibar !
This chromium new « material design » go from Charybdis to Scylla.
As a result, I have made some tests few weeks ago :
And here the summary up with RobRich version :
— 68.0.3404.0 (552599) is the last one with narrow bookmarks bar.
— 68.0.3406.0 (553004) is the last one with the old classic bookmark manager if you disable chrome://flags/#enable-md-bookmarks (newer version lost this flag)
— 68.0.3400.0 (551871) is the last one with the old classic extension manager if you disable chrome://flags/#enable-md-extensions (newer version get this flag, but it do nothing anymore)
Note : you should probably need to disable chrome://flags/#secondary-ui-md too. YMMV.
To put it in a nutshell : because I need the old classic bookmark manager AND a narrow bookmarks bar I have stopped all updates and I stuck with RobRich version 68.0.3404.0 (552599).
I will try to customize the Roomy Bookmarks Toolbar Extension too be less buggy but if I fail or if it take too much time I will probably go back to Firefox or Waterfox as primary browser...
I can tweak the width of the bookmarks a little more if desired. Slightly wider perhaps? I cut them down by a third in the above shown build.
@RobRich: Didn't know that was possible. The difference is huge still. I appreciate your efforts, though!
Obviously you have clearly shorten the total length of bookmark in bookmarks bar. (★ top of the image)
Great !
But to go further what most of us are looking is also too shorten the padding between icons without name (★ middle of the image)
But it is a good idea to tweaks chromium source.
I need to learn how to compile Chromium and need to do a bisection beetween narrow and large bookmarks bar to find where the pixels to kill are…
I think I will try too make my own compilation instead of an extension.
I just have afraid because dev here speak about 2 days and 20Go to compile chromium source to bin … o-O !!
Source and various tools can be up to 20GB to download, but then it can be incrementally updated - usually a few MB.
Clang really cut down the compiled build storage requirements compared to Visual Studio. My latest 64-bit build directory is under 4GB, though I do disable ThinLTO build caching.
I will look at the bookmark bar source a little closer. There might be a way to further close the spacing.
I will post a build to try here in the comments. While take a few minutes to update and relink.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3434.0-r559605-exp-win64
Had to update and relink a couple of times. Zero'd out bookmark insets now.
I think bookmark icon-only spacing is about as narrow as it is going to get by just modifying variables.
I would not mind reducing the space around bookmark text, but that is perhaps another time. I did not spot a quick fix by skimming the bookmark bar code. Might be something in Material Design instead. I also think possibly disabling the tail fade on bookmark text might help in perceptually closing the spacing, even if it does not actually change the spacing.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3434.0-r559605-exp-2-win64
I am open to actual bookmark width. Bookmarks with text still are chopped by a third from default. I can add back some, or just return to default if desired.
66.0.3359.181 https://www.virustotal.com/#/file/5e2e7365424dfa47029a720be7298a6a7c02b249de817dfae6d58700000ef9f6/detection
66.0.3359.170 https://www.virustotal.com/#/file/002377b4678a5a5c25b43a03e70e6f297a157392fdcfa8cbbe5ed73680ca12b8/detection
Thoughts?
Otherwise, Chromium is a not a signed executable, plus its hash will not match any public Chrome releases despite having the same file name. AFAIK, either could be a reason for being "suspicious" according to certain malware scanners.
Might want to check the machine that's compiling the 32bit versions
For curiosity's sake, I just tossed chrome.exe from my latest public 32-bit build at VirusTotal.
https://www.virustotal.com/#/file/814ac552e7117dd0104b05b9118dd7fbfe30cd83b1a0ad1dc72f91a687798faa/detection
Not as many results as your run, but nonetheless, mine even hit one false positive for a supposed (decade-old) virus.
I can not speak as to what other builders do, but my build box is regularly security audited.
----------------
New experimental Linux build available.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3434.0-r559637-exp-linux64
This experimental build includes actual ThinLTO link-time optimizations enabled - not just using it as a parallel linker. Please note libc 2.7 or later is required, thus likely breaking compatibility with older versions of Linux. Ubuntu 18.04 or similar is recommended. The command "ldd --version" can be used to check the installed libc version.
To keep file sizes somewhat down I also modified the Linux build configuration to lower the instruction import limit for ThinLTO. Chrome OS is doing the same thing right now, and the claimed performance difference versus the default limit was like 1%, so whatever IMO.
<<
Better for sure but not quite like the 68.0.3404.0 (552599) build i think, hard to tell from screenshot only. Is it the maximum allowed?
>>
@Anon3378, it is not like 68.0.3404.0 (552599) it is… Better !!
RobRich succeeded to get the same padding than older’s versions but more, he also reducing the text in bookmark !!
I can make pixel by pixel comparaison because Rob use a standard full-HD 1920x1080 screen :
RobRich (sent by the Chromium’s Gods) succeded bookmarks padding with textless icons
RobRich (sent by the Browser’s Gods too) succedeed bookmarks texts chopped by a third from default
I ’m a little busy now but I will try your experimental bookmarks hacked version soon and keep you informed.
But I ’m pretty sure your experimental bookmarks hacked version will become my official new daily used browser !
However, keep the tail fade at the end because that "it does not actually change the spacing" will just make the bookmark more ugly and less legible without any benefit in spacing.
Thank you very much Rob, I would like to learn how to compile, how to hack source but in a few hours you maked everything !
I understand it is some work so I suggest for many users as me and Anon33xx to make a new version like this one once a month for example on your GitHub misc-Channel called with something like « Old BookMark Style Version » ;)
I think we are going to get a new browser on the market soon ! Chrome, Firefox and… ChromoRoboMium ! ;D
Again, thank you for everything Rob !
It does not surprise me that you are reacting. Thank you !
If I use Rob version in daily usage, you should know that your version Stable is my version when I need a very interactive browser and something robust. (video, audio, webGL...)
I admit that I did this little codecs comparison page hoping that you take action!
Thank you very much also Nik for your consistency in building Portable Chromium binary since century !
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3435.0-r559838-exp-win64
It features the bookmarks bar changes, plus refactoring of compiler optimizations and modification of the LLVM instruction import limit for ThinLTO. The hopeful expectation is to decrease binary file sizes without significantly (or even at all?) impacting performance.
As we can see, RobRich a zero’d all paddings than he can zero’ing plus reducing text length. Fade tail is still present for nice ending too long text.
The only pseudo-problem we can (barely nerver) encounter is if we have a full width colored 16px icon (a square) with a full width wide length large character at starting text ( 📺 , 📅 , █ , — , smileys , …) : it touch.
But the case would be very rare and as a workaround we can use a tiny narrow unbreakable space before the text ( see ➜ https://fr.wikipedia.org/wiki/Espace_(typographie)#Langage_HTML )
For me it OK !
Firefox is still better in the only and unique case of a full only icon textless bookmarks bar (10px between icons VS Rob 12px)
But that only 6 icons less on a full-HD screen (±74 VS ±80 ➜ ±8%) while in the new MD original Chromium design the bookmarks bar in full-HD can take only… ± 50 icons ! ➜ ±38% !
And as soon as we add text in Firefox bar, RobRich largely takes advantage again thank to is shorten text…
Thank you Rob !
You maked my week-end !
Nobody IRL will understand why i am in so good mood ! ;)
Of course on the mother picture read 68.0.3434.0 and 68.0.3431.0 instead of 66.xxx (cut and paste error)
About the three last Rob compiled experience, the bookmarks bars is identics.
Strictly from exp1 to exp2 and the only difference between 68.0.3434.0 and 68.0.3435.0 is the highlighting height, a Chromium behavior ➜
Like @Mumu said (and LOL at that image, i laughed) thank you very much for your efforts. You're really good when it comes to tweak this kind of stuff!
The only difference remaining now is the bookmarks bar height, which according to @Mumu comparisons, is 6 pixels (?) higher. Nonetheless i'm happy with this anyway, the thing which triggered me the most was the fact that i lost 8 bookmarks to that space between each other.
Thank you :)
----------------
I have picked up an annoying random crasher. Started around the same time as adding back a couple of LLVM tweaks for register allocations, so out they go for now. I will get a new experimental build posted in awhile.
About the refactoring of optimizations in the experimental build, optimized code paths are building at -O2. I have been down this road before building Chromium, as -O3 is not always faster due to allocations, caching, etc. Likewise, ThinLTO is optimized at lldlto=2, plus I modified LLVM to lower the default instruction import limit for ThinLTO from 100 to 30.
Result? Octane 2.0 and Basemark Web 3.0 are about the same. File sizes are down by about 26MB overall.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3435.0-r559863-exp-win64
Includes bookmark mods, refactored compiler optimizations, removal of previous LLVM register allocation tweaks, LLVM instruction import limit mod for ThinLTO, and enabling LZMA2 compression for the installer. The compression settings have not been updated in years, so I might be able to squeeze a slight installer file size reduction there.
Same here with 68.0.3434.0 (559605) win64…
« […] Mumu seemed to like it […] » Yeah ! :D
And many other anon ! 👍
If your bookmarks are hacked because of the reduced by a third text you can rename it.
For example :
Before ➜
Here a bookmark name 1
Here a bookmark name 2
Here a bookmark name 3
Here a bookmark name 4
After ➜
Here a bo…
Here a bo…
Here a bo…
Here a bo…
Renamed to ➜
1 Here a …
2 Here a …
3 Here a …
4 Here a …
But I agreed, if we must have a debate it’s not to the others anons to rename their bookmarks to fit short length but to me to deal with standart bookmark length text :(
Or as I said previously to Rob, roll out once a month (for example) a custom extra narrow bookmarks bar version for few autists like me on your misc-channel ! ;)
Last minute edit : Why not compile standard untouched source on clang-channel and « hacked » version on misc ? With this, Anon3397 above will be satisfied by using usual clang-channel and me on misc-channel.
Grab the latest exp build. r559863 has been stable thus far in my usage. Looks like it was one or both of the LLVM register allocation options I was using in recent builds, which I removed for r559863.
I still have sometime random brutal close (crash) with version ➜ 68.0.3435.0-r559863-exp-win64
But do jump to quick on it, it probably a chromium problem.
----------------
On the Linux side, I am attempting to use the recently added ability to utilize a provided in-tree Chrome OS (basically Linux) profile to provide profile-guided optimization (PGO) for Chromium on Linux. Not sure how far I can deviate from the expected optimization defaults with it still working as expected, though. Currently building a preliminary test build.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3435.0-r560127-exp-win64
Fresh build. Updated LLVM source and build. Updated Chromium source and build.
Thinking of possible trouble spots, I withdrew LLVM's new pass manager for the build. I do not really need it anyway, so whatever.
Nothing else I am doing should be affecting stability. Performance, yeah, but that is another topic.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3436.0-r560151-exp-linux64
I use Chromium to watch Netflix
but since 68.0.3424.0 dev-codecs-sync,
Widevine updater is no longer working,
thus Netflix not working...
(currently 68.0.3435.0 dev-codecs-sync still doesn't work)
The last known Chromium build dev-codecs-sync that works is 68.0.3399.0
and Widevine updater works accordingly
I am using 66.0.3359.181 stable-codecs-sync for now...
They have been some changes in codecs configuration.
As by this #comment-3387, Nik is aware about and on it.
Just stuck on your 66.0.3359.181 stable-codecs-sync for now and wait for next update I supose…
=====================
@RobRich
Still random crashs on last v68.0.3435.0-r560127-exp-win64…
Rarely, one by 5 minutes and I can’t find why ’cause chrome://crashes is disabled on Chromium :(
I will investigate on [Monorail / Chromium Bugs] on last issues…
There is a Chromium bug report, but I do not have the link right now - away from my computer.
Revision a3b0c20cba521b2b7182ea85781afb1bc06eceb0-refs/heads/master@{#560127}
OS Windows
Faulting application name: chrome.exe, version: 68.0.3435.0, time stamp: 0x5aff8fcc
Faulting module name: ntdll.dll, version: 10.0.17134.1, time stamp: 0x207580e2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4eeb
Faulting process id: 0x2710
Faulting application start time: 0x01d3ef3611881603
Faulting application path: C:\Users\RobRich\AppData\Local\Chromium\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3bcb65df-43e4-44db-a521-2bf2031a2166
Faulting package full name:
Faulting package-relative application ID:
0xc0000374 is heap corruption.
Closest bug report I could find in a quick search:
https://bugs.chromium.org/p/chromium/issues/detail?id=822629
Other similar reports:
- https://www.google.com/search?q=chrome+0xc0000374
- https://www.google.com/search?q=chrome+ntdll.dll
Does any one use the installer version of Chromium? If so, can you set Chromium as the default browser in Windows? And it's listed in the "Programs and Features" of Windows like any other program? Can you uninstall it normally?
Thanks!
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3436.0-r560190-exp-win64
Has the bookmark mods. No optimization mods. Compiled with the revision's bundled Clang. Linked with VS2017.
Faulting application name: chrome.exe, version: 68.0.3436.0, time stamp: 0x5b00f6b9
Faulting module name: ntdll.dll, version: 10.0.17134.1, time stamp: 0x207580e2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4eeb
Faulting process id: 0x3bf0
Faulting application start time: 0x01d3eff3a438bec9
Faulting application path: C:\Users\RobRich\AppData\Local\Chromium\Application\chrome.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 61a4d8ae-6e2e-4beb-9a87-957d8cab06db
Faulting package full name:
Faulting package-relative application ID:
I am going to try a VS2017 build to rule out Clang, assuming I can even get Chromium to build with VS2017 anymore. Been quite awhile.
Thanks for this update! :)
https://support.microsoft.com/en-us/help/4093836/summary-of-intel-microcode-updates
Assuming you have Win10 April 2018 Update:
https://www.catalog.update.microsoft.com/search.aspx?q=4100347
Just covering bases here. I manually installed the microcode update earlier tonight, and no Chromium crashes.... yet?
that´s smart, I did not even know of that driver from VMWare, they have some nice tools as usually! A bit off-topic: can you possibly post the latest AMD microcode updates? I would like to update my Threadripper 1950x too, or at least check if I have the latest one. Is there another source where to download the latest microcode updates to use with this driver, beside from installing Linux?
Thanks so much :-)
But I think you are right, the problem come probably from (my/our) system and not Chromium…
See ya soon and thank you for your help and patience !
That said, and for the curious....
I get my AMD microcode from the Debian archive.
https://packages.debian.org/sid/amd64-microcode
7z can unarchive the deb, then unarchive the tar, then ya' have the files.
IIRC, you might have to have the Intel microcode files as well to get the VMware utility to run without errors. This one has a microcode.dat file:
https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File
To verify, you can access the CPU MSR registers to view the patch ID of the microcode using RW.
http://rweverything.com/
Regardless of how the microcode is updated, and assuming everything is right, a currently modern system ideally should show mitigations for Meltdown and Spectre. If so, you should be good to go.
https://www.grc.com/inspectre.htm
As for my Opteron box, I am still waiting on Spectre mitigation; probably in a future Debian AMD microcode update.
----------------
Speaking of Linux.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3437.0-r560194-exp-linux64
The LLVM instruction import limit for ThinLTO is back to default. Compiler optimizations are stock since I am using a provided PGO/AFDO profille, but ThinLTO linker optimization is pushed up to O3.
I am currently cooking a Windows build using similar compiler optimizations as the default Linux config, while relying on ThinLTO at O3 to do the heavy lifting on extra performance optimization.
https://bugs.chromium.org/p/chromium/issues/detail?id=844999
Suppose we might actually see if its Chromium, Windows, or whatever.
I don't know why in dev build the widevine isn't work, because config arguments is the same. I still try to figure it out.
----------------
IIRC, only one crash since last night.
----------------
The build box has churned out multiple Windows builds today. Been comparing optimization options. Fun.
It probably is more of a waste of file space than a serious increase over -O2 for most tasks, but I am back to -O3 for all optimized targets for Windows builds based upon Basemark Web scoring. ThinLTO is at -O3 and its default instruction import limit, so even more file space, plus rolled back in some LLVM compiler options as well.
"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-deferred-spilling",
"-mllvm", "-enable-implicit-null-checks",
I have some things to do right now, so I will push the build to the regular listings this evening. :)
Next up is probably seeing about getting new pass manager and maybe even NewGVN back into the mix.
Thank you for your help and your heavy investment!
I'll be honest, it become a bit too technical for me when I study links you provide.
From what I understand:
I got a Intel Core i7-4710HQ on a windows 8.1 (sorry).
My CPU ID is 000306C3 with a Microcode Revision number 1C.
You are right, there is a Microcode Update (version 0x23) for my Haswell (including H, S), Xeon E3 on https://support.microsoft.com/en-us/help/4091663/kb4091663-intel-microcode-updates
But this one seems to concern only Windows 10.
I confirm that I am not up to date in my windows update. I have not done the update against Spectrum and Meltdown to avoid impacting the performance of my device too much (but it seem there is no or little impact on my modern hardware)
I'm not sure of the link between Spectrum and Meltdown and Microcode CPU updates.
However, I noticed that you crashed too with the same version as me (68.0.3436.0-r560190-exp-win64 ➜ No optimization mods / Compiled with the Clang / Linked vs VS2017 bundle) and you have no more crash until today having updated your microcode.
In short, I must for starting eliminate all parasitic causes on my side like using a RAM disk, clean the cache or start from a blank profile, update my window and repair what I broke in Windows 8.1 for make it operate like a windows 7, etc.
In fact what we miss the most is the return of other anons!! Is it only you and me who crash or is it everyone?
I do not even know if it comes from Chromium, Windows, or whatever for now :(
If there is really nothing to do, I will either switch to Windows 10 or beg Nik to compile a version with the bookmarks modification only for me :$
But don't take offence Portable by Versatile Apps, works more fast of your 68.0.3434.0 or your 68.0.3437.0
I don't understand why ?
@Anon3429: Could be revision changes, though I am thinking perhaps memory usage. It has been an issue previously with my 32-bit builds. I have been reusing my 64-bit config for recent 32-bit builds, so I will revisit the optimization levels for the next public build.
What is interesting?
-------- [1] --------
The stable version of Nik { Nik @ stable-codecs-nosync - 66.0.3359.170 / 540276 } works perfectly with all codecs.
But with the next update { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 } we lost some codecs…
I inform the community:
« […] Here a quick comparison of how codecs works with different Nik, Marmaduke, Rob or Squalus […] » (#comment-3362)
Nik reacts 48 hours later with the following message:
« […] i did not notice that they change some configuration. The next build will have codecs enabled. […] » (#comment-3387)
The following versions are corrected.
Well done Nik!
It seem to only remains a problem with WidevineCdm according to Anon3426 ( #comment-3426 ) which I can not test because I can not find a video with Widevine…
If someone has a link or a technique…
-------- [2] --------
The codecs functioning of { Squalus @ ungoogled-chromium 66.0.3359.139-1 / 540276 } is exactly the same as { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 }
Is Squalus @ ungoogled-chromium based on Nik @ stable-codecs-nosync?
-------- [3] --------
This will interest RobRich: I encountered a crash while testing the codecs with the version of { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 } and also 2 crash with the version { RobRich @ - clang - 68.0.3437.0 / 560197 }…
But I have less more crash (only two in 12h usage) after a full windows soft/hard/firm-ware update and using last clang (not exp).
-------- [4] --------
We notice a curious detail:
The { Nik @ stable-codecs-NOSYNC - 66.0.3359.181 / 540276 } version has a DLL (widevinecdmadapter.dll) in the version of the previous release (66.0.3359.170)
While the version { Nik @ stable-codecs-SYNC - 66.0.3359.181 / 540276 } does have this DLL in the same version (66.0.3359.181)
See snapshot here ➜
-------- [5] --------
Marmaduke seemed to have the best technique for embedding codecs as he describes at #comment-3246
Where he explains that he followed the tutorial of… Nik !!
---------------------
Morality, Nik you seem to be the codecs master.
Are you still using this tutorial to integrate all codecs ➜ https://github.com/henrypp/chromium/blob/master/hevc_support.md ?
If not, would it be possible for you to briefly explain (If you want and when you will have an instant) how you are doing so that other devs (if they want) can learn from your skills?
I confess to also doing this in a personal perspective because I reunite informations to try one day to compile the Holy Grail ➜ Chromium ungoogled version + modified bookmarks + full codecs + Widevine!
We can not let Nik, Rob, Marmaduke and occasionally Squalus forever do all the work!
Sorry for the long post, I will try to be more quiet for the future.
Widevine test page: https://shaka-player-demo.appspot.com
Marmaduke's latest Mac sync stable build incorporates full CODECs (including mpegts) and Widevine support.
Ungoogled is version specific (and tends to lag behind the stable build); and can be difficult to incorporate into DEV builds: there are certain generic patches that can be used.
An "Ungoogled build" can be approximated by the judicious use of flags and plugins.
Mehgan.
No sync • No WebRTC • No Widevine • 66.0.3359.181 (540276) running perfectly, as usual. ;-)
Or Sync • WebRTC • Widevine • 68.0.3438.0
It woulb be great !!!
Please ?
Thank you for the Widevine test page.
I added a line at the beginning of my table with tool-tips on hover ( https://www.murielfrenchcouture.fr/autres/Chromium/codecs.html ) for Widevine tests.
It seem that to get a Widevine / Netflix functional browser you need a SYNC (Dev or Stable) Chromium version and to visit chrome://components to be sure to have latest version of « Widevine Content Decryption Module » (1.4.9.1076 at 2018 may,23)
A Chromium relaunch may be necessary.
Thank to Nik for updated this page to explain how to codecz’ ➜ https://github.com/henrypp/chromium (As an aside, is Nik and Henry++ the same guy?)
Finally I confirm that with a judicious use of flags + µBlock Origin + µMatrix + #extensions you can make a serious privacy browser.
For @Anon344x : don’t fight. I’m actually learning how to compile Chromium and as soon as I success to it I will compile whatever Anons here ask for.
I got a Windows® and a Debian in a VirtualBox but because of the amount of RAM needed I think I will could compile only in Windows®
I try to follow this link ➜ https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
But it’s long because I’m not a developer originally…
I don’t know how to get a « chrome.zip » formatted to match the « chrome-win32 » archive format used by Nik / Chrlauncher ; I don’t know how to make a Sync or NoSync, etc.
To be continued…
Thank you.
Installer
No sync • WebRTC • No Widevine
It's enough for me.
I want just the better optimisation for OS 32bit. 4G Ram on 1G is reserved for the OS.
I can't compile if needed OS 64 bit and 8G Ram
> It seem that to get a Widevine/Netflix functional browser you need a SYNC version .
Yes. WebRTC and sync must be enabled.
> Is Nik and Henry++ the same guy?
No. Henry++ is the developer of chrlaucher and other excellent tools. Nik is a developer of stable/dev Chromium on Windows. He simply uses the Github repository of Henry++.
> I'm actually learning how to compile Chromium
Good luck! ;) You need time and a recent computer (ex: 64-bit OS, i7/i9/Xeon/Opteron/Ryzen processor, 16GB+ RAM, 1To SSD discs).
- Official instructions: https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
- Nik instructions: https://github.com/henrypp/chromium/blob/master/building_chromium_gn.md
- Eloston instructions about "ungoogled-chromium": https://github.com/Eloston/ungoogled-chromium/issues/235
- For more: #source-code
Is your GN.exe arguments page always valid / up to date for Chrome 67 and above?
https://github.com/henrypp/chromium/blob/master/args_gn.md
----------------
Updated Linux build.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v68.0.3440.0-r561577-linux64
I will try to have updated Windows builds tonight or tomorrow. I hit some performance regressions in internal builds, including nearly 15% in Octane 2.0. Pulling a Chromium project build to compare and establish a baseline for regression checking. Fun.
Actually I'm reading the 3000+ lines of gn.exe help flags with in background a Ninja that is compiling with some flags I don't really understand for now but I have seen here in the comments section like :
enable_nacl = false
use_lld = true
use_thin_lto = true
etc.
I ran into a error by trying a #sync version because I set the google use_official_google_api_keys to true without having the google_chrome_api_keys.h file in source…
But in short, like Rob say, it could be fun to try and learn ➜ the problem is that every test take me 6h at 88°C on my old laptop… I now understand why Rob had spoken about his Intel 16 Xeon E5-2690 v4 cores !
I am afraid when will come the time to hack bookmark_bar_view.cc and toolbar_view.cc…
I previously considered 4x10 Xeons for 40 cores with 80 threads, but my Opteron system still is pretty quick building Chromium, so I digressed for now.
Perhaps something like the following to start:
clang_use_chrome_plugins = false
is_clang = true
is_component_build = false
is_debug = false
is_official_build = true
is_cfi = false
symbol_level = 0
remove_webcore_debug_symbols = true
target_cpu = "x64"
use_lld = true
use_jumbo_build = true
enable_widevine = false
enable_remoting = false
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
treat_warnings_as_errors = false
You can add sync, codecs, widevine, etc. later. Get the basic browser working first. :)
You can also add use_thin_lto = true as a a multi-threaded linker, but note you will need to modify a build file to actually enable ThinLTO performance optimizations. Otherwise, even LLD single threaded without ThinLTO is still pretty quick for linking a non-debug build.
If building on a notebook, a cheap notebook cooler with an USB-powered fan could be beneficial assuming you do not already have one. Like $10 to $12 shipped on eBay. I have one under my 17" notebook.
I just success to compile a chromium (68.0.3440.0 - #561474)!
If I run Chrome from with output building folder, it run flawlessly but…
➜ I get the following out folder (at right of the picture) :
➜ Instead of a chrome.zip archive like you and Nik :
And my files (chrome_child.dll, chorme.dll, etc.) are ridiculously little, I missed out something…
I need to invest a little more to know why I don't get un chrome.7z like in your comment #comment-3446
But you are right, a Nik/Rob Archive format first and a race with you at the better optimizations switches 2 ou 3 months later…
The file get the same size as you and Nik !
So it seem I just need to manually zip files (without *.lib ; *.pdb) and test this in a clean environment…
I must work IRL for now but compiling Chromium is not as impossible as it seem ! Thanks to this comments section ;)
That build target will give ya’ a 7z archive and the installer.
If you have time and agree.
Can you compile 32 bit of your 68.0.3440.0 (561732)
Or build what you want.
Thank you so much for your hard work!
I will post a fully step by step « How to compile Chromium on windows » as soon as I get something totally functional.
I take lot of snapshot for the moment…
@Rob,
Thank you for your answers and interventions always relevant and fast!
By manually removing the * .lib, the *.pdb and adding a VisualElements folder as well ; I managed to make a functional portable Chromium folder with exactly the same structure as archives used by Nik / Henry ++ !
I progress slowly step by step as you say, but surely.
------- [1] (Find best GN Args…) -------
- For the next step I'll add Nik's flag « is_win_fastlink = true » that I also found while reading a conversion from GYN to GN.
- Then try your GN args’s list in #comment-3453
- And finally finish by preferring your command « ninja -C out / mybuild mini_installer.exe » .
------- [2] (Add Codecs…) -------
About the codecs I have exactly the same functional as your Clang, Polly or Misc versions but less than Nik version (it has m2ts, 3gp, qt, amr, etc.)
I will see to try the new tutorial that he made for me/us here ➜ https://github.com/henrypp/chromium/blob/master/hevc_support_new.md ; It seem it need some hack in source to get more codecs…
------- [3] (Modify * .cc sources…) -------
Finally, I was able to trace the history of all changes to the bookmarks-bar since last 66.x stable version (https://chromium.googlesource.com/chromium/src/+log/master/chrome/browser/ui/views/bookmarks/bookmark_bar_view.cc , …/layout.cc, …/toolbar.cc, etc.) so I should be able to make changes according to.
I will share my conclusion next week to see if we ended with the same modified files.
------- [4] (API + Widevine ?) -------
For Widevine I need to create an API (https://github.com/DrewML/chrome-webstore-upload/blob/master/How+to+generate+Google+API+keys.md)
I already have a Google account for SEO to use for make this API but I will see if I really need it because I don’t like Sync version (NSA, FBI, WebRTC, Etc.) and Nik already make full x32 & x64 , dev and stable , SYNC , functional versions of Chromium…
For the moment I'm just missing out on how to compile a specific version of Chromium and not necessarily the last source (Fetch chromium version xx.x.xxxx.x instead of fetch chromium)
By the way ; this stuff take a lot of time and I need to by an usb fan as you advice.
But I will quickly automate all of this like Nik seem to do once everything will be functional.
@Nik : you get an API, you know how to hack source for codecs, you make tutorial, etc. Are you a official Google Chrom[e|ium] Dev ?
Edit : D’oh ! Again a long post :( Sorry…
————————
I am working on code bloat to maybe reduce cache+memory pressure for both 32- and 64-bit builds. Some targets are at Os, while hot targets at O3. ThinLTO is at O3, though with a reduction in the function import limit. String tail merging is enabled. The end result is a considerable reduction in overall output size, though a quick run through a couple of a benches show no significant impact.
Causal testing suggests I am still leading baseline (standard project dev build) by around 10% in Basemark Web. YMMV depending on numerous factors, of course.
Big thank you for your 32 bit build.
"For the moment I'm just missing out on how to compile a specific version of Chromium and not necessarily the last source (Fetch chromium version xx.x.xxxx.x instead of fetch chromium)"
These are my Mac (generic) notes for a specific Chromium version: amend for windows.
=======
['release_branch' is an arbitrary name]
cd /volumes/disk1/chromium.stable/Program/Chromium
export PATH=`pwd`/depot_tools:"$PATH"
cd src
[OPTIONAL] git checkout master; <<<<REMOVE AMENDED FILES>>>;git branch -D release_branch
(i)git fetch --tags
(ii)git fetch origin 66.0.3359.181 <<< Version you want to build.
(iii)git checkout -b release_branch FETCH_HEAD
A list of amended files might be shown: delete them, 'git checkout' the files you have just deleted:
@@@EXAMPLE, if previously patched ffmpeg REMOVE: sync will reinstate: @@@
==========
@@@iMac:src bigchocolate$ rm chrome/browser/BUILD.gn @@@ THIS IS AN EXAMPLE @@@
@@@iMac:src bigchocolate$ rm chrome/browser/extensions/api/desktop_capture/desktop_capture_base.cc
@@@iMac:src bigchocolate$ git checkout chrome/browser/BUILD.gn @@@ THIS IS AN EXAMPLE @@@
@@@iMac:src bigchocolate$ git checkout chrome/browser/extensions/api/desktop_capture/desktop_capture_base.cc
@@@rm -rf /volumes/disk1/chromium.stable/Program/Chromium/src/third_party/ffmpeg @@@ IF PREVIOUSLY PATCHED!
>>>>>>>>vi third_party/widevine/cdm/widevine_cdm_version.h
(iv)gclient sync --with_branch_heads --jobs 1
You might have stash errors here: 'git stash' should solve the problem. Re-run 'gclient sync --with_branch_heads --jobs 1' (Skip option to rebase)
https://web.archive.org/web/20181220114253/https://www.opentaps.org/docs/index.php/How_to_Use_Git:_a_Tutorial - documents the 'git stash' command quite well.
(v)Patch code as required
(vi)gn args out/release ...
(vii)time ninja -C out/release mini_installer.exe
====
Chromium is best developed on a multi-processor cpu with hyper-threading. For example an old HP DL380 G6/G7 with dual Xeons and a large amount of RAM (64Gb+) and on a virtual platform such as ESXi 6.7/6.5u2
On average, a "normal" Mac or Windows build takes about 55 minutes. You will soon tire of 6 hour builds!
But, DRM'd content is so common now, it is becoming a problem. I can't watch Hotstar nor Amazon Prime Video. Is there any way I can add a component or something? Is there any way I can make it work?
My build box has 64GB for Windows builds, though my virtualized Linux build box has 32GB and builds okay with ThinLTO and PGO/AFDO.
Looking at something a little more mainstream, I sometimes roll low-priority builds on my Core i5-7300HQ notebook with 16GB of memory.
My operating system is ESXi 6.5u2 (6.7 is not compatible - I'm operating at the margins!) My development machines for Windows and Mac are virtual machines ... I don't actually own a Mac (Hackintosh rules)! I've always detested Apple computers: they lack both form and function; but, the underlying Mach kernel is robust.
Awhile back I picked up a HP DL385 G5 with a couple of K10 Opterons and 32GB memory, which I bought supposedly for building software on Linux, though admittedly right now it is collecting dust. I paid $33 for the base system on a eBay auction and did a local pickup to spare the shipping costs.
----------------
@Aditya Dutt You are going to need a version with Widevine enabled. I suggest a "stable" build as well, as Widevine directly off the development trunk can be a huge question mark on actually working. Nik's stable build should have you covered. :)
Right now I am working on code bloat plus getting a Linux build going.
I should be close to migrating my Linux build from my misc repository to my mainline Clang repository.
Chromium 69.0.3442.0 (Official Build) (64-bit)
Revision bf9a8c37e2e3d447cbfbba77744b01cba170e3fb-refs/heads/master@{#562126}
OS Windows
No Sync - WebRTC - No Widevine - Polly Optimised - lld-link - FullLTO
https://github.com/macchrome/winchrome/releases/v69.0.3442.0-r562126-Win64
Tank you again ; your last 32 bit windows works faster than those before :)
Would it be possible to you to share your changes about the bookmarks-bar? (pastebin or where you prefer)
It's been 4 days that I am doing some tests like edit:
static const int kBottomMargin = x;
static const int kButtonPadding = y;
Etc.
But every time I get or crappy design or compilation errors…
I reassure you, I do not wish to purely and simply copy you, I just need to have at least one functional sample to study from...
It is also, and above all, because I have to wait for a crazy time of compilation after each tiny change and marmaduke saw it very well: « You will soon tire of 6 hour builds! » It seem soon = 5 days ! ;)
In fact, right now, I am looking to run the chromium UI in Visual Studio to see my changes in real time and compile only when the result is satisfactory (https://stackoverflow.com/questions/46078967/chromium-debugging-on-windows-enviroment) ...
By the way : 3 days on your 68.0.3440.0 (561732) - x64 with no crash and not problems of any kind !
Can anyone confirm this?
Thank you for you work guys.
@meconium: Spell check is working here. v68.0.3440.0-r561732-win64. Maybe check (or redo) your Chromium profile directory for a possible corruption.
@sebas: Set to the following flag to disabled.
chrome://flags/#account-consistency
@ChromiumLover: We went through (likely) the same crasher with my builds around the same revision. I am not sure if it was Chromium or LLVM, but it appears to be resolved with my latest 64-bit build, so I am hoping we now should be beyond it. I would think Nik's next builds should be okay.
@Mumu: Here are the quick edits from my notes. Just overwrite the existing variables.
C:\depot_tools\chromium\src\chrome\browser\ui\views\bookmarks\bookmark_bar_view.cc
kHorizontalMargin = 0
kButtonPadding = 0
C:\depot_tools\chromium\src\chrome\browser\ui\views\harmony\chrome_layout_provider.cc
INSETS_BOOKMARKS_BAR_BUTTON = 0, 0
DISTANCE_RELATED_LABEL_HORIZONTAL_LIST = 0
kMaxButtonWidth = 100
Thanks anyway.
Thank for you file. I got approximately the same change.
I will try mine first and post the result in parallel with your for UI result comparison.
Important: You wrong packed « chrome.zip » 68.0.3440.0 (561732) - win32 for your last Clang version instead of ➜ « chrome.zip » 69.0.3445.0 (562445) - win64…
Tweet: https://twitter.com/ericlaw/status/1001477285860560896
"Build Chromium yourself? ICYMI, you need to compile with an API key, or logging into Google sites will give an obscure error message."
Image from tweet:
Source: https://chromium-review.googlesource.com/c/chromium/src/+/1044210
I assume this is logging into most (or all) Google login sites and not just Gmail. I typically use Nik's builds and therefore those have no worries with regard to that since his builds do always contain Google API keys.
Thanks, the workaround works.
thank your for latest 32 bit build.
@Sebas + Anon3483 Welcome. :)
C:\depot_tools\chromium\src\testing\variations\fieldtrial_testing_config.json
Change:
"AccountConsistencyVariations": [{
"platforms": [
"linux",
"mac",
"win"
],
"experiments": [{
"name": "DicePrepareMigration",
"params": {
"method": "dice_prepare_migration_new_endpoint"
},
"enable_features": [
"AccountConsistency"
]
}]
}],
To:
"AccountConsistencyVariations": [{
"platforms": [
"linux",
"mac",
"win"
],
"experiments": [{
"name": "DiceFixAuthErrors",
"params": {
"method": "dice_fix_auth_errors"
},
"enable_features": [
"AccountConsistency"
]
}]
}],
Why not this ➜ https://pastebin.com/raw/Gb55hbg0
Who is equivalent to « chrome://flags/#account-consistency » set to disabled ?
https://chromium.googlesource.com/chromium/src/+/lkcr/testing/variations/fieldtrial_testing_config.json
https://gitlab.collabora.com/web/chromium/blob/0657d7be268ad57cce7c9ea889e8f979d6333fb9/testing/variations/fieldtrial_testing_config.json
6 month old. So your solution seem more robust since we already seen it working in past…
https://chromium.googlesource.com/chromium/src.git/+/de95b29a55c944b2540c43353de3201d7cb7de0f^!/#F3
My latest Win64 build has the change. I will try to push updated Win32 and Linux64 builds tonight or Thursday.
for No sync • No WebRTC • No Widevine • 67.0.3396.62 (550428) • Wednesday, 30 May 2018
*** Pls advice IF this is the LAST GOOD COPY of STABLE w NO webRTC ???
Much appreciated for your time and kindness :) Hv a gd wkend :)
And the other hand you could fit 120 favicons for a full HD screen on this totaly ugly unreadable bookmarks-bar… 😳
No sync • No WebRTC • No Widevine • 67.0.3396.62 (550428) desperately perfect! ;-)
Thanks!
Revision 4f3fe86e6cc61679ecf92bd3670cbf0b885008cb-refs/heads/master@{#563638}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v69.0.3448.0-r563638-linux64
----------------
Rehashing a topic from awhile back, there is an AMD mircocode update available.
https://packages.debian.org/sid/amd64-microcode
Thank you for your time making Chromium with codecs available to us. And thank you everyone for this great site :)
---------------------------
Nik: Hey again Nik! I ran into a rather unusual problem with this build, and only this build. Every previous build I've used from you has never had this happen. When visiting Youtube trying to watch a full screen video causes the image to fullscreen and FREEZE with no control or restoration of video playback. Sound will continue to play but video is frozen. Happen with ALL YouTube videos. I was able to get a full screened video to properly start showing motion and play perfectly by striking ALT-TAB which unfroze the video. But any attempt at exiting the video causes the screen to freeze with a white background with a smaller black square in the top left corner of my screen. I just wanted to take the time to report my findings as this has never happened before. Previous version was flawless. Thanks! :)
---------------------------
Nik: Also I forgot to mention... I can't exit the fullscreen video playing while frozen. I can't navigate away to a new page either. I have to right click Chromium and select close as further navigation is impossible. The screen will not refresh and remains frozen with background video sound playing until Chromium is closed or video ends.
AFFECTED VERSION: ((Sync • WebRTC • Widevine • 69.0.3448.0 (563845) • Friday, 1 Jun 2018))
Thanks for your help!
Only extension I have is uBlock Origin and I already tried uninstalling and creating new profile but still constant random crashes.
Anyone else having this issue?
As for crashes, as for YouTube black Screens it seem we need to blame Chromium devs, not Henry, Nik, Marmaduke or Rob…
So please report these two problems here ➜ https://bugs.chromium.org/p/monorail/issues/list
With as many details and screenshot as you can !
git revert --no-commit 3e5eaae29d310061c0504f7d011f8bb0263e0078
For clarification, I am talking about a workaround for the fullscreen issue. My 69.0.3450.0 Windows builds include the workaround. I will try to push an updated Linux build to GitHub later or maybe tomorrow.
As for heap corruption crashes.... good luck. Been there, done that awhile back. At some point they seemingly just quit happening, so it is likely revision related, but I do not have a good candidate for the actual underlying cause.
Even better. The revision just made it to the trunk, so builders do not need to revert locally now.
https://chromium.googlesource.com/chromium/src/+/554a4b6a90144952665ec035d62fd60faade7412
GitLab tweet: https://twitter.com/gitlab/status/1003409836170547200
(1) :
- µ💲oft who said I remind : https://www.theregister.co.uk/2001/06/02/ballmer_linux_is_a_cancer & Open Source is Cancer too…
- Where there's muck, there's brass…
- https://www.zdnet.com/article/from-open-source-hater-to-no-1-fan-microsoft-now-tops-google-facebook-in-github-contributors/
- https://www.zdnet.com/article/microsoft-completes-its-linux-journey-joins-the-linux-foundation/
Outside of the obvious opportunities for Visual Studio, the company is a large PaaS provider with Azure, which is a key area where GitHub integration could come into play eventually. Export from GitHub to Azure and implement code in the cloud with a few mouse clicks.
BTW, Microsoft also cares little about what OS, be it Linux or Windows, on which you are running your code in the cloud, as long as it is running on Azure.
What could possibly go wrong!
Hopefully, Github will not go the same way as Nokia/Symbian and a 1001 other Microsoft failures.
Laters
Meghan
chrome://flags/#account-consistency --> Set it to disabled or fix auth errors.
I have been going ahead with forcing the default behavior to to fix auth errors in my builds, as it was the previous behavior.
Compiled under macOS 10.14 Mojave beta (18A293u) and Xcode 10 beta (10L176w) - SDK 10.14
This build cannot be guaranteed to work under all Mac platforms, and is not particularly refined.
Chromium v69.0.3453.0.0-r565207-macOS
Chromium for 64-bit macOS - Thursday, 07 June 2018
Chromium 69.0.3453.0 (Developer Build) (64-bit)
Revision 9af34b4853164a8025c9a34cc0aa120203af75d1-refs/heads/master@{#565207}
OS Mac OS X
Sync • WebRTC • No Widevine
Chromium.69.0.3453.0.0.sync.app.zip
https://github.com/macchrome/chromium/releases/v69.0.3453.0.0-r565207-macOS
(Auth errors fixed)
Update to No sync • No WebRTC • No Widevine • 67.0.3396.79 (550428) • Thursday, 7 Jun 2018 (64bit)
So far all GOOD
Much appreciated for all the great work and selfless service :)
Chromium 69.0.3453.0 (Official Build) (64-bit)
OS Mac OS X - macOS 10.14 Mojave beta (18A293u) and Xcode 10 beta (10L176w) - SDK 10.14
[Bootstrapped LLVM/Clang 334178 (Customized: polly, compiler-rt, libcxx, libcxxabi, etc...)]
Revision 9af34b4853164a8025c9a34cc0aa120203af75d1-refs/heads/master@{#565207}
No Sync • WebRTC • No Widevine • ThinLTO • CFI • All Codecs
Chromium.69.0.3453.0.0.nosync.app.zip
https://github.com/macchrome/chromium/releases/v69.0.3453.0.0-r565207-macOS
======
about://gpu functions correctly!: CFI blacklist has been implemented.
HTML5 graphics smooth and vibrant.
10.14 is quite robust for a beta. A classic in the making!
Proof of concept over. Back to normal builds.
Is that expected to happen?
Did I miss something? How can I "fix" it?
Also you can try forcing color profiles to see if there is a difference.
chrome://flags/#force-color-profile
Found an issue with No sync • No WebRTC • No Widevine • 67.0.3396.62 (550428):
Can't connect to Google services (any), tried on a clean profile with no extensions.
No problem with Freesmug's current version. Actually, when I connect thru Freesmug's, close it, open yours, I stay connected. But if I disconnect, I get "Something went wrong" error on my next attempt.
I think this has happened after I've done a "killall cfprefsd" in Terminal when testing some other app a week ago or so... this issue might have been present a long time ago, but you can't suspect it until something happens that disconnects you, I bet.
How does the equivalent sync version behave?
" ... Tried disabling hardware acceleration as a test? Also you can try forcing color profiles to see if there is a difference.
chrome://flags/#force-color-profile "
Both the above suggestions, disabling acceleration and forcing color profile (to sRGB), seem to work fine.
Which one would you prefer?
I thank you very much for your quick, kind and useful answer.
I still have, however, a... technical curiosity: why do you think this new release behaves differently than the previous ones, with exactly the same extensions, settings and so on?
Thanks!
Yes! Disabling the flag did the job! :-)
I've tried downloading the equivalent sync version but it's awfully slow...
I'll try later, if it's useful to you?
It's not necessary to download the Sync version. The "auth errors" issue only applies to the no-sync version.
In my DEV builds I fix the "auth issue" in the code; not so in the Stable build: I prefer that individuals set the approriate flag.
There will be no 67.0.3396.79 stable build - unless that's the final v67 version, after v67 WebRTC will be enabled. I've been more concerned with establishing a Mojave Chromium build system.
Ok. If I understood correctly what you wrote some time ago, v67.x will be the last stable for MacOS 10.9.5?
The Mac Chrome/Chromium releases currently use the 10.12 SDK, which is compatible with OSX 10.9.5. Given Apple's push towards the "Metal 2" architecture, it is almost certain that the Chromium build requirements will change and that OSX 10.9.5 will not be supported.
As long as 10.12 SDK is officially used to build Chromium then OSX 10.9.5 will be supported (and "stable" builds will be produced).
I've produced the Mojave (10.14) builds so that users can assess the preliminary compatibility of SDK 10.14 with the(ir) current OSX/macOS releases.
@RobRich:
My knowledge of macOS is limited to 10.11+
The backward compatibility of Chromium with previous versions of OSX is a function of the Chromium authors' build requirements.
To be honest, my sole concern is that I am reluctant to buy any new computer hardware. The GPU market has been totally distorted by crypto-miners; and the latest crop of CPUs are fundametally flawed. I'm satisfied, as long as my current build system can produce future versions of Chromium.
My color profile, however, shouldn't be "particular" at all, as I never used other themes than the Chromium default one and never changed any of its settings, through all the Chromium releases I've been using.
That's why this sudden... yellow issue with this new release surprises me.
Anyway, I'll follow your suggestion and I thank you again.
It becomes grey after ver 68 I think?
What do to mean by "accent colour" and by "title bar"?
Can you make a screenshot of before and after?
Are you talking about nth’time that Chromium take a ugly decision about UI/ Design?
Prior everything, have you tried RobRich solution :
chrome://flags#enable-color-correct-rendering --> disabled.
And/Or disabling hardware acceleration in chrome://settings at the bottom?
I need some help/precision about your helping tutorial about adding codecs to chromium compilation.
I used pastebin because the comment section here kill white spaces⁽¹⁾ :
https://pastebin.com/JcRKteeQ
Here a pattern to cut’n’paste to save you some time for your reply (if you would)
———————————————————————————
Question 1:
[YES] or [NO Because… … …]
Question 2:
A/ [CHROME] or [CHROMIUM] or [BOTH]
B/ [WIN] or [WIN-MSVC] or [BOTH]
Question 3:
[x64 folder only for x64 && ia32 folder only for x86] or [BOTH]
———————————————————————————
Of course, it’s an open-ended question and if RobRich, marmaduke, WildByDesign or anyone who understand and/or know something, feel free to post!
⁽¹⁾ : Hey Jerry ! What about a secret tag "code" in this comment section without documentation about it that only oldfag will use ?
Just updated to No sync • No WebRTC • No Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018 (64bit)
All good so far - been online for an hour or so
Thanks Jerry too
Much apreciated for your time and great sharing
1) yes
2) in my case it's ___\Chrome\win\___ because gn arg is ffmpeg_branding = "Chrome"
3) if you build x64 then x64, if x86 then ia32
For the moment I was able to find how to customize bookmarks bar height, radius, highlight, spacing, padding, etc. And as soon as I will get every codecs working fine I will post a full step by step pictured tutorial to compile chromium here and/or github .
Thank you Jerry too! Let be honest, we rarely need to write code in this comments section ; but exactly as you mention here #comment-3488 when we will need it, it will be really helpful!
Not like in this line ;)
Yes, ChrLauncher always download the full binary, even if the update is only one word in a translation pack.
And I am pretty sure that ChrLauncher use Jerry API’ to make his update with here the details :
dev-official ➜ The Chromium Authors (dev) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=dev-official&out=json
dev-codecs-sync ➜ Nik (lkcr) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=dev-codecs-sync&out=json
dev-codecs-nosync ➜ Nik (lkcr) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=dev-codecs-nosync&out=json
dev-clang-nosync ➜ RobRich (lkcr) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=dev-clang-nosync&out=json
stable-codecs-sync ➜ Nik (stable) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=stable-codecs-sync&out=json
stable-codecs-nosync ➜ Nik (stable) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=stable-codecs-nosync&out=json
ungoogled-chromium ➜ Nik (lkcr) ➜ https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=ungoogled-chromium&out=json
Note that it’s an incomplete response, I am pretty sure too that the API can retrieve Linux, Android and Mac update and probably order French fries…
More about API ➜ #api
Hi all!
Got a very strange issue here: my PSU died and I transferred my complete MacOS from my desktop hackintosh to a laptop, all is working except for Chromium where all my extensions get cancelled and all my parameters reset... Tried a few times, no way.
I suppose Chromium detects that it's not the same computer and resets everything.
Is there anything I can do?
Previous Chromium settings will be at:
~/Library/Application Support/Chromium
If the original values were not backed up (or over written) then you will have to manually reset them, and re-install your plug-ins, which ideally should be all in a specified folder.
You can approximate a Mac portable install (ie, changing the user directory) by following the instructions at:
https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md
Yes that's the folder. The original is intact — only Chromium has not been closed properly because of the PSU failure.
I've tried the instructions of the link you gave, creating this script:
set chrome to "\"/Applications/Chromium.app/Contents/MacOS/Chromium\""
set userdatadir to "\"/Users/Myself/Chromium\""
do shell script chrome & " --user-data-dir=" & userdatadir & " > /dev/null 2>&1 &"
(and putting my backup profile folder at /Users/Myself/Chromium/Default)
It starts but wipes out the profile all the same...
I'm not sure I understand you well when you say "if the original values were not backed up (or over written)", sorry — (I'm French...): I have also tried using a clean backup from two weeks ago (with Chromium closed properly), same result.
Do you mean using Chrome Sync feature?
Isn't there a way to recover things in a situation like this? It seems amazing! :-o
On this aspect, Firefox is much easier to deal with, you copy profiles here and there with no fuss... :-(
I learned that the hard way as well. I did a backup of my Chromium profile (located at AppData) and formatted my computer. Once done, i went to the AppData folder again as put it there. Chromium did open but the profile was broken. I then searched Google and apparently Chrome stores/encrypt his stuff along with Windows (using CryptProtectData function). In other words, since it's not the same Windows user it doesn't work as it stores needed data on a user account level.
On a correctly functioning Chromium, configured to your particular requirements, go to chrome://version and make a note of the "Command Line". Store your unpacked extensions in a directory, and when/if required manually reload them. If the original data directory has not been corrupted then any extension used should be configured and work.
I know that my instructions are terse. But it is for the user to mitigate against any potential data loss.
I run Chromium for Windows as a "PortableApp", which can be moved from computer to computer with the profile intact; with the exception that any extensions used have to be reinstalled. Not ideal, but it works for me.
By the way, I see that it is about the same for any chromium based browser: Opera and Vivaldi also lost their extensions...
I'm wondering: if I run Chromium through VMware Fusion, I suppose I could bring the VM on any Mac I want? (except for the loss in performance...)
Revision 26e766991a4fed6c1f6b1b1a43ccfdc1ea1ab9e4-refs/heads/master@{#567896}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v69.0.3463.0-r567896-linux64
I have the latest version of Chromium portable open and running (it's not the default browser in my system).
I've instructed a few programs to open links in Chromium via command line.
What happens is, the links from those programs get opened in a tab at the end of the current open window (intended behaviour) but there is also a second window with an empty tab opened (unintended behaviour).
Is there anything I can do so that the second, unnecessary window is not opened each time?
I have exactly the same problem since 4 or 5 years now... I have tried everything :(
I managed once to restore normal behaviour by half destroying my registry (deleting all registry keys chrom*, deleting all URL link default open, browser...) and applying a hacked BAT.
In short, I managed once to make it worked normaly, but only for a short time anyway because I broke it again as soon as I forgot to untick 'use as default to open' by opening a webm file.
This message will not offer you any help, but bring you compassion: you're not the only one with this problem it seem and I think it's almost impossible to solve it...
Sorry for us :(
But I will try to investigate again on a Virtual Machine to not detroy my system again...
tbh though, it doesn't bother me too much, i've gotten used to it
So if anyone has an idea where to start looking or how to fix this, please comment!
The Google login, error 500, will probably come back because your hack is no longer applicable.
Chrome’s monkeys removed the « AccountConsistencyVariations » var in « …/testing/variations/fieldtrial_testing_config.json »
See here : https://chromium-review.googlesource.com/c/chromium/src/+/1088612
But I’m not sure we need to hack something anymore because I remember seeing something about "only enable M2 if API Key is present" to avoid error 500 about build without API Key…
how says @Mumu tries to clean the record with chrome chromium entries or the extension that has assigned
use nirsoft regscanner and it is quite fast and comfortable
I hope it helps you
(I'm sorry I'm using translator)
https://pastebin.com/fQcPu3jS
Like if I do a google search, then try to immediately click on the first link or scroll, I have to wait till the little circle in the tab finishes spinning and the favicon shows, then all the scrolling and clicking executes all at once =/
Was fine with the last release, only started happening with this one.
No sync • No WebRTC • No Widevine • 67.0.3396.99 (550428) • Tuesday, 26 Jun 2018 (64bit)
All Good :)
Thanks Jerry for this great site
@Marmaduke,
Hello to both of you !
I still have some difficulties to compile a Chromium as perfect as yours !
I noticed that on the Jerry’s codecs test page : https://tools.woolyss.com/html5-audio-video-tester
Your compiled versions of Chromium run more or less all audios and videos formats⁽¹⁾ possible !
I understand that we can activate a lot of codecs by using GN ARGS with for example :
# Add Proprietary Codecs ➜
ffmpeg_branding = "Chrome"
proprietary_codecs = true
# Bonus ➜
enable_ac3_eac3_audio_demuxing = true
enable_hevc_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
enable_widevine = true
rtc_use_h264 = true
use_openh264 = true
# etc.
We can go even further by following the Nik’s tutorial⁽³⁾ that seems to enable the H.265/HEVC.
However nothing to do : I can never get as many formats as you two !
You both also have for example: M2TS / 3GP / AVI / QT / AMR / ...
I have tried all imaginables solutions until completely copy byte for byte⁽²⁾ Nik’s tutorial⁽³⁾ and Nik’s GN arguments⁽⁴⁾ but nothing to do : I can’t manage to have as many videos and audios format⁽¹⁾ as Nik or Marmaduke !
And I don’t know where to start to investigate right now...
-----------[NOTE]-----------
(1) : https://www.murielfrenchcouture.fr/autres/Chromium/codecs2.html
Column 1 to 4 ➜ Nik
Penultimate column ➜ Marmaduke
Last column ➜ My test
(2) : https://www.murielfrenchcouture.fr/autres/Chromium/Rapport.html
(3) : https://github.com/henrypp/chromium/blob/master/hevc_support_new.md
(4) : https://github.com/henrypp/chromium/blob/master/args_gn.md
----------------------------
Warning :
Do not link any link in this message: it’s a draft version for now!
I would make a clear and clean tutorial as soon as I get everything functional !
- Hate the new UI
- Translate languages from X to English has stopped working.
I'd like to go back to 61 or something in between that's got the Old UI as an option and Translation works.
Please advise.
PS: I just noticed that I was trying out one of the Chromium Updater tools and it seems to have taken it to:
Version 69.0.3475.0 (Developer Build) (64-bit)
PS: For the above points on Chrome Profile User Data this would be a good place to get insights and share back experiences/ fixes.
https://superuser.com/questions/951095/understand-structure-of-chrome-user-profile-data-to-transfer-to-new-pc-os-avo
Of course, thanks to Nik obviously for his tutorial about HEVC/H265.
To get more codecs I simply merged in folder « …\third_party\ffmpeg\chromium\config\ » the Linux-x64’s folder from ChromeOS with the Win-x64’s folder from Chrome with obviously adapting some Linux/Windows differences.
I now have Chrome’s-brand codecs AND ChromeOS’s-brand codecs ( https://support.google.com/chromebook/answer/183093 ➜ see Codecs Section ) for my Chromium binary.
While waiting for a clean tutorial I push here my raw modifications for RobRich and most impatients programmers who would like to seek for inspiration:
https://www.murielfrenchcouture.fr/autres/Chromium/Rapport2.html
With GN’s arguments for codecs:
# … … …
current_cpu = "x64"
target_cpu = "x64"
# … … …
ffmpeg_branding = "Chrome"
proprietary_codecs = true
# … … …
is_component_ffmpeg = true
enable_ac3_eac3_audio_demuxing = true
enable_hevc_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
enable_widevine = true
# … … …
There is now only the format « .M2TS » that I don’t master for the moment to equal the masters.
I should also try to add the H263 codecs to absolutely have all the videos that play on Jerry's test page: https://tools.woolyss.com/html5-audio-video-tester
More codecs would overload and slow down binary unnecessarily for real world usage (Youtube, DRM, NetFlix, Streaming …)
For the video: https://tools.woolyss.com/html5-audio-video-tester/?u=https://www.elecard.com/storage/video/140626_av1_720p_850kbps.webm I think the problem comes from the source because it doesn’t work with strictly anything ! Not even Iron Browser, Opera, IE, Firefox, Advanced Chrome, etc. Jerry, I invite you to keep an eye on it.
Thanks to Nik and Marmaduke for the codecs, Rob for the bookmarks-bar change & the Google dice error 500, Jerry for this platform, the API, etc. and last but not least Henry++ for the Chromium’s portability and all the anons for their contributions in comments section here.
I have an old PC and a lot of work IRL but I take notes and screenshots of each step to make a page « Compile Chromium for Dummies » when everything will be functional.
third_party\ffmpeg\ffmpeg_generated.gni
"libavformat/mpegts.c",
demuxer_list.c
&ff_mpegts_demuxer,
Thank you Juan Guillermo for your message 👍, I will try this right now !
Are there still others codecs specialists hidden in the anons? ;)
Seem there is no error with https://tools.woolyss.com/html5-audio-video-tester/?u=https://www.elecard.com/storage/video/140626_av1_720p_850kbps.webm , the problem is only that this codec is too recent… I will try to embbeding it also…
@Dan why not try github ?
Henry++ / Nik ➜ https://github.com/henrypp/chromium/releases
Rob ➜ https://github.com/RobRich999/Chromium_Clang/releases
Marmaduke (windows©) ➜ https://github.com/macchrome/winchrome/releases
@Anon3583: Marmaduke, Rob or Nik don’t seem to need any help: they already full masterize Chromium’s compilation. I will release soon a full step by step tutorial for beginner like us about compile Chromium on Windows and you will probably be able to compile your own version too. It’s not that much difficult, the problem is that is take lot of time, space, CPU…
@mumu: Right. AV1 is a new codec. There is currently no MIME type. I add it just for fun! ^^ Contact me via email if you want. I speak the same native language as you. ;)
The second entry here : https://github.com/RobRich999/Chromium_Clang/releases → 69.0.3472.0-r569934-win32
This 32-bit release is 6 days old.
Latest release
v69.0.3472.0-r569934-win32
aa1a96c
@RobRich released this 6 days ago · 1 commit to master since this release
I do not know who you are. I do not know what you want [...] But I will find you, and I will hug you!
The changes you proposed me here: #comment-3587 work perfectly!
My build can now also read .M2TS format !
So I'm tied with Nik and Marmaduke for playable codecs and videos on: https://tools.woolyss.com/html5-audio-video-tester
---------------------------
Beneath the euphoria I have wanted to add AV1 and H.263 support imitating your changes...
AV1 (ERROR)
█ https://tools.woolyss.com/html5-audio-video-tester/?u=https://www.elecard.com/storage/video/140626_av1_720p_850kbps.webm █
★ #define CONFIG_LIBAOM_AV1_DECODER 1 ➜ (config.asm / config.h)
★ third_party\ffmpeg\ffmpeg_generated.gni ➜ ... ... « libavcodec/libaomdec.c » ... ...
★ codec_list.c ➜ &ff_libaom_av1_decoder
But of course it's not that simple. There are dependencies for a folder « aom » in « libaomdec.c »
I tried to raw-copy this folder in ffmpeg and modify the include but I have missing symbols errors... It is probably missing stuff to add in « ffmpeg_generated.gni » ...
So I confirm that to get AV1 support we will need all Eastern Europe help and woke up Slavs agents @Nik and @Henry++ !!
H.263 (ERROR)
█ https://tools.woolyss.com/html5-audio-video-tester/?u=techslides.com/demos/sample-videos/small.3gp █
★ #define CONFIG_H263_DEMUXER 1 ➜ (config.asm / config.h)
★ third_party\ffmpeg\ffmpeg_generated.gni ➜ ... ... Nothing ?!
★ demuxer_list.c ➜ &ff_h263_demuxer
Same-same but different : symbol error.
I have to find one or more stuffs to add in « ffmpeg_generated.gni » or worse...
---------------------------
I wanted to drop a Beta version here with this comment for real-world users to test my build in Google, YouTube, Facebook, Twitter, NetFlix, Twitch, etc. but in the meantime the new Chromium UI (Material Design refresh) has become Chromium's standard ! Yuck !!
So all my modifications on the bookmarks-bar to mimic firefox’s bookmarks-bar are now obsolete, offset and ugly!
I understand better @XM AX now...
I just have to figure out how to force the flag « chrome://flags/#top-chrome-md » on « Normal » : a bit like RobRich does it here #comment-3572 to force « chrome://flags/#account-consistency » on « Enabled Dice (fix auth errors) » ...
I will make a bisection and I'll be back in a week hoping to finally could release a Beta version!
Thanks again @Juan 💋 and to all the others for their contributions of course!
AV1
&ff_libaom_av1_decoder
%define CONFIG_LIBAOM 1 **** CHECK/TRY *****
%define CONFIG_LIBAOM_AV1_DECODER 1
https://www.ffmpeg.org/doxygen/4.0/globals_vars_f.html
ff_libaom_av1_decoder : allcodecs.c , libaomdec.c
libavcodec\libaomdec.c
libavcodec\allcodecs.c
H263 (small.3gp)
Such mind numbing tedium is for the Chromium developers. Nik says that he has tried, and Marmaduke appears to be not particularly concerned.
Missing dependencies can be found (then incorporated into ffmpeg_generated.gni) by using "grep -rl" or by using the text search facilities of "Filelocator Pro" (or even Windows text search); my preferred tool is grep.
@Mumu
The learning curve is steep, but the plateau is constant.
Juan is busy plotting the demise of the England football team. As long as Raheem Sterling continues to misfire, Harry Kane will be my next recruit.
I surely will suggest browsing this site to some friends of mine who might find fascinating this unpretentious, powerful and pure browser.
You wrong packaged the x64 version « v69.0.3479.0-r571797-win64 » for the x86 (32 bits) version ➜ v69.0.3479.0-r571797-win32 on your Clang Channel (https://github.com/RobRich999/Chromium_Clang/releases)
Thank you for the feedback.
I've implement AV1 in one of my private Mac builds and have had partial success: https://www.elecard.com/storage/video/140626_av1_720p_850kbps.webm does not play, but Chromium's https://chromium.googlesource.com/chromium/src/+/master/media/test/data/bear-av1.webm when dragged and dropped plays.
Chrome's intention is to include AV1 with stable desktop v69; when they have implemented the bitstream. I'll leave the heavy lifting to the Chrome developers.
I would release this development build, but am having problems with Chromium's crap Material Design refresh. I don't know if the Mac Chromium build requirements have changed, or if it is just a bad build.
[EDIT by Jerry: bad link changed]
I have to admit that I loose my mind with this AV1 codec and I think I will give up for now about support it in my future build and wait that everybody sing from the same song sheet…
https://tools.woolyss.com/html5-audio-video-tester/?u=https://github.com/chromium/chromium/raw/master/media/test/data/bear-av1.webm
But you right, the latest build also support the widevine.
Sync • WebRTC • No Widevine • 70.0.3506.0 (578936) • Sunday, 29 Jul 2018
I think it was on ver 68
can you kindly put the link back ? Thanks and much appreciated :)
Anon3711: Because they do not exist any longer. This is now deeply integrated into the Chromium source base.
As of Aug 1st 2018, this browser is now telling me that all my sites I visit that include email or messages, websites that work PERFECTLY in other browsers, are now not secure and I can no longer access them. This even includes ebay, BT, BT mail, etc..
From Youtube videos not playing properly, or giving my quality settings, to media not working on websites across the net. This Chromium browser has just got so bad it's not worth using anymore.
@Dustyn Netflix most likely goes back to Microsoft Silverlight if it does not find WideVine and also because of this it maybe limiting higher resolutions 2160p, 1080p (idk how much they would block in such a case)
Sync • WebRTC • No Widevine • 70.0.3506.0 (578936) • Sunday, 29 Jul 2018 --> No Widevine Confirmed
In your case, I am sure you use a development version which can be very unstable. Prefer a #stable-chromium-version with all codecs enabled.
The source code of Chromium is used in many big software (Google Chrome, Opera, Vivaldi, Skype, Spotify, Steam, Minecraft, WhatsApp, Twitch, Android WebView, Microsoft Visual Studio Code, Electron, CEF, https://en.wikipedia.org/wiki/Chromium_Embedded_Framework#Applications_using_CEF). Moreover, near Mozilla Firefox, Chromium is the main web browser on the biggest Linux distributions like Ubuntu, Linux Mint or Debian. Note Firefox also uses few parts of the Chromium source code (sandbox...). Why? Because it is secure and solid (https://www.chromium.org/Home/chromium-security/brag-sheet).
So, there is no paranoid browser. There are paranoid users. If you hate Chromium, I can understand. Your best choice should be Safari on MacOS ; or Midori on a Linux distrib. There are too much software using the Chromium source code on Windows OS ^^
Last summer Google and Mozilla (and since, Apple) announced they would phase in distrust of certificates issued by Symantec (and a few other root CAs). Version 70 of Chrome/Chromium drops support for *all* affected legacy certs with no workaround in the browser.
See:
https://knowledge.digicert.com/solution/SO29611.html
https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html
https://blog.mozilla.org/security/2018/03/12/distrust-symantec-tls-certificates/
https://support.apple.com/en-hk/HT208860
*****
Another site to test Widevine: https://demo.castlabs.com/ (test the ones labeled DRM)
Widevine works in nik's latest dev/lkcr 64-bit build (70.0.3506.0 (578936)).
for the special "No sync • No WebRTC • No Widevine" links
Unfortunately there is no good way around the webRTC issue to date so we are stuck w those ver.
Thanks for maintaining the site - You do great service and work here. Much appreciated :)
Hv a gd wkend
@earthsound: Interesting info.
@Anon3617: Corrected.
@Anon3618: There is a way! Use a VPN with strong encryption for your whole OS or router. A few web extensions like uBlock Origin or ScriptSafe can also help you.
So the new URLs are:
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=win32_rel/
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=win_rel/
@fzy: A big thank you. I updated the whole site.
DEV releases: https://chocolatey.org/packages/chromium → broken.
Check "legal\VERIFICATION.txt". Their updater uses old folders (Win_x64...)
STABLE releases: https://chocolatey.org/packages/chromium-stable → broken.
Check "Version History". Their updater does not update.
Please comment on a possible workaround for NET::ERR_CERT_SYMANTEC_LEGACY
#comment-3720
But it's been 11 days since last dev builds, is there anything blocking new releases or are you on vacation or something?
https://chromium.woolyss.com/download/
I've noticed that! I'll investigate. Hopefully, the resizing problem will be solved by by dev build 70 - my next intended (DEV) build.
Stable build 67.0.3396.XXX will be the last build with no WebRTC: I will build the last revision.
Revision 74ff2c231069c5746724df6f4f1e1c93fcac991e-refs/heads/master@{#575161}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v69.0.3492.0-r575161-linux64
As I understand it Chromium does not auto update from one stable version to the other automatically.
For me this is the only reason why I will not install it yet.
However, as soon as this is implemented I, and I believe many many others, will !!!!
@Jan van Westland: i doubt it, but you can use chrlauncher
I had that issue after upgrading to 67 and had no idea how to fix it. tried everything, even new profile. just used gmail in incognito for a while but that was annoying.
for some reason the google sign-on "challenge" (captcha maybe?) returns a 401 response and fails to sign in.
can confirm that switching to sync build makes it work again
I think it has something to do with chrome://flags/#account-consistency
Disabling it fixes the login issue.
On the github releases pages, widevine isn't mentioned but I see that v69.0.3470.0-r569821-win64 has it and I can play Widevine protected content.
Thanks!
Back to nosync for me!
However, I come back with a Beta version!
Warning : x64 only for Beta-test…
Nothing better than Rob, Nik or Marmaduke it's just a version adapted to my preferences that I share:
It get in particular:
1/ A compact bookmarks bar between Rob appearance and Firefox style.
2/ Normally no error to connect to Google, Youtube or Alphabet-like accounts.
3/ Full codecs:
a/ Widevine in theory works: be careful to check/update it before in « chrome://components » (Widevine Content Decryption Module - Version: 1.4.9.1076 - Search for updates)
b/ The recent AV1 codec will only work after « Enabled » it in « chrome://flags/#enable-av1-decoder »
4/ The default classic appearance. But it is possible to force Material Refresh (Yuck! Sic!) into « chrome://flags/#top-chrome-md »
5/ The old classic New Tab page.
So I'm looking for Beta-testers to check :
α/ That Netflix, Youtube, Twitter, Spotify, Google, Deezer, Facebook and so on that I don’t use works without errors…
β/ That all videos found on the Net are playable…
γ/ That the default appearance of the browser and the « new tab » page are in classic style by default under Windows 7, 8.1 and 10.
If everything works flawlessly for everyone I will put an online tutorial with all sources/changes I made so that anyone can compile the same browser as this one or copy only part that interest them (bookmarks, codecs, Classic UI, etc.).
If there is a problem, thank you to tell me here what wrong that I add it to my need-to-repair list.
So here we are :
Chromium 69.0.3496.0 (Official build) (64 bits)
Révision 7e9fce12dabda70dab7b51b1f7d4c5143e3a1736-refs/heads/master@{#576093}
« chrome.zip » compatible version with Nik / Henry++ format ➜ https://www.murielfrenchcouture.fr/Chromium/chrome.zip (78,5 Mo)
« mini_installer.exe » version ➜ https://www.murielfrenchcouture.fr/Chromium/mini_installer.exe (45,7 Mo)
Note: I did not invent anything it is a compilation of all the advice I received in the comments section here and everyone will be thanked by (pseudo)name in the future tutorial with my alpha / official version.
Note²: Do not hotlink, this is a temporary-link-hosting for this Beta version while waiting to open a more serious Github or give everything to Rob, Jerry, Henry++ and/or Nik.
I hope, issue get fixed with new version from chromium.
In the words of Burning Spear: "It is good when a man can think for himself"
I've tested your build (apart from Netflix - Blaise prefers NetTorrents! Luke Cage in 4K is a delight.) and everything appears to be OK. Looking forward to the tutorial so that I can incorporate some of your features into my build.
I've always found Nik, RobRich and that rather cantankerous Novichok addict Marmaduke to be quite generous with their advice: IF individuals are willilng to make an effort.
Blaise
Youtube, Twitter and Google works fine from scratch. Netflix and Spotify works after go to chrome://components and update "Widevine Content Decryption Module" like you mentioned.
I don't use Deezer so can't test. Same goes for Facebook.
The default appearance of the browser is the classic style, no new modern stuff.
Bookmarks also have the compact view, even more compact than Rob's builds.
Will test further.
Appreciate your efforts :)
It seem there is not too much errors except with automatic translation that seems to be dependent on « sync » or « no-sync » version.
I must investigate this point.
The purpose of my future tutorial is not to give the changes that I made without explanations but to provide some advice for anyone that want to build their own Chromium to choose and understand what they want to do or not. (to choose for example bookmarks bar’s height, margin & padding, color ; widevine or not, sync or not, etc.)
That permit also to everyone to participate as Nik, Rob, Marmaduke and Juan Guillermo Cuadrado Bello for example which had help me to build this.
Soon, we will succeed in making our own Open-source Chromium only between us without being forced to apply disgusting and ugly changes imposed by Google ;)
I'm a bit slow at the moment because I have lots of stuff to settle IRL in addition to holidays, but we'll get there !
Side note - what do others think of the UI refresh coming? I think it is an awful direction to move towards - hopefully there will be a way to stick to the old interface.
Dev version 70 has been released; so, before I update my build system, i am building stable version 67.0.3396.99: this will be the last build without WebRTC.
I've been watching the World Cup (Kante is the engine of the French squad); drinking 35 year old Scotch; embarking on long walks; and "marvelling" at the "stable genius" that is Donald Trump; God help us all, Vladimir's bum-chum has his finger on the Nuclear Button. I apologise if I've offended anyone. In my defense I "misspoke".
Special thanks to Juan, Blaise, Raheem "the headless chicken" Sterling and Neymar - for his idiotic rolling
around.
I quite like the new look!
====
Chromium for 64-bit Windows - All Codecs - Saturday, 21 July 2018
Chromium 70.0.3499.0 (Official Build) (64-bit)
Revision ac0219786ac3b226f806c33445b253abd9a93e82-refs/heads/master@{#577080}
OS Windows
No Sync - WebRTC - No Widevine
https://github.com/macchrome/winchrome/releases/v70.0.3499.0-r577080-Win64
chrome://flags/#ntp-backgrounds
chrome://flags/#one-google-bar-on-local-ntp
chrome://flags/#ntp-ui-md
chrome://flags/#doodles-on-local-ntp
chrome://flags/#ntp-custom-links
chrome://flags/#ntp-icons
Manually set the flag for now. Fix auth errors or disabled should work okay.
chrome://flags/#account-consistency
Chrome 68 Stable has been published, just received the update...
And.. they changed the spacing between items on the bookmarks bar... AGAIN? They've just done this with v67, I think.. what is going on?
Please, I know you are the experts for this, is there something that can be done about this? At least to get the old 67 spacing back?
Some setting, or configuration flag?
@Anon3672 AFAIK, there is not a quick fix. I am changing values in the source code for bookmark spacing and width for my builds.
Is "No sync • No WebRTC • No Widevine • 67.0.3396.99 (550428) • Tuesday, 26 Jun 2018 " the LAST copy of NO WebRTC?
From v86 forces complusory WebRTC now and CANNOT be removed?
or is nik still trying to make a v68 WITHOUT WebRTC pending release later?
Thanks for your time and sharing
@RobRich: Thanks for the answer... Not the answer I hoped for, but not really surprised to be honest. Apparently, changing the values in the source code is the only solution.
About sync or nosync: there is a flag in chromium to switch on and off it
READ the DETAILS - https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address
It is possible to reduce WebRTC's imapct by using a combination of gorhill's uMatrix/uBlock and ScriptSafe:
https://browserleaks.com/webrtc:
RTCPeerConnection ✔ True
RTCDataChannel ✔ True
ORTC (Microsoft Edge) × False
IP Address Detection:
Local IP Address n/a
Public IP Address n/a
IPv6 Address n/a
WebRTC Media Devices
Device Enumeration × False
Has Microphone × False
Has Camera × False
Audio-Capture Permissions × False
Video-Capture Permissions × False
Media Devices n/a
Height of bookmarks bar in last versions just kill my eyes...
(they still use DTSDK 10.12, though, but even modifying the info.plist is not enough — it launches but no site can be displayed...)
I guess I'll have to stay with the last 67 build, for the time being.
Quite surprising: Opera 54 still works perfectly, just by changing LSMinimumSystemVersion in the info.plist! ;-)
Thanks, everybody, it's been a nice ride! :-)
I suppose you'll say that there's no particular benefit using that 68 dev build instead of the 67 stable, or is there?
Sync • WebRTC • No Widevine • 70.0.3506.0 (578936) • Sunday, 29 Jul 2018
The Chromium authors set the standard, a poor one one would say, for example, the inabilty to disable WebRTC. Apple is not much better with Mojave and its deprecation of OpenGL.
I still use Firefox 56.0.2; just use a browser that you feel comfortable with.
About Firefox, I'm really satisfied with Waterfox that I've been using all this year, it's FF56 with updates and no telemetry, I suppose you've heard about it. Chromium is faster, but I balance my browsing between both.
Thanks again! :-)
Sync • WebRTC • No Widevine • 70.0.3506.0 (578936) • Sunday, 29 Jul 2018
I'm was just being curious about the hold up.
By the way, the command apt-get (on Linux Ubuntu & Mint) is deprecated, now is only apt .
So, instead of:
sudo apt-get update
sudo apt-get install ...
It's better:
sudo apt update
sudo apt install ...
----------------
@Evan No-sync builds are actually builds without Google API keys included, so you can create and deploy your own #google-api-keys if desired.
Revision 7c36083d762cfc04d161e605c29bb95229a0bb7e-refs/heads/master@{#582315}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v70.0.3519.0-r582315-linux64
@RobRich, Nik and Marmaduke: Also a big thanks for your work and support! ;)
@RobRich: I am testing your build on Linux Mint 19 (https://i.imgur.com/NBjambG.png). No issue found for a basic using.
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win_x64/
Not sure if the new links were just for experimenting, or if they will now jump to and fro:
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=win32_rel/
https://storage.googleapis.com/chromium-browser-snapshots/index.html?prefix=win_rel/
@Jerry: https://chromium.woolyss.com/download/ is no longer updating since August 10th, why ?
Chromium 70.0.3528.0 (Official Build) (64-bit)
Revision 2ced14c361a8a8d7c8f3d584d6ed4a6d8fbc84c2-refs/heads/master@{#584334}
OS Android 64-bit
- only for Android 64
- official build
No Sync • No Widevine • ThinLTO
Chromium_Android_64.zip
https://github.com/macchrome/droidchrome/releases/v70.0.3528.0-r584334-And64
target_os = "android"
target_cpu = "arm64"
is_debug = false
symbol_level = 1
is_component_build = false
is_clang = true
ffmpeg_branding = "Chrome"
proprietary_codecs = true
is_official_build = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
====
I'm not a fan of the snapdragon "toolchain": it is not plug and play; and too old!
« Additional CODECs, privacy improvements and optimisations » is already a must for Android’s users (x64 ARM V8)
Are you going to follow this build ? I of course don’t ask for nightly’s builds but an update once a month would be great !
HEVC/H265 is now working. Will post an update when other additional CODECs are working.
In the future, I plan to do "monochrome" builds of Chromium that will only be compatible with 64-bit Android Nougart and above.
---------------------------
Chromium 70.0.3528.0 (Official Build) (64-bit)
Revision 2ced14c361a8a8d7c8f3d584d6ed4a6d8fbc84c2-refs/heads/master@{#584334}
OS Android 64-bit
- only for Android 64
- official build
No Sync • No Widevine • ThinLTO • Additional CODECS
Chromium_Android_HEVC_64.zip
https://github.com/macchrome/droidchrome/releases/v70.0.3528.0-r584334-And64
HEVC and some others! still a work in progress.
Will try this ChromePublic3.apk on a xiaomi Mi A1 on Android Oreo 8.1.0 Arm64v8 in official browser.
Thanks!
Bookmarks bar shows up empty
BTW, I should have new builds out later today. :)
@Evan: Appears so.
NONE of theese versions allow actual extensions portability without Google Account and ALL of them produce registry entries.
Revision c55c24524f098da7de402c6f6a891d09f85d5ba3-refs/heads/master@{#586166}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v70.0.3534.0-r586166-linux64
Likely requires libc 2.8 or later, as I updated the build environment to Lubuntu 18.10 including proposed updates.
Many current Debian/Ubuntu-based distos still are using libc 2.7, so YMMV.
About current stable version (68.0.3440.106): why no "No-sync" build?
Many thanks
@Alex: Yes, we know that Chromium is not fully portable. This is a feature of Chromium and all Chromium-based browsers (Google Chrome, Opera...). There are #secure-preferences on all plateforms except on Android and iOS. Chromium protects its user preferences using a hashing mechanism (HMAC SHA256). The only ways are to use the Sync option or to reload each extension. In short, extensions, certificates and passwords are not portable. However, it is possible to change these features in the Chromium source code and recompile it to make your own browser. But the task is not easy! ;)
> To convert a "Sync" version into a "No sync" version, just
> change #google-api-keys → setx GOOGLE_API_KEY "false"
So I need to set environment variables on my machine, right (goodbye portability? Maybe it's better use "set" instead "setx" so the var is temporary)?
Thanks
chromium vs chrome android
What's the difference between the two versions?
How much is chrome added funtion?
for android I use a Chromium version builded by Brave Software.
This version has, to difference than Google, an Adblock and it use DuckDuckGo (search engine) for private search (but You can change search engine).
Details on Google Play at this page https://play.google.com/store/apps/details?id=com.brave.browser
Remember that it has not a tool for translate web pages.
I notice that my taskbar is occasionally flickering when I use that build, go back to 70.0.3518.0 and it goes back to normal again.
I'm using @Nik's build and my OS is windows 10 though.
Also Chocolatey package moved to https://chocolatey.org/packages/chromium half a year ago.
Revision b1a9183dd954533f233fe3fa51f88bc96b72b257-refs/heads/master@{#589005}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3544.0-r589005-linux64
Please note libc 2.8 or later likely is required.
Chromium for 64-bit Windows - All Codecs - Friday, 7 September 2018
Chromium 71.0.3546.0 (Official Build) (64-bit)
Revision 9f87a1ee823c8bf185dfdde265e457c2cc668191-refs/heads/master@{#589421}
OS Windows
No Sync - WebRTC - No Widevine
chrome.packed-71.0.3546.0.-20180907.7z
https://github.com/macchrome/winchrome/releases/v71.0.3546.0-r589421-Win64
===
Standard build.
Attemped a build with "thin_lto_enable_optimizations = true" and "use_thin_lto = true" the package is larger, but no LTO cache was produced, and the build command line suggests that ThinLTO is not invoked.
On a related note, building with ThinLTO on Windows should be fixed for LLVM 8.0.0 trunk as of revision 341585.
https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/
https://bugs.chromium.org/p/chromium/issues/detail?id=880513
Thank you all for info, report, feedback and other.
@Anon3755: It was a display issue. Sorry for the inconvenience.
Revision e92f4a575519fe408146ba41a09b2eb5c4d4384d-refs/heads/master@{#590832}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3551.0-r590832-linux64
Rolled backwards to building on Xubuntu 18.04.01 against libc 2.27, so it probably will run on most *current* Ubuntu, Debian, and similar distributions.
https://github.com/Eloston/ungoogled-chromium
Privacy matters mostest
https://www.youtube.com/playlist?list=PLyqf6gJt7KuHBmeVzZteZUlNUQAVLwrZS
===
@Byron Swift
ungoogled-chromium tends not to be congruent with the current "stable" build of Chromium.
If, I have enough space on my development environment (actually, I have more than enough storage, but can't be bothered to go the server to install it!) the intention is to do an ungoogled mac build with Codecs.
I've been studying the ungoogled build process and am intrigued by the size of the actual build environment.
Is there any particular reasons about why you don't build the chromium with the codecs?
Sorry, if you had been asked this before.
https://xlab.tencent.com/special/spectre/spectre_check.html
To add the tap, simply do (only once):
brew tap cpbotha/marmaduke-chromium
To install the cask, do:
brew cask install marmaduke-chromium
To update this installation later, do:
brew update && brew cask upgrade marmaduke-chromium
About that Spectre browser test, I just ran it with 64-bit 71.0.3551.0-r590835 on two different systems.
My Intel Kaby Lake system with hardware Spectre mitigation and Chromium site isolation enabled passed. Running Chromium and the test.
My AMD Opteron system - without hardware Spectre mitigation - while building software failed three times and passed once. Turn off the build load, and the test passes most times, which I assume is due to Chromium site isolation being enabled. Restart the software build to crank up the processor load, and the test starts mostly failing again.
Apparently if one is going to run the test, the system should be doing practically nothing otherwise.
Revision 40eb6c29f46ec3b3dfef36201432dca6075df461-refs/heads/master@{#592678}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3558.0-r592678-linux64
Built against libc 2.7, so it *should* work on current, up-to-date versions of Debian, Ubuntu, and similar.
Also, have the archives for WinX32 and WinX64 stopped being built? I've been getting this message for a few days:
The specified key does not exist.No such object: chromium-browser-snapshots/Win/592713/chrome-win32.zip
The specified key does not exist. No such object: chromium-browser-snapshots/Win_x64/592710/chrome-win32.zip
Thanks
Rob, do you know the reason for this? Maybe a revision issue?
And the UI one is forced by you i assume?! If i set it to Default it works as intended by uses the new UI.
Just forced normal, and yeah, the new tab button is misaligned. Not sure it is anything related to my bookmark mod, but I will take a look.
In your build - 71.0.3551.0 (590835) - it looks like this:
And now with - 71.0.3557.0 (592621) - it looks like this:
------------------------
FYI, my v71.0.3558.0-r592993-win32 build acks ThinLTO optimization. Appears LTO currently is broken on 32-bit Windows and perhaps other platforms.
Speaking of the bookmark bar, I have narrowed up the spacing between bookmarks slightly more by modifying yet another UI value.
#win64-dev-official portable version.
"WPO" in regards to Chromium is more of a Microsoft Visual Studio terminology.
ThinLTO, at least when its LTO optimizations are enabled, is basically the LLVM (Clang+LLD) equivalent to MSVC WPO.
https://clang.llvm.org/docs/ThinLTO.html
Polly requires autovectorization, which ThinLTO currently does not support. That means using FullLTO to get LTO optimizations working. Unlike ThinLTO, FullLTO is not multithreaded, so it can take hours to run.
I dropped Polly+FullLTO because there was not much, if any, appreciable performance difference compared to ThinLTO at time. ThinLTO also builds in a fraction of the time, especially with my 32-core build box.
----------------
I went ahead with uploading the above Polly build to my misc repository. The build targets Intel Skylake and later Intel processors. YMMV.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v771.0.3559.0-r593137-win64-intel
----------------
Platform targeting thus far is taking a few edits to source, ninja build files, etc. Not fun, but not unreasonable for Skylake and later.
BTW, before asking about AMD, I tried targetting Bulldozer due to my Opteron build box. The amount of edits is getting ridiculous, so I probably will skip AMD targeting for standard x84-64 building instead.
I am working on a more generic Polly build right now, but I am running into a LLD linking issue. Trying to track it down.
LLVM LTO for 32-bit Windows builds can be a YMMV situation at times.
As to the current situation with the project, LTO bloats the file sizes, thus why Chrom(e/ium) currently is not shipped with LTO on Windows.
If ThinLTO would gain autovec support, which I did spot a possible mention awhile back, I would add Polly to my ThinLTO releases.
----------------
Hopefully have the LLD issue resolved. I recently changed LLVM build environments from msbuild to ninja, and naturally something I little care to track down apparently happened. Back to msbuild for now. Anyway.
Look forward to your more general polly build then =)
Thanks Rob!!
Chromium 71.0.3560.0 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision a11b9614123a1c8051d3f54060af79fc24758881-refs/heads/master@{#593429}
Compiler clang (+lld_linker +polly +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3560.0-r593429-win64-polly
For the curious, compared to my earlier Polly on Skylake+ build, a potential trade-off with a general x86-64 build is sometimes narrower vector widths and reduced vector interleaving during autovectorization.
I did set the vectorizer to maximize bandwidth for the general Polly build, which from a causal glance at live compiler feedback during the building process appeared to increase widening and inverleaving for some loops compared to the standard autovec optimizations.
I have not done significant performance testing with any of the recent Polly builds, especially comparing builds, so YMMV.
ThinLTO:
Speedometer
74.21 ± 0.49
Octane Score: 27427
Sunspider: 304.1ms +/- 1.0%
JetStream: 142.28
BaseMark: N/A (dunno why, but it reported "n/a")
Kraken: 1688.2ms
Polly:
Speedometer
68.64± 0.30
Octane Score: 26999
SunSpider: 317.1ms +/- 0.8%
Kraken: 1703.7ms +/- 0.2%
JetStream: 138.99
BaseMark: 774.21
Both fairly neck and neck imo.
I have a Polly+FullLTO build cooking. Modified my LLVM and Polly optimizations. Could take quite awhile to build. o.0
I had to track down the crasher(s) involved. Also modified Polly a little regarding SCoP detection, plus set various advanced build arguments for LLVM and Polly. As usual, additional tweaking likely will be required, but here is a proof of concept build to get it rolling.
Chromium 71.0.3560.0 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 675fb5b9bfb23451df4406983a1fd29d0b754593-refs/heads/master@{#593453}
Compiler clang (+lld_linker +polly +compiler_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3560.0-r593453-win64-polly
https://news.ycombinator.com/item?id=17942252
I'm not a technical user, but this seems pretty bad in my pov, are the Chromium builds by Rob and Nik, affected by this?
Not sure if I'll do benchmarks again, I'll hold off for the polly+FullLTO
Some people setup and use their own API keys with my builds, though, which enables sync and presumably this feature depending upon how the account consistency flag option is configured.
For those with sync enabled, you can try disabling account consistency. Potential YMMV on successfully logging into some Google services in my previous experiences, though.
chrome://flags/#account-consistency
FYI, for those using my builds without sync and not setting up their own API keys, I currently use a field trial modification when building to set account consistency to fix authentication errors since I do not build with sync, and it seems to work okay with the Google services I have tried.
https://news.ycombinator.com/item?id=18047418
https://ha.x0r.be/posts/chrome-is-a-google-service/
https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/
I rarely complain about software, but this seems to be an asshole move of the developers.
Also, I can't wait to play around with your polly+FullLTO build, gonna be sweet! :D
1. the incognito mode by default (#command-line-flags).
2. or chrome://flags/#account-consistency → disabled (Note this flag is experimental and can simply disappear!)
So does disabling chrome://flags/#account-consistency work for those builds or do I *have* to run a No Sync version?
Like RobRich said in a previous comment, the "No Sync" Chromium version has not Google API keys by default. So the automatic login is natively broken. ^^
Chromium 71.0.3560.0 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 675fb5b9bfb23451df4406983a1fd29d0b754593-refs/heads/master@{#593453}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3560.0-r593453-win64-polly-r2
That way they'll be no accidental clicking on it.
https://en.wikipedia.org/wiki/Automatic_vectorization
I also tweaked LLVM build flags to widen vectorization, potentially improve register allocation, and few other tricks.
Polly does various other loop-intensive optimizations that are not as easily measured by typical benchmarks, such as optimizing video codecs, cryptographic routines, etc.
Polly+FullLTO
Chromium 71.0.3560.0 (Official Build) (64-bit)
Revision 675fb5b9bfb23451df4406983a1fd29d0b754593-refs/heads/master@{#593453}
JavaScript V8 7.1.163
Speedometer 77.85± 0.50
JetStream 141.10 ± 8.4137
Sunspider: 303.8ms +/- 1.1%
Kraken: 1671.3ms +/- 0.5%
Octane Score: 27347
Basemark Web: 845.09
TL;DR
Can confirm @Anon3795 Polly+FullLTO is better in Speedometer now. Even on par if not tiny better than ThinLTO earlier, in Speedo and Octane. Jetstream now on par. Dropped a bit in Sunspider and kraken. Smashed the last polly build in Basemark Web though, by like ~70 points.
As always, Thanks Rob, your time and effort is much appreciated!! =)
Maybe if there was a 'speedometer' like test for privacy so you could fawn over scores that actually have merit.
1) If you're so opposed, begs to question, why are u here? It's all custom chromium builds here...
2) browser leaking data, idk, maybe it is, maybe it isn't. Who's to say my ISP or cell phone provider isn't leaking my data?
I agree it's wrong, but what are you recommending?
The political discourse is: To protect humanity from terrorists and cyber-terrorists, the governments around the world need the maximum amount of data for every person. Their main goal is to obtain these data by any means and then analyze them.
Some laws help governments to get them:
https://en.wikipedia.org/wiki/CLOUD_Act
https://en.wikipedia.org/wiki/Patriot_Act
https://en.wikipedia.org/wiki/USA_Freedom_Act
https://en.wikipedia.org/wiki/PRISM_(surveillance_program)
https://en.wikipedia.org/wiki/Bullrun_(decryption_program)
https://www.theguardian.com/world/2013/sep/05/nsa-gchq-encryption-codes-security (Edgehill)
Internet is a welcome tool for governments. The largest Internet companies (Alphabet/Google, Amazon, eBay, Facebook, Microsoft, Safari, Yahoo...) and associations/organizations (Mozilla...) have a lot of data. This is the Big data.
Before all, these companies get user data for their own business (advertising, marketing, continual service improvement...) but must help governments according to the laws. Most of them are American and Chinese:
https://en.wikipedia.org/wiki/List_of_largest_Internet_companies
These companies and organizations use many ways (directly or via third-parties) to get our user data. Some methods I know:
1) ISP, DNS
Retention period for server logs
https://www.eff.org/issues/mandatory-data-retention
Black box linked to the "Security Service" which monitor all internet traffic.
https://www.channel4.com/news/black-boxes-to-monitor-all-internet-and-phone-data
2) BIOS/UEFI
Absolute Home & Office, LoJack, CompuTrace, SMM which have access to the device and send data.
https://en.wikipedia.org/wiki/Absolute_Home_&_Office
https://en.wikipedia.org/wiki/System_Management_Mode
[RU] https://securelist.ru/ugroza-iz-bios/19169/
3) OS
Nothing to add! You know for example the problem of user data spying in Windows 10 (Microsoft), Android (Google) and iOS (Apple).
4) Software, App
Like web browsers (and their extensions), anti-virus, anti-spyware...
For example, Chrome (Google), Firefox (Mozilla) and Safari (Apple) are American products. So, they respect the CLOUD Act and Patriot Act. Opera (Otello Corporation) is owned by Chinese Qihoo 360/Golden Brick Capital.
Another thing is China (and the USA, and EU certainly!) considers the discovery of security breaches as a strategic advantage. "China's government wants to keep vuln discoveries by its citizens within its borders, a sentiment expressed by the country's top executives as well. Leading Chinese security company Qihoo 360's CEO Zhou Hongyi is a vocal opponent of Chinese teams going abroad to compete in events like Pwn2Own." (https://www.engadget.com/2018/03/16/chinese-hackers-pwn2own-no-go/)
In the USA, the CIA attacks Android/iOS phones by using undisclosed security vulnerabilities ("zero days") possessed by the CIA. (https://wikileaks.org/ciav7p1/)
5) Websites and web services.
You know for example the problem of user data spying by GAFA/Big tech services.
Moreover, most websites in the world use Google and Facebook stuff to build their webpages (Analytics, AdWords, AdSense, API, CDN, fonts, JS, "Like" buttons, Youtube videos...). The webmasters (who are lambda humans!) contribute to this global spying. Please, read the #guides about different technologies to get user data from a website. Also, the users "give the stick to be beaten with" when they use, for example, social media (Facebook, G+...) with their own personal data.
Finally:
Do not be paranoid (like Richard Stallman who rejects all major sites - https://stallman.org/). You absolutely cannot stop that. This phenomenon increase each day. Protect your #privacy against user tracking and profiling tools as you can (like Edward Snowden and other whistleblower recommend!).
Even using #chromium-forks with patches for removing Google integration, it is far from enough. But it is an honorable step! Note they are often outdated. Are they secure? Security ≠ privacy. Do not worry. You will be tracked even using a "secure browser", a VPN (or TOR network, if you like a slow connection!). Like most of us, you probably surf on the Web, use a connected TV, a laptop or Android/iPhone device, a video game console, a GPS in your car... and soon, a connected car, a smart grid... Welcome in the data world! :)
I modified LLVM using a proposed condition branch folding optimization still in project development.
I modified Polly for more permissive SCoP detection, plus I set an accompanying configuration for potentially improved loop fusion.
I have moved Polly up in the LLVM pass pipeline to after loop optimization during the inline cycle instead of right before vectorization.
Given the new pass location, I probably should look into enabling Polly's own inliner. Perhaps next time.
Chromium build and version details:
Chromium 71.0.3563.0 (Official Build) (Windows 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 420ec97cb6d2c364a56f1d5d7859b7bb39a8d05a-refs/heads/master@{#594262}
Compiler clang (+lld_linker +polly +fulllto +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3563.0-r594262-win64-polly
Chromium 71.0.3563.0 (Official Build) (64-bit)
Revision 420ec97cb6d2c364a56f1d5d7859b7bb39a8d05a-refs/heads/master@{#594262}
JavaScript V8 7.1.178
Sunspider: 304.7ms +/- 1.4%
Octane Score: 27182
Speedometer: 78.47 ± 0.25
Jetstream: 144.25 ± 0.77084
Kraken: 1654.0ms +/- 2.2%
BaseMark Web: 735.62
TL;DR
Most of the benchmarks are on par with previous polly build. However, Speedometer and Jetstream did well this time around. Overall, results seem to be similar, if not better in some cases than ThinLTO. Basemark Web was the one exception, dropping 100 points from last polly, a little weird.
I suspect Basemark Web could be related to the different position of Polly in the pass pipeline. That actually was something I was needing to know, and you have saved me from having to run benchmarks to find out. :)
I probably will move Polly back to before vectorization.
----------------
Currently I am trying to track down an issue with building 32-bit ThinLTO. First was inalloca errors. Found and reverted the LLVM revision generating the error. Next up was duplicate symbols. Disabled one of the duplicate symbol checks in the LLD code. The latest is LLD complaining about missing symbol files for system libraries. Working on applying a possible fix right now.
My understanding is the latest version of SRWare Iron has excluded it. Why don't you all do the same here in future releases?
@scorpiogreen: Choose a "no sync" version! ^^
----------------
@scorpiogreen We are not Chromium project devs, or to be specific, at least I am not. I do occasionally post bug reports and similar feedback to the project, but otherwise, my builds here are whatever I am using or working on at the particular time. It is a personal interest thing for me, and my own interest is generally browser performance.
----------------
About the sync situation, AFAIK, there is supposed to be an opt-out setting in a future release. Someone else probably will have to fill in particular details of how, when, etc., as I do not use API keys and sync, thus I do not really pay much attention to it.
I suppose thats living on the experimental side, eh?
How come there's no shortcut option to mute the current tab in Chrome like there's in Firefox (Ctrl+M)?! ...
@RobRich I appreciate what you do but that still begs the question. Thanks for all your good work, anyway.
Settings → Advanced → Allow Chromium sign-in → disable
----------------
This time I left out the branch folding optimization for LLVM currently in development. It could be hitting the branch predictor of some processors rather hard, thus possibly decreasing its efficiency.
I have moved Polly back to right before vectorization. As before, it is modified for more permissive SCoP detection.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3566.0-r595302-win64-polly
I already have profitability analysis down to 40 instructions per loop, but at some point I would like to have Polly go ahead with processing unprofitable SCoPs to potentially find more optimization opportunities. The issue is what components to efficiently target for such optimization. For example. part of libaom (AV1 video) recently ran in Polly with unprofitable processing enabled for like 10+ hours and was still going when manually stopped; and that was at the default dependency computeout.
Chromium 71.0.3566.0 (Official Build) (64-bit)
Revision 83f170eb2368ad8d396a0ff86aaea76ccf26597f-refs/heads/master@{#595302}
JavaScript V8 7.1.201
Speedometer: 77.8± 0.83
JetStream: 145.26± 0.31045
Kraken: 1729.9ms +/- 0.4%
SunSpider: 300.3ms +/- 0.9%
Octane Score: 27433
Basemark Web: 865.74
TL;DR
Modest improvements in Octane and Kraken. Rest are similar to previous polly builds. Basemark Web is now back up (+~100 points) from previous polly. All looking good.
As always, thank you so much Rob!!
There's a site* that scrolls slow/laggy compared to the rest of the web.
I get that it's a fairly heavy website, but the scrolling is smooth in both Firefox and Edge.
* https://www.w3.org/TR/html52/single-page.html
That said, the linked page uses like 400MB+ of memory for its browser process (site isolation enabled), which is quite a bit of HTML to process for a single page. I get why there could be a delay on some systems.
------------------------
Might be able to find a little more with Polly before getting too drastic with the configuration. ;)
I introduced a possible bug into Polly's SCoP detection when modifying for more permissive detection. Fixed it.
It appears the Polly non-affine option sets both non-affine reads and writes, with non-affine writes potentially negatively impact scheduling. I found an older code commit to implement non-affine reads without non-affine writes, and I have deployed the modification.
Currently rolling internal test builds.
As to Polly source code modifications, non-afffine reads are enabled while non-affine writes are not, plus more permissive SCoP detection is enabled as usual.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3567.0-r595351-win64-polly
Chromium 71.0.3567.0 (Official Build) (64-bit)
Revision ad233d1eb67fa115cd0580a9f293e2e9b8e0f84b-refs/heads/master@{#595351}
JavaScript V8 7.1.216
Basemark Web: 671.27
Speedometer: 77.33± 0.51
Jetstream: 144.68 ± 0.88017
Octane Score: 27796
Most of the benchmarks are similar, I left out Sunspider and Kraken for this reason too. Basemark Web however, significant decrease by 200 points this time, so uh oh.
As always, thanks for the benchmarks! :)
Not the version 66 Stable Android version you are looking for but check Marmaduke builds here : https://github.com/macchrome/droidchrome/releases
He make great version stable with full codecs, etc.
Revision d0b2ebaf1f6b47fca493e82da45eedf671cf6bf5-refs/heads/master@{#595975}
JavaScript V8 7.1.226
Basemark Web: 848.66
Speedometer: 77.29± 0.56
JetStream: 144.84 ± 2.5925
Octane Score: 27647
Can confirm, the Basemark Web score of your latest polly build is back up to what it was before. This seems to be a good build, snappy and so far smooth with no issues.
As always, thanks so much Rob, much appreciated!!
does anyone know what other updated browser has absolutely NO webRTC?
Thanks :)
@Anon3841: Also, thank you for your benchmarks.
@Anon3842: Do not afraid about webRTC! If you use a VPN on your whole OS or router, your VPN service protects you from this leak. Do not use VPN/proxy browser extensions. Moreover, you can protect you with some #extensions like uBlock Origin or ScriptSafe.
WebRTC is enabled in Chromium and in most "ungoogled" #chromium-forks (like Iridium, ungoogled-chromium) even if Chromium is compiled with "enable_webrtc=false". So, you can use Firefox and all Firefox-based browsers with "media.peerconnection.enabled" → false.
I think it's revision related but just wondering if anyone can confirm having this problem as well
Sync • Widevine • 69.0.3497.100 (576753)
@Anon3844+Anon3846 I would suspect revision related, too. Project dev build is at 3572. Might want to try it in the meantime.
chrome://flags/#top-chrome-md
I was using that to switch back to the old UI
---
Also running into a misaligned + symbol when one wants to add new tabs.
https://imgur.com/a/MUEMu6f
It seems to be edging it's way off the top of my screen
The new UI is a pain in the ass.
Many users use the switch chrome://flags/#top-chrome-md but since version (71.0.3556.6 / #592055) it is buggy. Chromium won’t fix it.
See here :
https://bugs.chromium.org/p/chromium/issues/detail?id=888304
https://bugs.chromium.org/p/chromium/issues/detail?id=892045
Old the last decisons from Chromium (UI, auto-login, etc. in fact, decision from Google) had male me switch to firefox.
from what I can see I've only been able to get it in 71.0.3559.0_Dev from: #win64-dev-thumbapps
For some reason I can't seem to get it anymore in newer versions or different chromium options from this site.
@Anon3849, thanks for the links. Sad news but not surprising at all coming from these devs.
So they don't plan on fixing either one of those issues?
Not good. I haven't had much issue with Chromium until now. The new UI looks hideous and the tabs associated with it are screwed up.
As far as the sign-in / synch auto-login is concerned, they did fix that with the option to turn it off so that's a good sign.
Let's hope they revisit those two issues I brought up, someday.
1. About the Chromium UI:
That’s personal tastes! ;)
Personally, I like Google Material Design (mainly used in Android) and Firefox Quantum's Photon. Material Design will gradually be extended throughout Google's array of web and mobile products, providing a consistent experience across all platforms and applications. So experimental flags like chrome://flags/#top-chrome-md will be removed soon. "[...] that using these switches is not supported or recommended. They should only be used for temporary cases and may break in the future." (cf. https://www.chromium.org/developers/how-tos/run-chromium-with-flags)
2. About the Google Chrome auto sign-in:
This feature does not exist in Chromium settings. That concerns only Google Chrome:
https://github.com/RobRich999/Chromium_Misc/releases/tag/v71.0.3572.0-r597448-win64-polly
It looked okay on quick runs of Basemark Web and SunSpider on my Intel Kaby Lake i5 system, though as usual with these experimental builds, YMMV on performance
I ended up turning on NewGVN (with store refinement), which in turn appears to have increased successful SCoP rates compared to other recent builds.
I also reset the optimization levels for now. One benefit is smaller code size, which might improve processor caching opportunities.
3 things...
That's too bad. I like the option of having chrome://flags/#top-chrome-md for those who want the older UI. I didn't sign up for Chromium to be an exact Chrome clone in mind. Disappointing.
Also the tabs still have a misaligned + symbol when one wants to add new tabs. You can see it in the
And finally there's that Google auto sign-in option now in the latest version of Chromium portable using the PortableApps platform. Don't know if you're aware of it but I just downloaded the latest version of it and it is there. Kudos to @RobRich in his 29 Sep 2018, 16:44 post up above for announcing it.
Thanks for your efforts
Chromium 71.0.3572.0 (Official Build) (64-bit)
Revision c1eb1615fe642de25c488bb103082786e1274f0f-refs/heads/master@{#597448}
JavaScript V8 7.1.276
Speedometer: 79.72 ± 0.75
JetStream: 155.15 ± 0.67305
Bassemark Web: 776.75
Octane Score: 32833
Basemark Web dropped significantly by about 70 points. =/ Absolutely crushed the rest. I don't know if this was purely because of your configuration Rob, or if it's revision related, but highest Speedometer, JetStream and Octane scores by far at the moment.
Speedo ~+4 Jetstream was ~+10 points and Octane is ~+5000. This build is now the one to beat.
I have not looked at the specifics, but WebGL probably influences a good chunk of the score. I ran default code path optimization levels, so some of the related code might have been built at O1, which maps to Os in clang-cl.
If sync is important for you, create your own #google-api-keys
I'm on a Windows 64-bit system, so I downloaded the 64-bit version
https://github.com/henrypp/chromium/releases/download/v69.0.3497.100-r576753-win64/chromium-sync.zip
From the .manifest file:
name='69.0.3497.100'
version='69.0.3497.100'
type='win32'/>
For comparison I tried this version:
https://github.com/RobRich999/Chromium_Clang/releases/download/v71.0.3572.0-r597399-win64/chrome.zip
From the .manifest file:
name='71.0.3572.0'
version='71.0.3572.0'
type='win32'/>
So I'm assuming now that only 32-bit versions of Chromium exist, and all the links to 64-bit versions contain a 32-bit version.
That raises the question:
If the link to a 64-bit version contains a 32-bit version anyway, why bother to offer a link that says: '64-bit version?
Hypothesis:
To placate visitors who would otherwise complain no 64-bit version is available
Is my hypothesis too simple? Is there more to it?
Colin Tennyson
Load the browser and point it towards the URL chrome://version to see the bit type of the Windows build. For example:
Chromium 72.0.3580.0 (Official Build) (64-bit)
Revision 683272efae485d924651022da3a76ed6977470f8-refs/heads/master@{#599494}
OS Windows
There are numerous other ways to check as well, ranging from command line utilities to debugging apps to even using notepad.exe to search an executable for its PE type. Take Sigheck for example:
D:\Chromium\Application>sigcheck64 chrome.exe
Sigcheck v2.60 - File version and signature viewer
Copyright (C) 2004-2017 Mark Russinovich
Sysinternals - www.sysinternals.com
D:\Chromium\Application\chrome.exe:
Verified: Unsigned
Link date: 1:00 AM 10/13/2018
Publisher: n/a
Company: The Chromium Authors
Description: Chromium
Product: Chromium
Prod version: 72.0.3580.0
File version: 72.0.3580.0
MachineType: 64-bit
https://docs.microsoft.com/en-us/sysinternals/downloads/sigcheck
https://chrome.google.com/webstore/detail/mutetab/acofndgbcimipbpeoplfjcapdbebbmca
https://github.com/RobRich999/Chromium_Misc/releases/tag/v72.0.3581.0-r599543-win64-intel
Chromium 72.0.3582.0 (Official Build) (64-bit)
Revision ec5ef4854713d5f8eaf67dcef2acad1c67cb925f-refs/heads/master@{#599622
OS Windows
No Sync - WebRTC - No Widevine
chrome.packed-2018-10-16.7z
https://github.com/macchrome/winchrome/releases/v72.0.3582.0-r599622-Win64
===
Thin LTO builds and building with the "tip of the tree" clang/LLVM seems to be broken, probably just a temporary problem. Takes 2.5 times longer to build a Full LTO clang/LLVM than it does to build bog standard Chromium!
Regardless, this is the version of Chromium that I'll be using for the next 4 to 6 weeks.
llvm\tools\lld\COFF\SymbolTable.cp
Around line 393 to 410, comment out the duplicate symbol reports.
// else
// reportDuplicate(S, F);
// if (!cast<DefinedRegular>(S)->isCOMDAT())
// reportDuplicate(S, F);
Also set 'treat_warnings_as_errors = false' in your Chromium build arguments if not already. There has been a recent change in LLVM -Wshadow reported warnings for enumerators. Devs are working on fixing the warnings' reported code segments, but otherwise, you can ignore those warnings for now.
@Evangelical: Agree. Auto sign-in is engraved in Chromium but works only with the "sync" (or valid #google-api-keys) Chromium version.
@Colin Tennyson: "win32" in the manifest file is a generic identifier (like RobRich said!) This is really a 64-bit version. You cannot install this version on a 32-bit Windows.
@Heyman: It is currently a known issue of chrlauncher. https://github.com/henrypp/chrlauncher/issues/100#issuecomment-383302954 The binaries are placed in a sub folder named after the version. So copy-paste the content and remove the parent folder.
I always do a Full LTO build of the latest LLVM. The Duplicate symbols problem was driving me up the wall, particularly as the problem occurs at the very end of a Windows Chromium build.
I have also just updated the homebrew tap, so your next "brew update && brew cask upgrade marmaduke-chromium" should install the new binaries.
@RobRich - What are your recommended polly parameters?
Managed to get Mac Chromium LTO and CFI builds working again.
==
Chromium for 64-bit macOS - All Codecs - Wednesday, 17 October 2018
Chromium v70.0.3538.67-r587811-macOS
9ab0cfab84ded083718d3a4ff830726efd38869f-refs/branch-heads/3538@{#1002}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, AV1, etc...)
- official build
- Stable
- SDK 10.14
- Xcode 10 (10A255) GM Seed
- Compiled under macOS 10.14 build 18A389
- Clang/LLVM 8.0.0 342458
No Sync • WebRTC • No Widevine • ThinLTO • CFI (Will probably make this the standard)
Chromium.70.0.3538.67.thinlto.cfi.nosync.app.zip
https://github.com/macchrome/macstable/releases/download/v70.0.3538.67-r587811-macOS/Chromium.70.0.3538.67.thinlto.cfi.nosync.app.zip
SHA1 B74A3AD58CBDBCAB51BC5B23E71B8124F8A875A1
==== Additional configuration ====
NO Swiftshader dynamic libraries! (Who uses them?!)
use_egl=false
mv third_party/libsrtp/VERSION third_party/libsrtp/LIBSRTP_VERSION
cflags = [ "-O3","-flto=thin"]
ldflags += ["-flto=thin","-fvisibility=hidden", "-fsanitize=cfi" ]
Try starting with:
"-mllvm", "-enable-newgvn",
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
I am using NewGVN right now as hoisting for regular GVN currently is disabled due to some reported performance regressions.
You can lower the profitability limit down to 40+ instructions per loop, though YMMV on real-world returns.
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
I also applied a source code mod to Polly to potentially help with loop fusion when configured to max, though it too is a YMMV situation, as I need to do further testing. I will try to let ya' know something about it in the near future.
I also suggest benchmarking your browser build at different optimization levels regardless of LTO optimizations. Depending upon various factors, you might find building the max/speed code targets at the /O2(-O2) defaults to be as fast or faster than -O3. Could be due to code bloat, caching, register pressure, etc.
Likewise, I have dropped the regular optimization targets back to their /O1(-Os) defaults as well. Remembering back to old MSVC PGO build stats, there are only like 300 or so functions even built for speed versus size for a profiled build. ;)
I actually have a internal build from earlier this week with all optimized targets set to -Os, though with a tweaked LLVM configuration plus dramatically increased inlining limits for V8. It is supposedly slightly faster in Basemark Web 3.0 *without LTO* versus a recent ThinLTO build. o.0 "Supposedly" as I really do not put much importance on BW3 scores due to variability in results, at least on my test platform. Anyway.
BTW, you can now set ThinLTO optimization (at lto_opt_level = 2) from the build arguments.
use_thin_lto = true
thin_lto_enable_optimizations = true
If otherwise setting manually on the build config, I suggest also adding "-fwhole-program-vtables" to the cflags or ldflags as appropriate for the target platform to enable whole program devirtualization.
chromium-sync.zip has win32
"-mllvm", "-enable-newgvn",
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass=loop-vectorize",
"-Xclang", "-Rpass-analysis=polly",
The rpass lines are optional. I sometimes take a glance to get a general feel for SCoP rates and vector stats when building.
I know that Nik compiles his Chromium builds essentially as default build settings, therefore I assume that Google Chrome devs must be making a switch on their end for official Chrome builds to keep the Audio Service within the browser process currently. They must have some sort of compile time switch for this.
If anyone is concerned about this extra process which is unsandboxed and running at Medium IL, have no fear, there is a working command line argument which will tuck that Audio Service back into the browser process for now. I have confirmed that this command is working successfully, but keep in mind you have to run it everytime and therefore you can add this into your Chromium shortcut. I will be doing this for now until Chrome devs properly sandbox that Audio Service process and that is likely why official Chrome builds still have that kept within the browser process.
chrome.exe --disable-features=AudioServiceOutOfProcess
"AudioService":[
{
"platforms":[
"linux"
],
"experiments":[
{
"name":"AudioProcess_LaunchOnStartup_Sandboxed_v7",
"params":{
"teardown_timeout_s":"0"
},
"enable_features":[
"AudioServiceAudioStreams",
"AudioServiceLaunchOnStartup",
"AudioServiceOutOfProcess",
"AudioServiceSandbox"
]
}
]
},
{
"platforms":[
"mac",
"windows"
],
"experiments":[
{
"name":"AudioProcess_LaunchOnStartup_Sandboxed_APM_v8",
"params":{
"teardown_timeout_s":"0"
},
"enable_features":[
"AudioServiceAudioStreams",
"AudioServiceLaunchOnStartup",
"AudioServiceOutOfProcess",
"AudioServiceSandbox",
"WebRtcApmInAudioService"
]
}
]
},
{
"platforms":[
"android",
"chromeos"
],
"experiments":[
{
"name":"AudioServiceStreams",
"enable_features":[
"AudioServiceAudioStreams"
]
}
]
}
],
Anyway, it looks like the field trial config was likely missing the "AudioServiceSandbox" part for M70 at the time for stable channel, as you said development is still ongoing. Although I know that you mostly play/build with the latest code changes and therefore you would have likely had the sandbox portion already.
Instead of disabling "AudioServiceOutOfProcess" as I initially had mentioned, M70 Stable channel users can simply enable the sandbox feature for the audio service thanks to RobRich's details.
chrome.exe --enable-features=AudioServiceSandbox
I have confirmed that this takes the Medium IL Audio Service utility process and starts that process as Low IL and fully sandboxed. This is great news. Keep in mind that I am referring only to M70 stable. Users of RobRich's latest M71/M72 or whatnot would likely already have that sandbox enabled.
As I understand it, a lot of Chrome's internal code is going to continue to compartmentalize and break out into individual 'utility' processes (Out Of Process) and those utility processes will eventually have the AppContainer sandbox (Untrusted IL) protection as well. However, at these mid stages of development for these Out Of Process utility services, Low IL sandbox is perfectly fine for the time being. I was concerned especially regarding the initial default Medium IL, however. But with RobRich's help there, we can sandbox the audio process on M70 stable with the command line above.
@marmaduke One clarification on a particular build type. You probably should be using -03 across the board for all optimized targets with a Polly build, at least in theory.
Introducing Chromium ThugCAT for Mac. (For the curious, CAT stands for Chromium Arsehole Technology)
Thug Cat, or Thugsy as he is known, is the local cat; his sole purpose in life is to deploy his technology on unmown lawns. In honour of Thug Cat's impending death by lawn mower, I would like to introduce Chromium ThugCAT for Mac.
ThugCAT is a clang/LLVM -O3 polly (RobRich) optimised, full LTO, CFI beast! The browser that Chrome asspires (sic) to be.
Chromium for 64-bit macOS - All Codecs - Wednesday, 17 October 2018
Chromium v70.0.3538.67-r587811-macOS
9ab0cfab84ded083718d3a4ff830726efd38869f-refs/branch-heads/3538@{#1002}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, AV1, etc...)
- official build
- Stable
- SDK 10.14
- Xcode 10 (10A255) GM Seed
- Compiled under macOS 10.14 build 18A389
- Clang/LLVM 8.0.0 342458
Sync • WebRTC • Widevine • Polly • LTO • CFI • O3 Optimised [ThugCAT]
Chromium.70.0.3538.67.polly.lto.cfi.O3.sync.app.zip
https://github.com/macchrome/macstable/releases/download/v70.0.3538.67-r587811-macOS/Chromium.70.0.3538.67.polly.lto.cfi.O3.sync.app.zip
SHA1 A995B2344BF0E07D24E9B82EA4C58999E7ED09F3
WARNING: ThugCAT might deploy technology on your desktop or lap.
ThugCAT takes approximately 3 times as long to build as standard Chromium, so due to anticipated lack of demand will probably be confined to future DEV builds.
When I'm trying to first open the latest version 70.0.3538.67 on my macos High Sierra I get an error "Chromium.app can't be opened because it is from an unidentified developer".
I have never had this error with Chromium from osxportableapps. And now I use 69.0.3497.100 - works fine.
What is the problem with 70.0.3538.67?
My Chromium.app is not signed.
Initially, you have to allow an exception in "Security & Privacy".
I've just checked (HS 10.13.6), and am not having this problem.
but previous versions was OK, just don't want use Chromium as exception in "Security & Privacy" )
On the Polly side, I set another layer of tiling for loop data locality, used register tiling to supposedly implement a type of loop unroll and jam, increased prevectorization to the 128-bit width of SSE, and added another pass of dead code elimination during loop optimization.
Prevectorization widening probably is the only significant change above, but I suspected the build would take awhile anyway, so whatever. I will try to further assess the viability of the others later.
"-mllvm", "-polly-prevect-width=128",
On the LLVM side, I am trying different instruction scheduling passes to bias towards instruction-level parallelism while still factoring register pressure and aliasing, increased inlining for V8, plus experimental loop versioning for potentially more accurate aliasing. Realistically the non-default instruction schedulers are more for code testing than deployment when it comes to x86 programs, so the idea is a huge YMMV right now when targeting such a wide swath of varying code comprising Chromium. My initial basic analysis is ongoing.
Deeper into the LLVM source, I have added several more passes of the aggressive instruction combiner to the pass manager configuration so it is called before the various regular instruction combiner passes and at any opt level. I am not sure of any particular benefit as of yet, but it was a relatively quick modification to locally test pass manager changes.
I also have been poking at the LLVM target description file for the x86 architecture. As default configured, we are missing out on extra potentially useful instructions due to attempting backwards compatibility to much earlier x86-64 processors. For example, anyone here actually running Chromium on a Pentium 4 Prescott?!
It is going to take some effort to determine if there are any instruction set benefits. For a particular example, be it via command line or target description file, it is not as simple as generically turning on AVX support for the compiler due to the potential for register save and restore transition penalties when running mixed AVX (256-bit) and SSE (128-bit) code through the same SIMD pipeline.
I'm very privacy and security focus: i delete/disable a lot of services (such as Siri), use a firewall - Hands Off, and use DNSKong (an oldie but a goodie) an HOSTS file blocker. Perhaps High Sierra has auto-updated and changed certain parameters. OSX is probably the best commercial OS on the market (compared to Windows 1809 the stuff that comes out of Thug Cat's arse is better). Apart from changing my build system to Majove 10.14 nothing has changed. I do not know what has materially changed.
@RobRich
I think Google should get its arse in gear and actually issue some canonical Polly and LTO build instructions. The utter dross that is produced by Microsoft - namely Windows 1809, and Google vis-a-vis Chrome is mind blowing. One gets the impression that the only "thing" these mega-corporate welfare queens are good at is asking government for hand outs. Paul Allen must be turning in his grave.
Current public ThinLTO build:
SunSpider: 263.5ms +/- 1.2% (lower is better)
Octane 2: 39220 (higher is better)
ARES-6: 23.92 ± 0.57ms (lower is better)
Dromaeo V8: 1859.48runs/s (higher is better)
Just tested internal Polly without LTO build:
SunSpider: 250.6ms +/- 1.8%
Octane 2: 39690
ARES-6: 23.14 ± 0.22ms
Dromaeo V8: 1880.57runs/s
This is for Win7 (not sure about win10, MAC or VM)
ON win7 - All extensions and its settings are in C:\Users\XXX\AppData\Local\Chromium\User Data\Default - ***Save a good copy as backup
How I do it when there is a new update - (In your case move data/settings from chrome to chromium)
1) Clean uninstall everything (make sure no chromium folder is left behind - make sure you have the backup done)
2) Install new chromium
3) Load chromium
4) Goto <Setting> <System> DISABLE <Continue running background> and close chromium (*** this is important step)
5) If desire, cclean or manually delete Default-folder in C:\Users\XXX\AppData\Local\Chromium\User Data\Default
6) Copy-Paste the saved good copy to C:\Users\XXX\AppData\Local\Chromium\User Data\Default (with chromium completely closed down)
7) Run chromium and everything orignal extention should be there with new chormium updated
Also Note : C:\Users\XXX\AppData\Local\Chromium\User Data\Local State contain all your settings you pull up in chrome://flags
So you need to copy and paste a saved copy of Local State from chrome to the new chromium,
you get all your original preference PLUS the new stuff the dev put in
Otherwise you just manually go thro all the config and setup again :)
Good luck :)
I had some difficulties to find the latest system requirements; realizing later on that there is a headline called "macOS 10.10+". Bummer…
So, I'm using 10.9.5 -- for different reasons. Main reason: Apple releases crap, making software (as hardware) worse and worse, and I don't trust them.
Is there any chance that there will be a chromium browser 70+ (all codecs), supporting 10.9.5? Because even the "official" chromium download says that the requirements are 10.9.5, but serve a version needing 10.10.
@san: Since June 2018, Chromium browser 67 is the last supported version on macOS 10.9.x. The latest system requirements are the same as Google Chrome: https://support.google.com/chrome/a/answer/7100626
@Anon3900: Thank you for your help. Do not forget the import/export option of chrome://bookmarks ;)
But this tester here: https://tools.woolyss.com/html5-audio-video-tester/
Does not seem to indicate this proposition. Is this expected behavior?
chrome://flags/#enable-av1-decoder
SunSpider: 263.5ms +/- 1.2% (lower is better)
Octane 2: 39220 (higher is better)
ARES-6: 23.92 ± 0.57ms (lower is better)
Dromaeo V8: 1859.48runs/s (higher is better)
Current public ThinLTO r601406 build:
SunSpider: 248.5ms +/- 1.8%
Octane 2: 39815
ARES-6: 22.36 ± 0.22ms
Dromaeo V8: 1868.74runs/s
Using non-default instruction scheduling passes to bias for instruction level parallelism, plus modified the LLVM pass manager to enable the aggressive instruction combining pass for all opt levels above -O0.
I was tuning for JavaScript performance for now, so someone else can toss the build at other benchmarks if desired. I did some quick casual runs of Speedometer and BW3 to verify compatibility, and IIRC, the numbers were about as expected for my ThinLTO builds.
----------------
On the experimental front, I am still poking at modifications to the LLVM target description file for the x86 architecture. Thus far I have added four additional instruction subtarget features that should not break compatibility with most popular x86 processors from like 2010 forward. As to performance benefits, if any, I need to generate an updated build and run numbers.
Chromium.70.0.3538.67.sync.app [Standard build]
sunspider-1.0.2: 306.6ms +/- 2.1%
Octane Score: 31237
ARES-6: 31.15 ±0.62ms
Dromaeo V8: 1465.56runs/s (Total)
Chromium.70.0.3538.67.polly.lto.cfi.O3.sync.app
sunspider-1.0.2: 305.7ms +/- 1.7%
Octane Score: 30951
ARES-6: 31.46 ±0.35ms
Dromaeo V8: 1470.89runs/s (Total)
Chromium.70.0.3538.67.thinlto.cfi.nosync.app [-O3]
sunspider-1.0.2: 303.0ms +/- 2.2%
Octane Score: 31162
ARES-6: 31.22 ±0.24ms
Dromaeo V8: 1468.56runs/s (Total)
===
CFI adds a slight overhead (Chrome is working to make this the standard in all builds.)
Nothing conclusive, but my preference is for thinlto (perhaps with O2 - standard - optimisation) and cfi. Full LTO is a bit of an indulgence given the much longer build time.
Also, I build the vanilla Chromium (with same build flags as Bromite) for Android, side by side: https://www.bromite.org/chromium
It is used mostly for checking if a bug is present upstream in Chromium.
Fun note: I was able to disable webRTC for a few builds after the build flag was removed upstream, but in the end I had to give up as it has become too tightly integrated as you mentioned...I hope other build flags do not follow this fate!
Site archive: https://web.archive.org/web/20180925045932/https://chromium.woolyss.com/#chromium-forks
I decided to incorporate some of csagan5's patches into a private present (OSX) stable build. Namely:
(i) Disable-WebRTC-by-default.patch
(ii) ungoogled-chromium-Disable-webRTC-log-uploader.patch
(iii) getBoundingClientRect-measureText-add-fingerprinting-mitigation.patch
WebRTC is disabled to a certain degree, apart from RTCPeerConnection, RTCDataChannel - which is consistent with using third party methods; but, DeviceEnumeration is also enabled. I don't know if ClientRect is generating spurious or random data, but it appears that this has not been disabled.
Only a sub-set of the available patches has been applied, so a more comprehensive application of patches might produce a different result.
Taking a really quick look at recent changes, I did note there have been SQLite component updates. History, autofill, cookies, etc. use it.
====
Chromium for 64-bit macOS - All Codecs - Wednesday, 17 October 2018
Chromium v70.0.3538.67-r587811-macOS
9ab0cfab84ded083718d3a4ff830726efd38869f-refs/branch-heads/3538@{#1002}
OS Mac OS X
- only for macOS 64
- with codecs (h264, h265, flac, xvid, AV1, etc...)
- official build
- Stable
- SDK 10.14
- Xcode 10 (10A255) GM Seed
- Compiled under macOS 10.14 build 18A389
- Clang/LLVM 8.0.0 342458
No Sync • No WebRTC • No Widevine • Polly • LTO • CFI • O3 Optimised [ThugCAT]
Chromium.70.0.3538.67.polly.lto.O3.nosync.app.zip
https://github.com/macchrome/macstable/releases/download/v70.0.3538.67-r587811-macOS/Chromium.70.0.3538.67.polly.lto.O3.nosync.app.zip
SHA1 03E46A975D6BDBABF76B7BE53311CEB866B11BD3
===
No new Mac builds until November.
chrome.zip | sha1: d56ab47fb472d7212ef01f8ea0c3ce2763f1e1ca
https://drive.google.com/open?id=1yXI92U_EA3ydioy7j9rg-XxWRCQ6TDU5
mini_installer.exe | sha1: d2d10abd561680b46dbc0ed67b3ea7c8501051dc
https://drive.google.com/open?id=1C7wSOiu39rC94tD3vUqinAQWqJ48picu
Of note, the build does have somewhat higher processor requirements than typical. Most procs supporting SSE4.2 should have the various additional instructions being tested in the build. I have yet to assess any performance differences, so YMMV.
Chromium 72.0.3589.0 (Official Build) (64-bit)
Revision 50ff782ea54a72162d479634088516802f0d96be-refs/heads/master@{#601638}
JavaScript V8 7.2.57
Octane Score: 35246
Speedometer: 79.83 ± 0.34
JetStream: 164.71 ± 0.66423
SunSpider: 269.9ms +/- 0.9%
Kraken: 1154.3ms +/- 0.9%
@marmaduke: Nice to re-see Webrtc patches! ;)
@Anon3918: It is a development version. So use it only for tests. RobRich and marmaduke are the specialists of experimentation! ^^
chrome://flags/#account-consistency
64-bit ThinLTO public build r602039 rescinded and replaced with r602251. The updated build has basically the same optimizations except for expanded compiler target instrction set definitions, which are back to LLVM defaults.
I was taking a closer look, and there are some nitpicky generational differences in subtargets of a particular instruction set I added to the definitions. I suspect they were not even used, but anyway to be safe.b I will keep the instruction modifications in experimental builds for now.
Chromium 72.0.3591.0 (Official Build) (64-bit)
Revision 50fe66c6897c9b56d22634b13d0a844e84174143-refs/heads/master@{#602251}
JavaScript V8 7.2.77.1
Speedometer: 81.50± 0.35
Octane Score: 35486
SunSpider: 270.2ms +/- 1.5%
Kraken: 1148.3ms +/- 0.9%
JetStream: 164.60± 5.6867
Mostly similar to before, but Speedometer picked up a tiny bit. JetStream on the other hand, is getting a larger variation in numbers across runs.
Overall though, the new optimizations are better than the previous ThinLTO builds.
With previous version "72.0.3587.0 (601406)" the bug is not present. Just FYI
I just pushed an updated build due to the Twitch bug resurfacing. No idea if project devs have resolved it, but it is worth a try IMO.
64-bit ThinLTO benchmarks are likely to remain somewhat static for the immediate future, as I think the current configuration is working decently for most mainstream systems. Otherwise I will continue pushing experimental builds as I think of other possible performance modifications to include.
Now to figure out what is breaking 32-bit ThinLTO during building. Hopefully just a revision issue.
32-bit embedded builtins support has (had?) a TODO support note in the arguments, and a related blog post mentioned late 2018 as a possible timeline. Suppose the v8 project devs might be trying to enable support; or maybe accidentially enabled it prematurely.
I would indeed mention somewhere that it is only for Android, to avoid confusion. And if it is of any use you can also list the vanilla Chromium version (https://www.bromite.org/chromium) as I see that no Android versions are here
@marmaduke the clientRects patch (like the canvas patch that you did not use) will add noise to the returned values. Such noise is not visible for the canvas and it should not cause problems for the rects. I think in some cases it may cause a slight wiggling Javascript-based reactive designs, but I am not sure it's due to this (never confirmed).
ungoogled-chromium has put some of these anti-fingerprinting patches under a flag, you might want to give a look at that too: https://github.com/Eloston/ungoogled-chromium/tree/master/patches/bromite
Chromium.70.0.3538.77.nosync.app.zip
https://github.com/macchrome/macstable/releases/download/v70.0.3538.77-r587811-macOS/Chromium.70.0.3538.77.nosync.app.zip
SHA1 989D5704263E9794835A59522D92B8688730611C
=====
csagan5's No WebRTC and canvas patches:
- Disable-WebRTC-by-default.patch
- ungoogled-chromium-Disable-webRTC-log-uploader.patch
- getBoundingClientRect-measureText-add-fingerprinting-mitigation.patch
- Canvas-fingerprinting-mitigations-for-image-data-and-webGL.patch
The canvas finger print generates random data, for most parameters. The clientrect can be (totally) blocked by not allowing frames (uMatrix). Canvas fingerprinting and device enumeration can be blocked by SafeScript.
No Sync • No WebRTC • No Widevine is a one-off build: Normally, No WebRTC and canvas blocking can be attained by using SafeScript and uMatrix/uBlock.
'Chrome Extension Downloader' (web site) do not works anymore, but You can use a Python script on GitHub at https://github.com/dn0z/Chrome-extension-downloader or:
1. CRX Downloader at https://online.standaloneinstaller.com/crx-downloader
2. Crx4Chrome works yet (but sometimes extensions are not updated) at https://www.crx4chrome.com/
chrome://flags/#page-almost-idle
chrome://flags/#proactive-tab-freeze-and-discard
I do not really follow the work, but I see tab discarding, memory pressure, ranking, etc. has been undergoing changes for awhile now.
There are possibly even bigger changes if running a current dev build.
Build v72.0.3596 x64 is actually v72.0.3594 x32 inside the zip file.
endless update... ;(
--------------
64-bit ThinLTO r603512 should be resolved.
This is Anon3941 - Thanks for sorting that upload, and for all your efforts here. Very much appreciated.
The OS installed on my laptop is Windows 10 Pro N - Version 1803 (OS Build 17134.191)
- - - - - -
- System
- Provider
[ Name] Application Popup
[ Guid] {47BFA2B7-BD54-4FAC-B70B-29021084CA8F}
EventID 26
Version 0
Level 4
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2018-11-01T11:49:26.709346500Z
EventRecordID 37933
Correlation
- Execution
[ ProcessID] 620
[ ThreadID] 748
Channel System
Computer DEATHSTAR
- Security
[ UserID] S-1-5-18
- EventData
Caption chrome.exe - Application Error
Message The application was unable to start correctly (0xc0000034). Click OK to close the application.
@YOLAWS Any third-party, active anti-virus/malware utilities installed? If so, perhaps try temporarily disabling such apps to test. Assuming that fixes it, you might need to whitelist chromium.
I have updated windows for OS Build 17134.376
I do not use any antivirus
Windows Defender is disabled
The Windows Firewall is disabled
I use Comodo Firewall v11.0.0.6728, I tried installing Chromium with it turned on and off.
I uninstalled the previous version of Chromium, I removed the user's profile, and cleaned the system registry with Revo Uninstaller, CCleaner and System Ninja every time before installing the new version of Chromium.
But the result is always the same, error 0xc0000034.
So I make the downgrade of Chromium to version 72.0.3594 and everything works fine.
Use the portable zip, instead of the installer, shouldn't happen there.
Your suggestion worked perfectly, thank you.
My best regards
In my case, I uninstalled the previous version of Chromium without deleting the profile and configures.
Here Chromium was installed in the following directory:
%USERPROFILE%\AppData\Local\Chromium\Application\
And the profile and settings were stored in the following directory:
%USERPROFILE%\AppData\Local\Chromium\User Data\
I downloaded the zip file with the latest build of the Chromium (chrome-win.zip)
And I copied all the files inside the uncompressed directory into the application path:
%USERPROFILE%\AppData\Local\Chromium\Application\
%USERPROFILE%\AppData\Local\Chromium\User Data\
make a copy of this folder to save your profile and settings, after formatting just copy it in the same place again.
I'm pretty sure that will result in a corrupted profile, and majority of your settings will be reset. I remember dealing with something like that in the past. Something like this:
This seem to be a bugfix release and corrects some errors (like do not downloads 'official' Chromium builds - issue nr. 107 by woolyss)
- GitHub page: https://github.com/henrypp/chrlauncher/releases
- direct download 'chrlauncher-2.5-bin.zip' at https://github.com/henrypp/chrlauncher/releases/download/v.2.5/chrlauncher-2.5-bin.zip
oof! The video performance seems to get slower and slower with each release.
1080p60 VP9 is dropping frames like crazy on Youtube. Tried with and without GPU rasterization disabled.
Firefox shows no dropped frames in 'stats for nerds'.
Planned obsolescence? Haswell should be good enough for this.
Tweaked the LTO instruction import limit. Enabled LLD tail merging. Enabled aggressive instruction combing for all optimization levels above zero. Enabled a new LLVM feature for hot and cold code block splitting. Enabled a new LLVM feature to help cull the importing and exporting of inline functions lacking local static variables.
Beyond the obvious file size reductions, the potential end-result performance idea is to perhaps allow for closer and/or greater hot code caching at the processor(s) via code size reduction and splitting hot from cold code blocks, while retaining the desired code optimization levels.
I will start a 32-bit build in a few. Maybe tomorrow to push it to public, assuming it builds.
windows 7 64-bit
when moving a bookmark to a bookmarks folder chromium abruptly exits to desktop without error message
I confirm. For example here : (Warning, be sure to use a Privacy & Ads Blocker before clicking !) https://www.20minutes.fr/sport/football/2366899-20181106 --> in the middle of the article the twitter photos are very blurry.
I will try to find better samples. Please Anon3966 provide samples too that we can open a bug on https://bugs.chromium.org
look forward to your next dev build w/ sync & codecs. thanks for sharing your builds!
----------------
FYI. My 32-bit r605443 does not include ThinLTO. Missing symbols issue, which IIRC, has been recurring with 32-bit ThinLTO builds lately.
----------------
There is an assigned priority two regression bug report for blurred images in certain tables.
"Working on code bloat, so r605443 performance could be a little YMMV. Ran some quick numbers, though, and the results looked generally okay here. Might have to do a little performance tweaking due to changes."
Turns out it was my fault. I installed "The Chromium Authors" 605211 and that build of theirs was horribly broken (Youtube said h264 wasn't supported) and it was dropping frames like crazy in VP9.
Switched to your 605443 and everything is hunkydory.
Note to others: Don't use out of process rasterizer or zero copy rasterizer with Haswell's GPU.
If you drag and drop a bookmark on another bookmark, in the bookmarks bar, the browser will crash.
Is anyone else having the issue with 70.0.3538.77 (587811) that they are logged out of every website on every Chromium restart?
Thanks.
chrome.7z | sha1: ccaf820c7c69024aae2fc78d4d57a3379546fa24
https://drive.google.com/open?id=1jAcZkYIJQ1CbxF3fOp_lR_xSNGd8bq2U
^Build format in 7z archive without layout changes, so do not extract it over an existing install. Extract somewhere else and run.
Also the chrome://flags are not accessible to noob users like me. Is there any wiki or a guide for the ever-changing list of chrome://flags with no vague descriptions.
@zxdc: chrome://flags are experimental. There is no more info elsewhere or in the source code.
1) chrome://flags are developmental and prototype features hidden in Chromium.
2) About #command-line-flags (switches), Chromium supports hundreds of them that may add features to the browser, change how features work, or remove features from it. Some switches are only useful to developers, as they enable them to test certain features in Chromium, while others have practical uses that users of the web browser will appreciate as well.
Note that if you look at chrome://flags to see if the command line (switch) option is active, the state might not be accurately reflected.
https://peter.sh/experiments/chromium-command-line-switches/#top-chrome-md used to exist in chrome://flags and got removed, see what I mean.
If the V8 snapshot issue can be resolved, it should be even faster. Plus toss in a better profile set and some of compiler optimizations as applicable.
The macOS sync build of 70.0.3538.102 seems to be broken at the moment. I did double-check the SHA1. When I unzip and try to start, I get this error message: "Chromium is damaged and can't be opened. You should move it to the Trash."
The current stable nosync version does work, but it has difficulty logging in to google services.
Must be just me then. Proof-of-concept build is sluggish. Opening incognito window you can visually see the lag.
Running benchmarks show significant performance hits.
The no sync versions works as designed!
Try this:
Chromium for 64-bit macOS - All Codecs - Saturday, 10 November 2018
Chromium 70.0.3538.102 (Official Build) (64-bit)
Revision 4bbeebac88fdc09c97265e47c205868bbd190497-refs/branch-heads/3538@{#1077}
OS Mac OS X
- ThinLTO and CFI
- SDK 10.14
- Xcode 10.1 (10B61)
- macOS Mojave 10.14.1 (18B75)
- LLVM/Clang 346586
Sync • WebRTC • Widevine
https://github.com/macchrome/macstable/releases/download/v70.0.3538.102-r587811-macOS/Chromium.70.0.3538.102.rev1.sync.app.zip
Chromium.70.0.3538.102.rev1.sync.app.zip
SHA1 D18A35BD281BCC6F06500D9F698BAD0ADD819BBC
A big part of the performance issue is the lack of V8 snapshot support. That, plus the lack of my usual compiler optimizations.
That said, I am actually showing local gains in a few benchmarks. Until the V8 snapshot issue is resolved, I might try doing partial PGO on certain other components besides V8.
I dropped project devs a line about the V8 issue, though, so let's see what happens there in the meantime.
@marmaduke: Thank you too! ;) I updated your comment.
@Evan: For fun, I quickly made a dynamic page to show the https://chromium.woolyss.com/correspondence-between-command-line-switches-and-flags-in-chromium/
https://bugs.chromium.org/p/chromium/issues/detail?id=896555
Potentially related:
https://bugs.chromium.org/p/chromium/issues/detail?id=377847
I don't know which 32-bit PortableApps version to download anymore
You can also try the following link: https://chromium.woolyss.com/?box=1
- green: third-party stable builds
- blue: third-party dev builds
- orange: official dev builds
About 32-bit PortableApps version, there is only the #win32-dev-thumbapps no-sync version on this site.
But you can find other PortableApps versions on the web. Note, they are often outdated:
- https://www.thumbapps.org/2016/10/Chromium-portable-32-64-bit-dev-nik-build-pgo-optimized-all-codecs-Widevine-sync-WebRTC.html (sync version)
- https://sourceforge.net/projects/winpenpack/files/X-Chromium/releases/ (no-sync version. 32-bit???)
Georges
France
Right now V8 embedded builtins are broken with Windows ThinLTO builds due to how snapshot assembly is being handled. It is the same issue I hit with the recent ThinLTO+PGO build.
I pulled the V8 project separately and successfully built it with ThinLTO after the following commit to to use plain assembly instead of inline assembly.
https://chromium.googlesource.com/v8/v8/+/bd8ed720cfa0533e4732490f5240380e234e469e
-------------------------
I got tired of waiting for an updated V8 roll. I remapped my local Chromium project's V8 to a separate local updated V8 project repository. ThinLTO is back working as expected. :)
Now to the Win64 ThinLTO r608640 build, which should go public in a few minutes.
LLVM is largely stock. Basically just disabled duplicate symbol checking. Default pass manager passes, default LTO function import limits, etc. Wanted a get a working Chromium build done ASAP without possible extraneous breakage in the mix.
As for LLVM options to build Chromium, I have enable the new pass mananager, newgvn, hot/cold splitting, etc. Quick benchmarks look okay. Even some improvements in Octane 2, MotionMark, and SunSpider.
I will get a 32-bit build cooking to hopefully push over the weekend.
btw on the experimental front, you still planning on playing around with the additional instructions? or is that being shelved?
I probably will revisit it with a future FullLTO+Polly build.
I'd like to request if someone can work together with other devs to make an open-source optimized stability-focused fork of Chromium that ignores/removes Google-specific crap they throw in while preserving the benefits of Webkit. I personally lack the knowledge to do so (though I'm trying to learn!) and wanted to see if any interest is there for this type of thing.
Just looking through Chromium flags you see all the junk they shove in to bloat the code for no discernible end-user benefit. So much bloat :(
@JC Denton: Thank you very much. Try ungoogled-chromium or iridium. Note on Windows, there are often outdated.
- https://github.com/Eloston/ungoogled-chromium
- https://github.com/iridium-browser/iridium-browser
chrome://flags/#enable-simple-cache-backend
@Anon4018: Please read the nik's comment at https://chromium.woolyss.com#comment-3574 He prefers to concentrate his efforts on the STABLE versions.
Wrong tag for v72.0.3582.0-r599622-Win64/chrome.packed-2018-10-16.7z
@sluTTY: Also thank you for your feedback. Solved issue.
Chromium 72.0.3616.0 (Official Build) (64-bit)
Revision 3cfde766316c5d856cbf7d8f5d3276a7644d5e0c-refs/heads/master@{#609328}
OS Windows
No Sync - WebRTC - No Widevine
SDK 10.0.17763.132 (Visual Studio 15.9.0): October 2018 Update version 1809
Same here, cannot delete cache on Win64 but can when reverting to previous build.
Chromium 72.0.3617.0 (Official Build) (64-bit)
Revision 756bea38c853ce40e3daba7f7fadf85b0920785f-refs/heads/master@{#609662}
OS Windows
No Sync - WebRTC - No Widevine - ThinLTO!
SDK 10.0.17763.132 (Visual Studio 15.9.0): October 2018 Update version 1809
Already try to send this message.
Anyone get a solution to get last Chromium with H264 on ubuntu 14 ?
Thank a lot for chromium build for windows, I use since years.
sudo apt-get install chromium-codecs-ffmpeg-extra
Already get H264 but want recent chromium (> 66) on ubuntu 14.04.
Seems not possible. recent Chromium PPA available don't build successfully recent chromium for 14.04
https://snapcraft.io/chromium
- Brave Browser Adblocker rel 1.0.6.9 has been released at november 23, 2018.
This build (.apk) contains Chromium 70.0.3538.110 of 'The Chromium Authors' and it's 'no-sync' so You cannot log in to Gmail.
✓ Google Play: https://play.google.com/store/apps/details?id=com.brave.browser
✓ GitHub sources: https://github.com/brave/browser-android-tabs
✓ GitHub builds: https://github.com/brave/browser-android-tabs/releases
- Brave Sync
coming soon
✓ GitHub: https://github.com/brave/sync/wiki/Design
About API keys on Mac:
- the instructions on this page to put them in a ~/.profile file don't work (tried it in 10.9 before and now in 10.11)
- I've succeeded globally defining the variables in ~/Library/LaunchAgents
Is there any way to make the ~/.profile method work? In this case, the instructions on this page should be modified accordingly as Chromium Sync doesn't seem to care about that file... (tried the last Marmaduke version)
@Anon4038: Brave is one of many #chromium-forks on Android. Nothing against this project. Just Chromium and Brave are different! ;)
@Aargl: I do not use macOS. The instructions about #google-api-keys must be outdated :/ Read this Github thread and its comments: https://gist.github.com/cvan/44a6d60457b20133191bd7b104f9dcc4 Please, then tell us which method works for you. I understood that it works with variables in ~/Library/LaunchAgents. But can you help more? Do you use "export", "launchctl setenv" or create a "plist" file, for example?
Thank you! But I mean just to another folder in the same partition, not to a different machine. My bad for not being specific about it.
the x64 --> 72.0.3623.0-r610957-win64 (ZIP) and (MINI-INSTALLER) is a copy of the x86 --> 72.0.3612.0-r608640-win32...
It seem you have tangled your folders again ;)
Pushed a 32-bit ThinLTO build.
Also pushed a 64-bit Polly+FullLTO build for the adventurous people. ;)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v72.0.3623.0-r610957-win64-polly
@Plecostomous: I technically can, but I have no personal use for them. Ya'll typically get the same (or similar) builds I use.
Struggling to find a solution.
@RobRich: Thank you for all! ;)
@Milos: Thank you for info. I updated the site.
@T: I agree with @Anon4050
Chromium 70.0.3538.110 (Official Build) (64-bit)
Revision ca97ba107095b2a88cf04f9135463301e685cbb0-refs/branch-heads/3538@{#1094}
OS Windows
No Sync - WebRTC - Widevine
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
ungoogled-chromium-70.0.3538.110-3_windows.7z (7-Zip archive)
Eloston is doing what Google should be doing (and perhaps is incapable of): a "self-contained", standalone, toolchain, tar ball build of Chromium. There is absolutely no reason why the casual user shoud have to download 14Gb of Google's finest crud to build an existing revision of Chromium.
@Anon4055: Yes with the Archive and Portable versions because there is no install. However, about the Installer version, you cannot do it but it is possible to change your #user-data-directory by passing the " --user-data-dir" command-line flag to the Chromium binary.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v72.0.3625.0-r611967-win64-pgo
Note, I enabled AVX support across the board for optimized code paths. YMMV.
I probably need to work on file sizes, which might further help with caching and data locality, as right now it is a slammed -O3 build for both compiler and link-time optimizations. Maybe also consider rolling in hot/cold code splitting.
Anyway, as is, it is delivering several positive benchmark returns on my Kaby Lake test system. :)
----------------
@Anon4055 Another trick with the mini_installer.exe is use a directory symbolic link.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink
You know Chromium is going to be installed to your Windows user appdata directory by default, so it is pretty straightforward to just create a symbolic link of the intended directory to wherever else you actually want Chromium to reside.
For example on my notebook, I have a directory symbolic link from the expected Chromium install directory on my OS SSD to another directory on a different Optane SSD.
mklink.exe /D C:\Users\RobRich\AppData\Local\Chromium D:\Chromium
----------------
BTW, for those building with ThinLTO on Windows. You likely are going to need to a quick code edit dealing with inline ASM to get V8 building with ThinLTO, at least for the near future.
C:\depot_tools\chromium\src\v8\src\snapshot\embedded-file-writer.cc
Comment out around line 410 or so, as it has been bouncing around in recent V8 revisions:
fprintf(fp_, ".def %s%s; .scl 2; .type 32; .endef;\n", SYMBOL_PREFIX, name);
The issue is link time optimization of inline asm. Apparently the streamer called by the ThinLTO compiler path does not understand the COFF directives in the inline asm. As a workaround, V8 inline assembly can build and run without the directives, which is what is being disabled in the above edit. AFAIK, it is just harder to debug the resulting code.
I have reported it to the V8 project. The Chromium guys working on LLVM and other compiler tasks already have some ideas on the table.
One thing, I notice it added as 'widevine' but see no widevine component in the program directory, also updating via chrome://components doesn't work (I assume as the url is nulled out), so does it actually have widevine?
Thanks
@Anon4058: Widevine functionality is included; but, you have to manually install the Widevine elements (The WidevineCdm folder from the respective version of Chrome).
@Anon4058: Use RobRich's method or the method that I initially proposed.
For the computer literate, download the standalone Windows Chrome installer, elect to install it as portable, BUT don't press enter, use your imagination - rummage around in the respective users appdata and find the approriate archive, extract the required directory, then cancel the portable install.
Though Microsoft have embraced open source the past 5-10 years, I didn't expect them to abandon their EdgeHTML engine so soon. I guess the abysmal usage rate, bugs, and man hours to maintain caught up with them.
https://www.windowscentral.com/microsoft-building-chromium-powered-web-browser-windows-10
Please, I would like some explanations about the "portable" editions of x86 & x64: I downloaded the latest portable zip files (v2.5) and launched the .exe one. On the first launch (the 19th 11.2018), it downloads correctly all the files but, when you pull an update (today), the launcher never gets it, and is launching the binaries I still got of the previous release. In fact, it never downloads the newer binaries, and I need to delete each time the bin folder to get the new ones. I don't know how to only do an update. If you still didn't get this issue, maybe a possible correction next time?
Bonus question: I don't know why a PortableApps version is not uploaded on PortableApps.com. I tried to ask if I could put updates, and I get no answers. So, I have to create it on my own... ^^
Thanks for answers
V.
@RobRich: Like ever, thank you for the Widevine install info.
@Anon4066: Exactly. I updated the site. Thanks.
@VIRGO77: Please check your mailbox, I answered you in your language! ;)
@earthsound: Thank you for info. The site traffic is unlimited ^^
MS Edge will use the Chromium rendering engine (Blink) on Windows 10. I am not surprised. MS Edge currently uses Blink on Android ; and ANGLE on Windows. Also, other Microsoft products use Chromium parts: MS Visual Studio Code, Skype, Minecraft. Read the #project part for more info. Moreover, the Chromium source code has an official mirror on Github (a Microsoft hosting service since 2018): https://github.com/chromium/chromium
And finally, Microsoft is #1 in the number of people contributing to its open source initiatives on Github since 2016:
- https://octoverse.github.com/2017/ (Check "Projects with the most contributors")
- https://octoverse.github.com/2016/
In the next few years, you will see more Microsoft products using Chromium.
Ciao!
System is a Haswell CPU with HD4600. Is this in preparation for planned obsolescence for when this goes main into Chrome?
Tried disabling hardware raster, oop, oop-d (viz compositor)...
Using 70.0.3538.110 (64-bit) Nik stable, going to update to latest 71.0.3578.80. Does 71 still require
--enable-features=AudioServiceSandbox
parameter?
However, if you prefer to disable the out of process Audio Service in general and put it back into the main chrome.exe process which is currently still what official Google Chrome is doing, you can use: --disable-features=AudioServiceOutOfProcess
Here are two working procedures, tested by me with Marmaduke's Sync versions:
Method 1) with ChromiumSyncEnabler (https://github.com/ezeeyahoo/ChromiumSyncEnabler)
- put Chromium_template and ChromiumSyncEnabler.py at the root of the current user (~/)
- put Chromium.app in ~/Applications
- in Terminal, type: python /Users/your_user_name/ChromiumSyncEnabler.py
- enter your API keys
N.B.: if you want to activate for all users, do the same procedure putting the files respectively in / and /Applications (I haven't tried, but I can't see why it wouldn't work...)
Method 2) creation of a ~/Library/LaunchAgents/setenv.ChromiumSync.plist containing:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" " https://www.apple.com/DTDs/PropertyList-1.0.dtd ">
<plist version="1.0">
<dict>
<key>Label</key>
<string>setenv.ChromiumSync</string>
<key>ProgramArguments</key>
<array>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_API_KEY</string>
<string>your_key</string>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_DEFAULT_CLIENT_ID</string>
<string>your_key</string>
<string>/bin/launchctl</string>
<string>setenv</string>
<string>GOOGLE_DEFAULT_CLIENT_SECRET</string>
<string>your_key</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>ServiceIPC</key>
<false/>
</dict>
</plist>
(with your_key being the corresponding API key)
N.B.: I don't know if the ServiceIPC part is needed or not, but it works like that. :-)
Of course, you can name the LaunchAgent setenv.ChromiumSync or anything you want.
• This is perfectly working in 10.11.
• In 10.9, you must create 3 separate LaunchAgent files instead (one for each key).
• I couldn't test more recent OSes, but I think it should work as in 10.11.
The choice between method 1 or 2 depends on wether you want to enter your API keys each time or not... ;-)
i replaced d3dcompiler_47.dll with the one from 70.0.3538.102 and the problem was solved...so i would like to know is there any other solutions or will the support for windows 7 be dropped?
----------------------------------------------------------------------------
Processor: Intel Core i5-540M
Graphics: Intel GMA HD Integrated Graphics
Operating System: Windows 7 Pro_SP1 (64bit)
@Aargl: I updated the site with your great #google-api-keys tutorial on macOS.
@WildByDesign: Like ever, thank you for your great help! ;)
@JCM: You are on a site about a free and open-source browser. Slimjet like many other #chromium-forks are closed-source. So I can check the Chromium source code, add similar features to Slimjet and compile it for my own needs. My question: why should I use Slimjet, Google Chrome or other? ^^
@Lukanz: Thank you for your feedback but I do not know how to solve your issue. Did you test to disable chrome://flags/#disable-accelerated-video-decode just to see?
About the support for windows 7, it will be dropped in a few years (not before January 14, 2020 - https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet). Personally, I think Chromium will be supported until 2021/2022 because many users and entreprises use this OS). Moreover, Microsoft is rebuilding its Edge browser on Chromium and bringing it to the Windows 7 and macOS (https://github.com/MicrosoftEdge/MSEdge). Note MS Edge and Google Chrome are the first browsers used in entreprise. Microsoft becomes very influential on the Chromium project, mainly for Windows. It is a good benefit for the open source community and users. All rendering engine of main browsers are now all open-source: Blink for Google Chrome, Vivaldi, Opera and MS Edge ; Webkit for Safari ; Servo for Firefox). For info, Firefox uses some stuff of Chromium too (#project).
i use portable chrome version from portableapps.com and replace the Chrome-bin folder with the one from chromium and with each update i do a clean install...and now starts the issue that since 70.0.3538.102 chromium starts (after a clean install) but i only get a blank site, so i replaced d3dcompiler_47.dll (10.0.17763.132) with (10.0.17134.12) and chromium open as usual and i checked the latest chrome build and they use d3dcompiler_47.dll (10.0.17134.12), so maybe thats the problem!
----------------------------------------------------------------------------
Processor: Intel Core i5-540M
Graphics: Intel GMA HD Integrated Graphics
Operating System: Windows 7 Pro_SP1 (64bit)
There are 2 solutions:
1- install 71.0.3578.80 and replace the d3dcompiler_47.dll with the older one from 70.0.3538.102
2- in my case just stick with 70.0.3538.102 and report the problem and hope that it will be fixed :)
yes im using the portable apps chrome launcher because i added some extra line to it e.g:
##########################################
RMDir /r "$EXEDIR\Data\profile\Default\Cache"
RMDir /r "$EXEDIR\Data\profile\Default\GPUCache"
RMDir /r "$EXEDIR\Data\profile\Default\Media Cache"
RMDir /r "$APPDATA\Temp\*.*"
RMDir /r "$LOCALAPPDATA\Temp\*.*"
RMDir /r "$LOCALAPPDATA\Google"
########################################################
and after each exit it cleans up all left behinds!
Chromium 71.0.3578.80 (Official Build) (64-bit)
Revision 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860}
OS Windows
No Sync - WebRTC - Widevine - All Codecs
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
I can actually get Ungoogled to build with the "Safe Browser" patch; but, Chromium fails to launch. I amended the Windows specific (Safe Browser) patch, but feel that the problem is with the generic patches.
Anyway, it's Eloston's build process that I like, and suggest that someone helps out and solves the Windows Safe Browser problem.
ungoogled-chromium-71.0.3578.80-1_windows.7z (7-Zip archive)
https://github.com/macchrome/winchrome/releases/download/v71.0.3578.80-r599034/ungoogled-chromium-71.0.3578.80-1_windows.7z
SHA1 EE4DB4459716B0AA95DF160EDC7E9AF438DC2359
@marmaduke: Idem for you. Now, you can update your "ungoogled-chromium" info yourself. Make sure "win64" is present in the download URL like your other releases. You forgot it! ;)
Moreover, if you make a ZIP archive like others, I can make a portable version (using chrlauncher).
@Lukanz: Here, there is a "name" field in the comment form! ;) Chromium 71.0.3578.80 and 72.0.3615.0 work well (basic browsing) on Windows 10 Pro 1803.
As I mentioned, they've been embracing OSS more and more over the years, but I don't think anyone outside of Microsoft expected them to add a Chromium based engine (ANGLE is not the browser rendering engine) any time soon.
After more info was released from various people within MS, it looks like they aren't abandoning EdgeHTML, just going to add chromium renderer as another option on the desktop. I.e, apps can chose the WebView based on chromium (see Kyle Alden's (Edge Project Manager) comment on this reddit post: https://www.reddit.com/r/Windows10/comments/a3pt19/microsoft_edge_making_the_web_better_through_more/eb8rhe5/?context=8&depth=9)
Also, I think that stat you pointed out is misleading. Their vscode only has 768 contributors. Does that github number (15k) include contributors to forks of the project (8,721), as well? *shrug*
i uninstalled my graphic driver and tried ms standard driver and had no problem loading the latest version... that means its time to send my x201 to retirement!
to anyone with an old graphic card: a workaround for chrome or chromium showing a blank screen replace d3dcompiler_47.dll with version 10.0.17134.12
Because tin foil, thats why. People are so concerned about privacy on the internet, that they forget about the other more important thing....actual real life. My company develops facial and behavioral recognition tech for retail tracking and surveillance to improve consumer shopping experience. What good is that facial recognition lock, when I can just 3D print your face?
About the official stat from Github, it was at the beginning of 2017. :)
Like I said before, I am not surprised that Microsoft choose Chromium for Edge (https://github.com/MicrosoftEdge/MSEdge). Why? It is simple. I follow the Chromium #project from the start and Microsoft products for years. You know that a web browser is a complex and big project. For huge projects, more and more companies prefer to use open-source projects to build their own products. Few examples: Mozilla Firefox is fully open-source (which uses Chromium parts too). Apple uses Webkit for Safari. Google created and share Chromium. Adobe uses Chromium parts in their all products. Opera abandoned its Presto engine for Chromium in 2015. Microsoft uses Chromium (Electron framework) for its excellent Visual Studio Code. It is a great success. Idem about Skype and Minecraft launcher. Microsoft also is the owner of Xamarin, which maintains the SkiaSharp .net wrapper for Google's Skia library. Microsoft uses some of Google's projects when it suits them.
About this "Edge" history, the main goal of Microsoft is not just to replace EdgeHTML by Chromium. Basically, it's the logical evolution of their whole business. It is the opportunity for Microsoft to improve their products and to develop other ones on all platforms/OS (IA-32, x64, ARM, Windows, macOS...Linux?) for their consumers (enterprise) and "simple" users. Their market grow even bigger. The competition is tough.
@Lukanz: Good to read that! ;) Thank you for your help.
@Anon4094: I agree with the following comments about #privacy . As you see, you are on a site about a free and open-source browser. Google Chrome like many other #chromium-forks are closed-source. So I can check the Chromium source code, add or remove features and compile it for my own needs. For example: 32-bit Chromium exists on Linux ; Not Chrome. Chromium can exist without Chrome! ^^ My question: why should I use Google Chrome? ^^ Chrome is a Google product. Chromium is a project of the open source community. Sure Google is the creator of this project. Chromium, being a big project, needs a huge infrastructure. Google has got it and shares the source code of Chromium. It is good for both Google and us! ;)
Look, don't patronise or under-estimate the intelligence of the average Western individual. We know that we are heavily surveilled, and that basically, the main function of market research is to encourage us to buy products that we do not need (on credit) and cannot afford.
Basically, who cares! Most people are quite satisfied to surrender freedom for a false sense of security.
At best, individuals can use "ad-blockers" to avoid/evade online "analytics". In the "real world", we have law enforcement that indulge in extra-judicial killings: aided by "commercial" analytics - IBM are pretty big in that field!
The Corporate Security Surveillance State existed long before Microsoft, Apple, Google, the advertising agencies, the UN, Nato, retail analytics, and the Stasi. In the West we call it Liberal Democracy, which is not particularly "liberal" or democratic: The Gilets Jaunes, Catalan pro-independence activists and so on.
A volley of rubber bullets, water cannon, stun guns, and incarceration awaits any individual who challenges the surveillance state.
Why attack people who just want to browse the net free from adverts for erectile dysfunction, mail order brides and so on; then to conflate the issue with the physio-demographics of the purchase of cheap plastic goods and low quailty food from Wal-Mart - and related questions of data-retention?
- https://dnschecker.org/#A/chromium.woolyss.com
- https://www.digwebinterface.com/?hostnames=chromium.woolyss.com&ns=all
- https://toolbox.googleapps.com/apps/dig/ (Google's DNS lookup - Put "chromium.woolyss.com" in the form input)
- https://threatintelligenceplatform.com/report/chromium.woolyss.com/7yj6kHKxUW
TLS/SSL also tested --> correct:
https://www.ssllabs.com/ssltest/analyze.html?d=chromium.woolyss.com
Tested under the latest STABLE versions of Chromium and Firefox.
If you use a DEV version, it can be a revision issue.
For info, IPv6 is disabled on my Network Adapter on Windows 10 (https://i.imgur.com/1i0KBKy.png)
Chromium for 64-bit macOS - All Codecs - Ungoogled - Friday, 14 December 2018
Chromium 71.0.3578.98 (Official Build) (64-bit)
Revision 15234034d19b85dcd9a03b164ae89d04145d8368-refs/branch-heads/3578@{#897}
OS Mac OS X
only for macOS 64
with codecs (h264, h265, flac, xvid, AV1, etc..)
official build
ThinLTO and CFI
Ungoogled
macOS SDK 10.13 - Tested under High Sierra, don't know if it works with 10.14!
No Sync • WebRTC • Widevine
https://github.com/macchrome/macstable/releases/download/v71.0.3578.98-r599034-Ungoogled-macOS/Chromium.app.ungoogled-71.0.3578.98.zip
SHA1 676FA199DF5DD7B4BEF3019D41584D05D56ABCBE
====
See you in the New Year!
You can also clear the host cache in: chrome://net-internals/#dns
https://github.com/Eloston/ungoogled-chromium/issues/619
At the: py get_package.py windows build\src\ungoogled_packaging or at the root:
Edit:
config_bundles\windows\patch_order.list
config_bundles\common\patch_order.list
Do not include the following patches (delete) from the respective patch_order.list:
ungoogled-chromium/windows/windows-fix-building-without-safebrowsing.patch
inox-patchset/0001-fix-building-without-safebrowsing.patch
iridium-browser/safe_browsing-disable-incident-reporting.patch
iridium-browser/safe_browsing-disable-reporting-of-safebrowsing-over.patch
ungoogled-chromium/fix-building-without-safebrowsing.patch
out\default\args.gn
#safe_browsing_mode=0 ***** Comment out
Select compiler by:
clang_base_path = "C:/clang.compiler"
packaging\windows\build.py documents the windows build process. (Study and improvise!)
=====
To manually build/amend a checked out Ungoogled:
set PATH=C:\Ungoogled\python-2.7.14.amd64;C:\Ungoogled\python-3.5.4-embed-amd64;%PATH%
set DEPOT_TOOLS_WIN_TOOLCHAIN=0
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat" amd64 10.0.17134.0
====
Eloston's build process is very good and elegant. You can even amend the process to produce "standard" and optimised builds!
It seems that "ungoogled" build from Marmaduke has the setting "Keep local data only until you quit your browser" enabled by default.
After launching and then closing this build for the first time, I started Chromium again and realized that many thousands of my cookies were gone.
Immediately switched back to the normal build from Nik, as I don't want to use software that may have "surprises" like this.
For the love of God...get a therapy dog or learn to run Chromium in a portable manner.
@Anon4110 & Anon4111: The "ungoogled-chromium" project removes Google stuff in the source code. It is recommended to read the FAQ before to use it.
https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq
@Evan: I used the Cloudflare DNS the whole day and did not see your DNS issue. Anycast works properly on my Web hosting service. I do not use a CDN. I sincerely hope it is a temporary issue. You are the only one I know with this issue.
@Dustyn: Nik is busy! ;)
@Evan: Probably you! ;)
https://community.cloudflare.com/t/fails-to-resolve-https-chromium-woolyss-com-and-https-woolyss-com/
@Anon4120: Sure, it may be possible. Example: https://community.cloudflare.com/t/archive-is-error-1001/
Are you able to connect to https://archive.is/ with Cloudflare DNS? I cannot. This is a famous website (https://www.alexa.com/siteinfo/archive.is). I have a SSL_ERROR_NO_CYPHER_OVERLAP result (https://i.imgur.com/WTcIcw3.png) on all stable browsers with an updated Windows 10 Pro 1803. WTF!!! I haven't got this problem with other #dns-services and my ISP's DNS. I understand in this case it is a misconfigured domain but why only Cloudflare DNS cannot resolve it?
Note I removed your confusing nickname ;)
@Anon4121: About codecs, follow the Nik's tutorial (#source-code).
Also when I others also have faced such issues I meant this - https://community.cloudflare.com/t/microsoft-store-doesnt-load-when-using-cloudflares-dns-server/49999
Regarding CloudFlare DNS. I have experience many random DNS resolution issues with seemingly random web sites since CloudFlare DNS inception. Not specifically your web site, but simply just random sites at random times. Usually I just have to refresh 4-5 times and finally the DNS resolution occurs in these random (yet somewhat rare) occasions. I had even spent time searching CloudFlare forums and found several threads on the same very issue. But yet, to this very day, this random DNS resolution issue still occurs. I only notice it once or twice per week, maybe. But I am surprised that such a big networking company of CloudFlare's stature cannot fix this as of yet.
It used to happen more often to the point where I switched away from CloudFlare DNS for several months. Now it does not happen as often and I've just learned to tolerate it in hopes that they will fix it one day.
Otherwise, me and all others from my zone will never be able to resolve this domain on CF.
>The "ungoogled-chromium" project removes Google stuff in the source code.
>It is recommended to read the FAQ before to use it.
Cookies have nothing to do with the "Google stuff". And FAQ never mentions that they are deleted by default in that build of Chromium.
Just like bookmarks or history, cookies may be valuable to the user, and deleting in them by default without any notification is a bad practice.
This makes sense only in the incognito mode or in the Tor Browser.
@Evan: I can manage DNS types (A, AAAA, MX, CNAME...) but I choose Anycast (https://en.wikipedia.org/wiki/Anycast) for authoritative name servers managed by my Web hosting service to improve the speed and reliability. I am not an expert. So I think badly I cannot fix this issue for "BOM" and other domain zones. Personally, my zone is "CDG" (Result of the following command in Windows Command Prompt: nslookup -class=chaos -type=txt id.server 1.1.1.1) and I haven't got issue like yours. I ask my Web hosting service.
- https://www.digwebinterface.com/?hostnames=chromium.woolyss.com&ns=auth
- https://www.zonemaster.net/result/47a5793a8bb7c939
@Anon4126: "ungoogled-chromium" is Google Chromium, sans integration with Google. It also features some tweaks to enhance privacy, control, and transparency (almost all of which require manual activation or enabling).
https://github.com/Eloston/ungoogled-chromium#ungoogled-chromium
Implicitly, I understand it works like with the "Incognito" mode by default. It is similar to Firefox Focus on Android and other browsers in this category.
> [...] deleting in them by default without any notification is a bad practice.
I totally agree with you. You can open a ticket at https://github.com/Eloston/ungoogled-chromium/issues
Thanks :)
@Anon4130: Search in these PPAs from Launchpad (by Canonical Ltd)
(Choose "AMD64" for 64-bit or "i386" for 32-bit):
- 67.0.3396.99: https://launchpad.net/~chromium-team/+archive/ubuntu/stable/+sourcepub/9240718/+listing-archive-extra
- 65.0.3325.181: https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/8872523/+listing-archive-extra
- Main page: https://launchpad.net/~chromium-team/+archive/ubuntu/stable
- All stable versions: https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+builds?build_state=built&build_text=chromium
especially the SDK with all the codecs included etc...that is not available currently at all online.
This will be a big help for any embedded Chromium...
I've been testing Marmaduke's ungoogled 71.0.3578.98 and it performs ok. However I have to admit that the lack of Translate support is a complete showstopper for me. I had confidence in the several times suggested Google Translate extension (aapbdbdomjkkjkaonfhkkikfgjllcleb) as a replacement, but after trying it, it's not working as expected: translate page functionality in the extension does nothing (disabled?), and having to manually select specific text to translate is not an option. Selecting all text, then translate just yields a wall of unformatted translated text.
Anybody knows of an extension that behaves like Translate (whole page) in the sync version?
@Starla: Personally, I use S3.Translator. It has many options.
https://chrome.google.com/webstore/detail/s3translator/debnnjfbneojbmioajinefnflopdohjk
Thank you so much for the ungoogled, all codecs, nosync stable build, your time/effort it takes making such possible is very appreciated.
It's been working great since I downloaded it on the 14th Dec, the ungoogled part is the most important thing to me I'm glad to see someone has picked up on it since the original branch was outdated for a long time, I hope you'll keep this ungoogled feature in your future updates.
@Jerry S3 Translator, handy addon for those few times when needed, thanks!
Here's some other extensions I use that some may be interested in:
- Browser Plugs (Anti-fingerprinting, Privacy and security, has whitelisting & more)
- Cookie AutoDelete (Privacy enhancement, Autodeletes browser cookies after leaving a website)
- Decentraleyes (Can speed up web pages & enhance privacy)
- Nano Defender (Protects uBlock Origin from websites seeking to get around adblockers with privacy intruding unethical measures)
- Dark Reader (Makes browsing the web easier on the eyes)
- Chrono Download Manager (Very useful feature packed download manager)
Why isn't there any chrome android fork which has support for chrome extensions?
Is there any (WONT DO) tag on such a issue on the upstream development of chromium android ?
So if i sound entitled but i think i am out of the loop on this issue.
I am currently pretty blessed to use the bromite fork of chromium maintained by csagan5 and i just wish there was any way to at least run userscripts on my android browser.
chrome://flags/#omnibox-ui-hide-steady-state-url-trivial-subdomains
Btw, I'm experiencing graphical glitches on latest Nik 71.0 stable after several minutes of usage: randomly, when loading a site without cached info, tab title is momentarily displayed in white text on black background, the page flashes (like in a display refresh) for a second or both. In addition, when navigating my favorites folder structure, parent directorys stay draw on window when accessing subfolders. Never experienced this before.
Same PC and latest Marmaduke 71.0 ug stable has not showed this behavior so far. I'm runing both builds as portable installations in separate folders (no interaction at filesystem nor registry level), and Nik's build glitchy behavior existed before I started testing Marmaduke's.
But note that Marmaduke build (like previous stables from Nik) does not exhibit that behavior with hw accel. enabled. Same PC.
--------------------
Scrolling back a few posts, interesting issue, though I have been using CF DNS (IPv4+6) for WAN DNS lookups on my residential LAN for quite awhile now while regularly accessing the woolyss.com domain.
@Evan Did you clear you local DNS cache(s)? All of them in your local path, from your PC to your router if configured to have one. In Windows for example:
ipconfig.exe /flushdns
--------------------
Been busy with personal life the past couple of weeks, so not much time to keep tabs on Chromium.
Just pushed an updated Win64 build. Win32 tonight or maybe tomorrow.
@RobRich: I am using quiet a while the portable version of your Chromium 64Bit for Windows. I noticed a file in profile directory, name is just 00000000. Size of this file is about 1,23GB. I never noticed this file before, when I used different versions of Chromium browser. I deleted the file, but the browser still works the way it should. You know what kind of file that is?
Kind regards.
Thank you very much to all users and developers! 😉
@Anon4135: Mumu has disappeared. Hope all is ok. He/she is ever welcome here.
@Francis: Thank you for your extensions list. Maramaduke will continue to compile the "ungoogled" version. He promised me!
@Bibiru: Get the previous version at https://github.com/henrypp/chromium/releases/tag/v71.0.3578.80-r599034-win64
@zxdc: Sorry, I know no Chromium fork able to run extensions (like uBlock Origin). This is why on Android I use Firefox Nightly (my primary browser) and Samsung Internet Browser. Both accept extensions (native for Firefox, apps for Samsung browser).
@Starla: It is ok. I am busy too! 😉 Like @Bibiru, replace Chromium by the previous version. Note I have no issue on win10.
@olle: Chromium uses a folder on C:\Users\%USERNAME%\AppData\Local\Chromium\User Data\Default\File System to store files (like "00000000") stored with the help of the File System API (https://developer.chrome.com/apps/fileSystem) which is part of HTML5. Use Chromium's chrome://settings/clearBrowserData dialog to clean it. Also, the "Click&Clean" extension can remove it.
@Evan and @olle: With Cloudflare DNS, I have no access to https://archive.is/ (Details at #comment-4122). I live in Europe.
This build contains:
● added 7zip packages support (issue nr. 120 - Marmaduke stable 'ungoogled-chromium')
● activate browser window when browser is running
● fixed bugs
- GitHub page: https://github.com/henrypp/chrlauncher/releases
- direct download 'chrlauncher-2.5.4-bin.zip' at https://github.com/henrypp/chrlauncher/releases/download/v.2.5.4/chrlauncher-2.5.4-bin.zip
https://github.com/RobRich999/Chromium_Clang/releases
https://github.com/RobRich999/Chromium_Misc/releases
Note, I do not create the portable versions. AFAIK, Jerry has server-side code packaging those using Henry's chrlauncher.
I am with Jerry, as it is probably cache data, hosted app data, or similar. No big deal deleting it. Even if hosted app data, it should reload -hopefully to a much smaller base state - if using the associated app or site again.
@Anon4152: Hello Henry! (I suppose). Thank you for work and updates.
Btw I've folder-compared fresh Nik's vs Marmaduke's. Aside from expected file data differences, folder structures (file naming and number) match. However Nik's has a exclusive "nacl_irt_x86_64.nexe", while Marmaduke's has a exclusive "chromedriver.exe".
I am Anon4152. but, unfortunately, I am not Henry++.
Periodically I browse 'chrlauncher' builds for other users (I use an archive build and I update my portable Chromium).
how do I remove it?
Since few weeks, I can't install any chomium version on my professional Windows 10 PC. The GPO don't download under IE and even when the download is OK with other web browser. Windows Defender SmartScreen doesn't want to launch any application from chromium with cause : Unknown editor...
More info don't unhide any "run anyway" button (GPO) and I can't disable SmartScreen in Windows Defender Option (GPO).
Is there a way to have a SmartScreen compliant chromium or a "how to" make it ?
@Anon4164: In Chromium, these extensions are hidden by default. In ungoogled-chromium, a patch show them. You can't/shouldn't remove them.
- https://github.com/Eloston/ungoogled-chromium/issues/86
- https://github.com/gcarq/inox-patchset/issues/25
- https://github.com/gcarq/inox-patchset/issues/132
@ChrisA: Chromium has no digital signature. Sorry, I do not know how "to have a SmartScreen compliant chromium" on a professional computer with Group Policy Object. Personally, I am the admin on my Windows 10 Pro 1809. So I disabled all SmartScreen options in Windows Security (https://i.imgur.com/l688QGF.png). Also, I can do it easily in the Local Group Policy Editor (https://i.imgur.com/v7dNZ8U.png) and MS Edge settings (https://i.imgur.com/ml6xjXc.png).
I've installed several Chromium 64BIT Portable versions - of course in different directories. The "chrlauncher.exe" file was replaced by the latest version 2.5.4. At first everything worked perfectly. But since the version 73.0.3654 from Nik appeared, all my - even stable versions - have been replaced by this version, while the old profiles have been preserved!
((Chromium 73.0.3654.0 (619063) • Friday, 28 Dec 2018))
Merry Christmas to you and your loved ones and a Happy New Year!
Chromium 73.0.3657.0 (Official Build) (64-bit)
Revision bf69dafea853e1f476fa39bdab9b581d894cf196-refs/heads/master@{#619264}
OS Windows
No Sync - WebRTC - No Widevine
- SDK 10.0.17763.132 (Visual Studio 15.9.2): October 2018 Update version 1809
- Clang\LLVM 350157 :- MingW64 Triple Stage Instrumented (PGO) [Xeon X5670]
- ThinLTO not working: will try LTO! Although, the compiler is instrumented (PGO/LTO) it should be possible to LTO Chromium.
Anyway, the Chromium build time is faster; subjectively, the browser feels snappier. And, I now have a better understanding of PGO.
D:\depot_tools\chromium\src\v8\src\snapshot\embedded-file-writer.cc
Around line 410 or so comment out as follows:
// fprintf(fp_, ".def %s%s; .scl 2; .type 32; .endef;\n", SYMBOL_PREFIX, name);
You do not need the .type directives for V8 assembly to build and run in Windows anyway. They are more about debugging.
About LTO and PGO, you can use them to build Chromium regardless if LLVM was built with them. I build LLVM with -O3, Polly, and a few other compiler options, though without LTO or PGO as they dramatically increase build times.
----------------
BTW, I also have switched to the LLVM monorepo format. If interested....
To get the code:
set PreferredToolArchitecture=x64
cd /D D:\src_builds\llvm-monorepo\llvm
git config --global protocol.version 2
git clone https://github.com/llvm-project/llvm-project-20170507.git llvm
git config branch.master.rebase true
I build the code using the LLVM checkout included with Chromium:
set PreferredToolArchitecture=x64
cd /D D:\src_builds\llvm-monorepo\llvm
git config --global protocol.version 2
git checkout -f
git pull
cd /D D:\src_builds\llvm-monorepo\llvm-build
cmake -DLLVM_TARGETS_TO_BUILD:STRING="X86" -DCLANG_PLUGIN_SUPPORT=OFF -DLLVM_INCLUDE_DOCS:BOOL="OFF" -DLLVM_INCLUDE_EXAMPLES:BOOL="OFF" -DLLVM_INCLUDE_TESTS:BOOL="OFF" -DLLVM_INCLUDE_BENCHMARKS:BOOL="OFF" -DLLVM_ENABLE_PROJECTS:STRING="clang;compiler-rt;lld;polly" -DBUILD_SHARED_LIBS:BOOL="OFF" -DCMAKE_BUILD_TYPE:STRING="Release" -DLLVM_ENABLE_ASSERTIONS:BOOL="OFF" -DCMAKE_C_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=bdver1 -mllvm -x86-experimental-vector-widening-legalization -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass=loop-vectorize" -DCMAKE_CXX_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=bdver1 -mllvm -x86-experimental-vector-widening-legalization -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass=loop-vectorize" -DCMAKE_C_COMPILER:STRING="D:/depot_tools/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER:STRING="D:/depot_tools/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang-cl.exe" -DCMAKE_LINKER:STRING="D:/depot_tools/chromium/src/third_party/llvm-build/Release+Asserts/bin/lld-link.exe" -G "Ninja" ../llvm/llvm
cmake --build
I then build my Polly optimized build using the above LLVM build:
cd /D D:\src_builds\llvm-monorepo\llvm-build-polly
cmake -DLLVM_TARGETS_TO_BUILD:STRING="X86" -DCLANG_PLUGIN_SUPPORT=OFF -DLLVM_INCLUDE_DOCS:BOOL="OFF" -DLLVM_INCLUDE_EXAMPLES:BOOL="OFF" -DLLVM_INCLUDE_TESTS:BOOL="OFF" -DLLVM_INCLUDE_BENCHMARKS:BOOL="OFF" -DLLVM_ENABLE_PROJECTS:STRING="clang;compiler-rt;lld;polly" -DBUILD_SHARED_LIBS:BOOL="OFF" -DCMAKE_BUILD_TYPE:STRING="Release" -DLLVM_ENABLE_ASSERTIONS:BOOL="OFF" -DCMAKE_C_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=bdver1 -mllvm -x86-experimental-vector-widening-legalization -mllvm -polly -mllvm -polly-detect-profitability-min-per-loop-insts=40 -mllvm -polly-invariant-load-hoisting -mllvm -polly-register-tiling -mllvm -polly-vectorizer=stripmine -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass-analysis=polly -Rpass=loop-vectorize" -DCMAKE_CXX_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=bdver1 -mllvm -x86-experimental-vector-widening-legalization -mllvm -polly -mllvm -polly-detect-profitability-min-per-loop-insts=40 -mllvm -polly-invariant-load-hoisting -mllvm -polly-register-tiling -mllvm -polly-vectorizer=stripmine -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass-analysis=polly -Rpass=loop-vectorize" -DCMAKE_C_COMPILER:STRING="D:/src_builds/llvm-monorepo/llvm-build/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER:STRING="D:/src_builds/llvm-monorepo/llvm-build/bin/clang-cl.exe" -DCMAKE_LINKER:STRING="D:/src_builds/llvm-monorepo/llvm-build/bin/lld-link.exe" -G "Ninja" ../llvm/llvm
cmake --build .
Set -march= accordingly, or IIRC, -march=native should work okay for a local build. Adjust the projects string if you want to add sanitizers or similar.
@RobRich: As usual, you are a fount of knowledge.
I've been tinkering with LLVM Advanced Build Configurations https://llvm.org/docs/AdvancedBuilds.html. The Apple 2-stage build works well - default compiler on my Chromium OSX builds; but, the Windows Multi-stage PGO fails to build. The Mingw-W64 instrumented build of LLVM is Ok, but is basic and cannot "bootsrap" itself.
I prefer to optimise the compiler, rather than to PGO Chromium. I just don't have the time! Life would be much easier if the Chromium authors issued some up to date legible development guidelines.
I have been poking at a generating an optimized component build that might speed the PGO process in Windows.
Thanks for your build... The file structure seems to have changed... Chrome.exe is now within the application folder.
Yours is the only build with no widevine, no-sync, but with all-codecs.
One issue which seems to have reared its head again in the last two builds though is the inability to log onto Google (gmail, etc...). You can log on in incognito mode. I read somewhere that this has to do with pathing (google assumes you have sync but you don't or something like that).
The file system changed to accommodate the portable installers/launchers.
Google API keys are required to access its services. i don't use Google services and don't supply API keys for the Sync build. I do have a set of API keys, but my preference is that the user supplies his or her own.
--------------------
Windows 64 bit LLVM\Clang 8.0.0 (trunk 350062)
Thursday, 03 December 2019
Four stage bootstrapped compiler, initially based on Mingw-w64 to create an instrumented LLVM, fed back into Mingw-w64 to create a (handcrafted) PGO LLVM, which is then bootstrapped to create a "pure" LLVM/clang.
Mingw-w64 x86_64-8.1.0-release-posix-seh-rt_v6-rev0
clang version 8.0.0 (trunk 350062)
Target: x86_64-pc-windows-msvc
Thread model: posix
clang.mingw-w64.compiler-E3-1270.7z
https://github.com/macchrome/compilers/releases/download/v.001-Win64/clang.mingw-w64.compiler-E3-1270.7z
SHA1 BBDC8A46BFCF6B71FB3AF66DD3469D6143F74322
Will/might pick up "fatal error: 'components/safe_browsing/proto/csd.pb.h' file not found -" when compiling Chromium 71.0.3578.98: just rebuild until the error goes away.
Will refine: crude but fast.
I've also built a RobRich spec compiler - and LTO'd the final stage.
https://www.pastiebin.com/5c2e43c24ff32
It defaults the setting to "dice_fix_auth_errors", which is apparently is no longer a selectable option in the about:flags options - just checked in a r619562 build.
----------------
Speaking of r619562, my Win64 build slated to go public today includes PGO optimization. Note, I am not profiling the entire browser, but I am instead profiling the code paths explicitly optimized for performance instead of size. YMMV, as fine tuning likely will be ongoing.
I also enabled AVX across all optimized code paths, so naturally, a processor with AVX support is now required.
@marmaduke - Can you please incorporate the fix referenced by RobRich in your next build?
Yes, on non-sync builds (all platforms).
https://github.com/UnnoTed/Ungoogled-Chromium-Extension-Installer or see "5. External extension installation" section on this page.
In fact I'm never really gone, I'm just follow this thread in ghost mode 👻.
I sometimes participate in @anon mode. A semantic analysis of all the answers could easily bring out all my participations! (hi NSA 👋)
I'm hiding because I'm ashamed that I have not done any updates on versions/codecs comparaison and because I don’t have enough time right now to customize a version of Chromium while Rob, Nik and Marmaduke are already doing a great job.
I don’t know how Rob do this, because customizing Chromium is a full-time job!
I have a lot of thing to do IRL but normally I would come back with real participation in a trimester I suppose.
sorry for vanishing, but I thought it wouldn’t be noticed!
Thank you all for your participation!
We are many more anons than you'd think , to follow and use your chromium’versions : keep going !
And of course, thank you to Jerry and Henry++, for providing us an interface to coordinate this all!
Happy new year for all ! 🎇 🎆 🎉
[ESXi 6.5, Windows 10 VM - 32 Gb ram, 2 x intel X5670 - 24 cores]
RobRich : 01:01:20.695 [hh:mm:ss.xxx]
Marmaduke : 01:03:10.445
Marmaduke - FullLTO : 01:01:51.945
I should have compiled Marmaduke - FullLTO with -march=westmere.
====== Compiler Specs:
robrich
C:\cmake\bin\cmake -G "Ninja" -DLLVM_TARGETS_TO_BUILD:STRING="X86" ^
-DCLANG_PLUGIN_SUPPORT=OFF ^
-DLLVM_ENABLE_LTO=Full ^
-DLLVM_INCLUDE_DOCS:BOOL="OFF" ^
-DLLVM_INCLUDE_EXAMPLES:BOOL="OFF" ^
-DLLVM_INCLUDE_TESTS:BOOL="OFF" ^
-DLLVM_INCLUDE_BENCHMARKS:BOOL="OFF" ^
-DBUILD_SHARED_LIBS:BOOL="OFF" ^
-DCMAKE_BUILD_TYPE:STRING="Release" ^
-DLLVM_ENABLE_ASSERTIONS:BOOL="OFF" ^
-DCMAKE_C_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=westmere -mllvm -x86-experimental-vector-widening-legalization -mllvm -polly -mllvm -polly-detect-profitability-min-per-loop-insts=40 -mllvm -polly-invariant-load-hoisting -mllvm -polly-register-tiling -mllvm -polly-vectorizer=stripmine -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass-analysis=polly -Rpass=loop-vectorize" ^
-DCMAKE_CXX_FLAGS_RELEASE:STRING="/MD -Xclang -O3 /Og /Oi /Oy /Ob2 /GF /Gy /Qvec /DNDEBUG /Gs- -march=westmere -mllvm -x86-experimental-vector-widening-legalization -mllvm -polly -mllvm -polly-detect-profitability-min-per-loop-insts=40 -mllvm -polly-invariant-load-hoisting -mllvm -polly-register-tiling -mllvm -polly-vectorizer=stripmine -Xclang -vectorize-loops -Xclang -vectorize-slp -Rpass-analysis=polly -Rpass=loop-vectorize" ^
-DCMAKE_C_COMPILER:STRING="C:/clang/build/bin/clang-cl.exe" ^
-DCMAKE_CXX_COMPILER:STRING="C:/clang/build/bin/clang-cl.exe" ^
marmaduke - (Mingw-w64 instrumented base)
cmake -G Ninja ^
-DCMAKE_BUILD_TYPE=Release ^
-DLLVM_ENABLE_RTTI=1 ^
-DLLVM_ENABLE_LTO=Full ^
-DCMAKE_INSTALL_PREFIX="c:/Clang.Marma" ^
-DLLVM_TARGETS_TO_BUILD="X86" ^
-DCMAKE_C_COMPILER="c:/Clang.Marma/bin/clang-cl.exe" ^
-DCMAKE_CXX_COMPILER="c:/Clang.Marma/bin/clang-cl.exe" ^
-DCMAKE_LINKER="c:/Clang.Marma/bin/lld-link.exe" ^
-DLIBCXXABI_USE_LLVM_UNWINDER=YES ^
-DPYTHON_EXECUTABLE="C:/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe" ../llvm
It's confusing for users who find there way here from Google!
The installer LOOKS like the latest version, since it's the newest one listed and it was released last month.
But if someone goes to the homepage and clicks the Mac tab (which was easier for me to find than the OS menu above), THERE'S the latest build!
https://chromium.woolyss.com/download/en/#mac
----------------------
Aw damn - actually the homepage doesn't even have the tabs I mentioned.
I can't even find the page for the link I posted.
Seems the only way to get there is by going back to Google and clicking a different link.
https://www.google.com/search?q=chromium+download
Why's it so difficult to find the latest Chromium?!
Next time I'll use MacUpdate.
Perplexed out.
> Why does this page not have the latest version posted?
This page has the latest Chromium versions (#mac-64-bit). Check the date ! ^^ You will see that the latest version is the orange box ("The Chromium Authors").
> the newest one listed and it was released last month.
What are you talking about? There are STABLE and DEVELOPMENT versions. Sure, they are different and released differently.
> the homepage doesn't even have the tabs I mentioned.
Here, you are on a simple site with only 2 pages and they are both linked:
- This page is the main page with ALL Chromium versions
- https://chromium.woolyss.com/download/ is a simplest multilingual page about ONLY development builds (official repository).
> Why's it so difficult to find the latest Chromium?!
Ask Google! Go to the official site at https://www.chromium.org/ and try to download Chromium! ;) No. Seriously, I explained that in my #notes
> Next time I'll use MacUpdate.
Ok. https://www.macupdate.com/app/mac/36244/chromium uses the FreeSMUG build released 1 month ago. This build is also on the #mac-64-bit section.
The actual needed setting is no longer in the user-accessible options. I instead change the default option in the field trial config at build time, which means the flag ideally should be at default before installing and left alone afterwards after installing the build.
A few possible ideas:
1. Reset your about:flags, re-install my latest build, and restore your other flags as desired.
2. Add " --account-consistency:dice_fix_auth_errors" to the chrome.exe command line.
3. Add " --force-fieldtrials=AccountConsistency/dice_fix_auth_errors" to the chrome.exe command line.
YMMV, as I have not tried these ideas since Gmail is working here. I would think #1 should have a decent chance of working, though.
Tried all of those three possible solutions, still doesn't work. I also never touch that account-consistency flag at all by the way.
Another idea. Make sure you have "Allow Chromium sign-in" disabled in the about:settings options.
@Milos: You can only mute a whole site (https://i.imgur.com/dkHhAzB.png). Nothing to do under chrome://flags. You cannot disable sound per tab. Maybe an extension exists for that.
Woah, you're right. Thanks a lot.
It is mostly a "get it working" build, though performance looks acceptable for general use IMO. There appears to be a mild JS regression in Octane 2.0 and maybe Basemark Web 3.0 scores. Not sure if build or revision related right now. Will take a look.
My main browser is now ➜
https://github.com/henrypp/chromium/releases/tag/v71.0.3555.0-r591690-win64
What drove me nuts is here 😠 ➜
https://bugs.chromium.org/p/chromium/issues/detail?id=892045#c6
This 71.0.3555.0 version is :
★ The latest compatible with chrome://flags/#top-chrome-md ,
★ Which allows me to have a shit tons of favorites in the bookmarks’bar ,
★ Which allows me to have fine, angular, discreet and racy tabs ,
★ Which allows me to mute sound with only one click on tabs ,
★ Which is perfectly secure thus far and compatible with most codecs (Thank to Nik) ,
★ Which run with Google accounts, Youtube accounts and so on ,
★ Which since 4 months of use almost 24 hours a day, has never presented a single bugs or slowdown!
★ Etc.
I am now part of users who unfortunately do not update anymore ¯\_(ツ)_/¯ because updates either brings more ads and/or spywares (Android), or either break something!
So, Rob’s versions, UnGoogled’s version, etc. are now my secondary browsers. (Thanks to Henry++ which makes them 1oo% portable so therefore they can run side by side at the same time)
Good luck to those who are with versions 72 or 73!
Oh! And last but not least : I agree that there is a slight difference in benchmarks (JS) between Rob’s 621140 version and this 591690’s version for example ; but it’s totally indistinguishable in real-world usage!
As like our old Rob would say : « YMMV! » 😉
https://pastebin.com/e8rgritt
Basically changing -O3 to /O2, enabling the new pass manager and newgvn, and tweaking a few compiler+linker options.
Change "-march=" according to your system's processor architecture, or remove completely for a more generic x86-64 SSE2 build. If going the generic route, alternatively consider adding "-mavx" or "-mavx2" to enable those instruction sets if desired.
cd /d c:\whatever
svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk clang-tools-extra
svn co http://llvm.org/svn/llvm-project/lld/trunk lld
svn co http://llvm.org/svn/llvm-project/polly/trunk polly
svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk compiler-rt
svn co http://llvm.org/svn/llvm-project/libcxx/trunk libcxx
svn co http://llvm.org/svn/llvm-project/libcxxabi/trunk libcxxabi
svn co http://llvm.org/svn/llvm-project/libunwind/trunk libunwind
and updated by:
cd /d c:\whatever
svn update llvm && svn update clang && svn update clang-tools-extra && svn update lld && svn update polly && svn update compiler-rt && svn update libcxx && svn update libcxxabi && svn update libunwind
Just update util the revision is consistent.
For a particular revision use .../trunk@XXXXXX
https://llvm.org/docs/Proposals/GitHubMove.html
https://github.com/llvm-project/llvm-project-20170507 was created during development of a monorepo as imported from the http://llvm.org/git repository.
Alternatively, it appears the more official https://github.com/llvm/llvm-project monorepo now is available as well.
The same version of stable chrome works on exact same settings.
To be clear, websites can use microphone, but WebRTC doesn't pass along the microphone input for some reason.
It used to work on some previous version (possibly 69). This isn't related to the AutoPlay changes, as it's the same even with those disabled via chrome:flags.
http://lists.llvm.org/pipermail/cfe-dev/2019-January/060795.html
https://chromium.googlesource.com/v8/v8.git/+/69e36a95be5ced4dc4c6a640d3c70ba24e8db860
I could revert the code, but the V8 devs claim the previous code does not do much (if anything?) for most real-world usage scenarios anyway.
Those into benchmark testing should set a new baseline regarding current dev releases IMO.
conducting a little research on this. And he in fact bought
me breakfast because I stumbled upon it for him… lol. So let me reword this….
as you guys (possibly RobRich) might remember, I am using your great builds to generate Forex trading strategies via https://forexsb.com/expert-advisor-studio and until recently have been using the excellent Lawlietfox, as it outperformed all Chromium builds on my TR 1950X CPU that I´ve previously tested (although always been using your Chromium builds for my private surfing). However, I am repeating these benchmark tests from time to time and did so again today. I thought it might be interesting to create a video of that benchmark for you guys/builders, comparing the trading-system generating/validating between Lawlietfox and the three latest excellent Chromium builds by RobRich (73.0.3667.0 (621140)), Marmaduke (73.0.3657.0 (619264)) and Nik (73.0.3654.0 (619063)) from this site.
PLEASE TAKE NOTE THAT I`VE LABELED THE INSTANCES WRONGLY, SORRY ABOUT THAT! So the lower left side is NIK and the lower right side is ROBRICH.
https://www.youtube.com/watch?v=8gFQchCtKtY
The observations from the video are interesting:
- Lawlietfox (Firefox) does not seem to do any parallel processing for Javascript while Chromium does it extensively as we can see by the CPU usage spikes (most likely serial vs parallel garbage collection because not much more could be run in parallel with that kind of task that I am running).
- If forcing every browser to just one CPU core (to make comparing to Firefox fair), all the Chromium builds still do better than Firefox, but interestingly RobRichs build is absolutely killing it on one core, leaving the others behind by a good margin (that was very interesting to see and I wonder why that is such a huge difference).
- If allowing the usage of all cores, all the Chromium builds are much closer, but RobRichs build is still making a slow but steady front-run the longer they run. Nice!
- Overall Chromium seems to use a lot more memory (almost double at certain places) for Javascript than Lawlietfox / Firefox does (not a problem though if speed is that much better).
Hope there is something interesting to take away from that test for our great builders here - big thanks again for all your ongoing efforts, it really pays off!
Cheers,
Lorenz
Interesting viewing. My builds tend to be generic x86-64 SSE2 (the lowest common denominator), thinlto and /02 optimised. RobRich is known for his performance builds.
You have the computing power, I suggest that you build Chromium specifically for the TR 1950X CPU (-march=znver1), and use optimisation strategies such as Polly.
hi and thanks for the feedback and all your efforts with your builds - amazing work throughout and for all these years already! Thanks :-)
Yes, I thought something like that already but still wanted to test things in-depth to see if the real world results (for my case) show the same outcome. I would have guessed that RobRichs builds are the fastest for me, but who knows, better test! :-)
Your idea about building Chromium specifically for my CPU is something I´ve been thinking about too - squeezing out the best performance/watt is what I am always looking for, given the high electricity prices in Germany. But honestly, I have no idea how to build it on my own. Yes, I am a sys-admin and Windows fanatic, but I have only once compiled Diskcryptor in VS 2015, but that was about it already. OK, I can code in Javascript and Java and!.... Q-Basic!!! :-) Haha...
If you feel like it and have a spare minute or a tutorial, I would surely like to know how I would go about building Chromium especially for my CPU and possible also run Polly (whatever that is) and PGO/profiling for that specific forex app only to speed it up further? That would surely be very great.
Thanks so much,
Lorenz
- https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
- https://github.com/henrypp/chromium/blob/master/building_chromium_gn.md (set GYP_MSVS_VERSION=2017)
Once the infrastructure is in place, and you've done your initial Chromium build then you can do a bespoke build: LLVM\clang will have to be compiled from source. Initially, concentrate on getting a functioning build system.
If you are willing to make the effort, assistance will be available. I started from scratch and have been assisted by Nik and particularly RobRich in the fields of program optimisation and compiler specification. You should also consult Mumu.
I would encourage others to build Chromium.
Thanks so much once again.
@Evan: Good news. Thank you for your feedback! ;)
----------------
I am now gathering enough profile data? o.0
Instead of profiling select code paths, I am now PGO profiling most of the browser.
I also rolled in additional tweaks for opt levels, register allocation, instruction scheduling, Polly, etc. I am expecting code bloat, which I might have to look at later if it gets ridiculous.
Hopefully I should have a working build ready for public distribution over the weekend.
Stupid question: would it ever be possible for you to make a custom build for the AMD Threadripper 1950X with AVX(2)(?) support? I would really love to see if it would make a performance difference against your normal high performance builds. If that is the case and they´d really be faster ~+10%, I think I´d be tempted to go and try to learn to make my own builds. But not sure if it is worth it right now to learn and build everything from scratch, just to notice it´s not really faster than your great builds :-)
Thank you so much,
Lorenz
For those benchmarking, take note there was a recent change in V8 preparsing, so I suggest establishing a new baseline for comparison.
Of note, I did a quick run of MotionMark 1.1, which returned a substantial increase here. YMMV, of course.
As for that AMD build, it would just be interesting to see if that would really bring any extra gains compared to your "generic" high performance builds, or if it comes out about the same.
Thank you so much!
Thank you very much for your all 32-bit Chromium.
But on my Windows 7 Ultimate 32 bit.
73.0.3677.0 (624317) • Saturday, 19 Jan 2019 doesn't start at all.
Windows File for help bug.
C:\Users\F\AppData\Local\Temp\WERA525.tmp.WERInternalMetadata.xml
C:\Users\F\AppData\Local\Temp\WERB194.tmp.appcompat.txt
C:\Users\F\AppData\Local\Temp\WERB241.tmp.mdmp
It probably is AVX support, which I will roll back to the default SSE2 for SIMD in 32-bit builds.
I will push a new 32-bit build this weekend.
Processor:
Name : Intel Core 2 Quad Q9950
Code Name : Yorkfield ; Max TDP : 95.0W
Package : Socket 775 LGA
Technology : 45 nm ; Core Voltage 1.124 V
Specification : Intel Core 2 Quad CPU Q9550 @ 2.83GHz
Yorkfield = Penryn = no AVX support
I will remove the AVX dependence in my modified 32-bit build and push an update.
@Anon4242 Probably the same thing for the installer, too.
Does it automatically take it from the official chromium site? Or does someone manually input it? I notice from time to time it's a little slow on the update.
Like for example if https://download-chromium.appspot.com/ has version 624484 then this site would not have it until like maybe over 10 minutes later.
Just curious.
I´ve just "finished" a test of your previous 73.0.3667.0 build vs your new 73.0.3677.0 build from 19. January. I´ve let them both run https://forexsb.com/expert-advisor-studio-app for just 20 minutes and there wasn´t a huge difference (within the margin of error), but then I´ve let both run for 6 hours and here is the outcome:
73.0.3667.0 = 175370 systems
73.0.3677.0 = 176500 systems
So the new build is ahead for sure now, if just slightly, but it is! Good work! Always pushing the boundaries Rob!! :-)
Would be eager to test an AMD build as earlier discussed, but I understand your time is limited and priceless of course. Big thank for all the good work!
Cheers,
Lorenz
> Does it automatically take it from the official chromium site?
Yes...and no. All is official but, Chromium being a big project, there are different sites linked together. Check the #links to understand! ;)
> this site would not have it until like maybe over 10 minutes later.
My server get more info (ex: the Chromium version, checksum hash...) and cache its result. It use different official Chromium sites to get all info. The process is completely independent than the official site. Moreover, my server is not a powerful Google server like the one of https://download-chromium.appspot.com/ where the user simply ask the latest Chromium version.
After launching and updating the browser does not start. Error message: 0x000001d. Please tell me how to solve the problem.
Wait for him or choose a stable one.
Check previous comments (Search "73.0.3677.0" term, for example).
https://www.cpuid.com/softwares/cpu-z.html
----------------
Updated 32-bit build pushed. A processor with AVX support is *not* required. :)
----------------
Building LLVM with Visual Studio 2019 Enterprise Preview:
https://pastebin.com/31TWuSkN
Big Big ; Thank You Very Much !
Cheers.
And many thanks for your work and time to do build for us
Others are at https://ungoogled-software.github.io/ungoogled-chromium-binaries/
That's why I ask for the previous one, which is 69.0.3497.100-2.
I tried to build the 69.0.3497.100-2 myself but it's falling due to safe browsing, which I can't fix with my knowledge.
https://github.com/uBlockOrigin/uBlock-issues/issues/338
https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2
You think we could see some custom optimized builds of firefox if these changes go ahead and it nukes ublock origin?
Apart from this I was still anyway wondering why there are so few optimized FireFox builds. I bet if RobRich would build Firefox, it could even beat Chromium in terms of performance ;-)
In a way, I knew this was coming. Google has tried to do this before and backed down in the past. They are an ad-driven company and uBlock Origin was "getting in the way" of that. I'd hate for that to happen to Chromium as well and hope it doesn't since a certain amount of privacy is stressed using Chromium.
Should that extend to Chromium, I will no longer use it. It's that simple.
:^(
-gorhill: "this would be the death of uBO and uMatrix."
-gorhill: " I won't work to make uBO less than what it is now"
-gorhill: "There are four listeners in the webRequest API which can be used in blocking mode: onBeforeRequest(uBO, uMatrix), onBeforeSendHeaders(uMatrix), onAuthRequired, onHeadersReceived(uBO, uMatrix). uBO uses two of them, uMatrix uses three of them."
-gorhill : "With this information on hands, everybody is free to decide for themselves."
https://github.com/uBlockOrigin/uBlock-issues/issues/338
Is the death of Chromium.
And time to switch to other browser when implementation of Chrome extension manifest v3.
Anyone knows for when it's planned ; the implementation of Chrome extension manifest v3 ???
Too bad.
I really love Chromium.
https://www.reddit.com/r/firefox/comments/aiqvcp/chrome_extension_manifest_v3_could_end_ublock/
In other words, google wants more money and sees adblocker as threats, then implement this.
On other hands, google force firefox to adopt it as well if they still want to be given money.
I doubt that Google can do any enforcing on Mozilla, if they´d try that, they´d have the next antitrust campaign here in the EU in no time. Believe me, they don´t want to risk that, after they´ve paid billions to the EU already for similar cases (Android).
Version 74.0.3684.0 64-bit (Marmaduke) can not be loaded via CHRLAUNCHER. An error message appears.
@Marmaduke: Thank you very much for your releases ! ;)
https://github.com/henrypp/chrlauncher/issues/123
Ironic they even recommend uBlock Origin on that webpage. I guess when Google orders them to, it will be removed.
Send e-mails.
To defend uMatix and uBlock Origin, they want kill
And the other extensions threatened with death also by Chrome extension manifest v3:
- community@chromium.org
- dknox@google.com
- groby@chromium.org
Strap yourselves in and feel the G's!!
I don't know if it's made on purpose, but both Marmaduke's versions (sync and nosync) point to the same link, currently: https://github.com/macchrome/macstable/releases/download/v72.0.3626.81-r612437-macOS/Chromium.72.0.3626.81.sync.app.zip
I've noticed it a few months ago, when I came back to Chromium (I was freezed to the last MacOS 10.9 version until I updated to 10.11), but I thought it was a temporary oversight that would be fixed with the next release... ;-)
@Aargl: Hi! Exactly. It was my mistake. Sorry! Now corrected. Thank you for your report ;)
@Marmaduke: Big thanks for your updates! ^^
Your versions are greatly appreciated! :)
After a bit of research, it looks that the ServiceIPC has been deprecated more than 10 years ago! :-D
MacOS Console testifies it showing "The ServiceIPC key is no longer respected. Please remove it", which leaves no doubt about it...
So, you can remove the line <key>ServiceIPC</key> in 2. Method with a plist file — and the line "N.B.: I don't know if the ServiceIPC part is needed or not, but it works like that. :-)" under the code area.
Rising Trojan.Mingc!1.660C (CLOUD).
I suggest that you breakout Wireshark and monitor the situation. Let's say that there is a "miner": who put it there? Not I! So, it must be the work of the Chromium Authors, and its organ grinder.
Verify your suspicion. If your findings are confirmed, I will be the first to give an opinion.
There is absolutely no reason to doubt the veracity and integrity of any of my Chromium builds: I and my associates use them in our business and personal lives.
https://github.com/henrypp/chrlauncher/issues/123
@Aargl: Big thank you for your help. I updated your part.
@Anon4289, @marmaduke: Do not worry! On VirusTotal, there is one bad result and this result come from a Chinese antivirus (Rising company) only used in China. Where is the official website? http://www.rising-global.com, http://rising.com.cn? Only in Chinese. Where is the SSL/TLS certificate for these sites selling security products/services?
https://www.virustotal.com/#/file/053ed8e318763f06742577f75c31fb82c4a3731ce43a13416e3b77ef7caa61b0/detection
Mistakenly included Widevine for Mac, previous downloaders should delete the Widevine folder.
how do i stay logged in chromium browser sync after clearing all cookies?
the chromium sync gets paused everytime i clear my cookies.
The real thanks should go to Eloston. I'm working on solving the safe browser issue: too may files have been pruned.
@RobRich
I've been experimenting with clang windows PGO builds! I've insrumented all of the C++ (that does not reset flags_cc) code and specifically Skia, V8 and Blink - renderer only. The size of chrome_child.dll is 362Mb. I didn't instrument any of the C code, apart from FFMpeg, because of problems with mksnapshot.exe failing to link; but, I managed to instrument V8, so I think that it should be possible to instrument all of the C code as well.
At the moment, I am generating profile data, approximately 400Mb for every launch of Chromium. I develop Chromium on a virtual machine and am surprised that the instrumented binary will produce profile data on a physical machine: whether the profile data is valid remains to be seen. Anyway, my thought is: surely it should be possible to produce a canonical set of profile data for a particular/specific build of Chromium.
https://github.com/henrypp/chromium/tags (stable and dev builds of Nik, for Windows)
My primary 17" DTR notebook was down for a SSD replacement. Cooked a 512GB SATA SSD, likely with PGO profiling. o.0 Replaced with a 512GB NVMe SSD drive, plus an 1TB SATA HDD for profiling and similar.
I should have a moderate GPU upgrade for the build box arriving soon, too, so I can perhaps move PGO profiling back to it. Profiling graphics benchmarks is not too fun with the existing GeForce GT 730, thus why I have been using my notebook with a GTX 1050m.
ARES-6: 29.07 ±0.74ms 29.39 ±0.37ms 29.42 ±0.21ms
MotionMark1.1 295.57 ±7.35% 299.59 ±2.42% 306.19 ±3.13%
Speedometer2.0 74.2 ± 0.85 74.4 ± 0.75 74.5 ± 0.82
JetStream 1.1 153.78± 1.4337 153.64± 2.5579 153.95± 4.1777
PGO:
ARES-6: 28.85 ±0.73ms 29.39 ±0.30ms 29.48 ±0.28ms
MotionMark1.1 173.47 ±33.78% 218.23 ±9.82% 265.16 ±3.66%
Speedometer2.0 69.02 ± 0.53 69.12 ± 0.28 69.15 ± 0.42
JetStream 1.1 153.36± 2.6664 154.95± 1.1176 153.86± 1.0967
than below, but give the following a try. Remember to change the drive
letters and directories accordingly.
https://pastebin.com/RK06uUu2
Thank you very much.
I have some preliminary benchmarks @Anon4299 - pressed the space bar and the comment was send before I had time to format and explain.
Ah, "Redundant COMDAT folding": I've been having serious problems with clang 9.0.0 with COMDAT - particularly when trying to do a VS 2019 derived bootstrap build of clang/llvm, and when building Chromium. I greatly appreciate your feedback.
I don't know if PGO contributes anything to the Chromium build process, but at this moment in time am more interested in understanding/mastering and refining the concept.
Also, yeah, there have been changes in COMDAT processing. I had to roll back some LLVM code to get a recent internal 64-bit Chromium build done. Looking like I will be poking at it again wth my next PGO build.
https://github.com/Eloston/ungoogled-chromium/blob/master/patches/ungoogled-chromium/windows/windows-disable-reorder-fix-linking.patch
I also have thought about custom ordering, but it requires even more build passes, especially to the already convoluted PGO process.
https://chromium.googlesource.com/chromium/src/+/master/docs/win_order_files.md
A small report about your MacOS Chromium.72.0.3626.81.nosync after a week use on 10.11.
At first launch, all my extensions raised alerts notifications saying they crashed and need to update (I don't remember the exact message...) — never seen that before — but since then everything seems to work ok.
Only thing: when I click the "Update manually" button in chrome://extensions, a black box appears on the left-bottom part of the page saying it's updating, and never disappears until I close the window.
I've found an extension that has been updated yesterday, so apparently auto-update is working.
@RobRich: Thank for your email. I updated and cleaned your comments.
D:\src_builds\llvm-monorepo\llvm\lld\COFF\InputFiles.cpp
Comment out the else error message as follows around line #509:
if (Config->ForceMultiple)
warn(Msg);
// else
// error(Msg);
D:\src_builds\llvm-monorepo\llvm\lld\COFF\SymbolTable.cpp
Comment out the else error message as follows around line #348:
if (Config->ForceMultiple)
warn(Msg);
// else
// error(Msg);
In theory adding ldflags += [ "/FORCE:MULTIPLE" ] to the Chromium build config (ideally) should work around the issues without the code edits, but it is not working for me right now. Anyway.
----------------
Moving on to another current issue, you probably are going to run into a grit configuration error if doing a non-component, non-debug release build at symbol_level = 0. Workaround as follows.
D:\depot_tools\chromium\src\tools\grit\grit_rule.gni
Find around line #102:
symbol_level > 0 && !strip_debug_info && !is_component_build,
Modify to remove the symbol_level check:
!strip_debug_info && !is_component_build.
----------------
Getting back to PGO, also remember to change all optimized code paths to "/O2" or even "-Xclang", "-O3" for the instrumented build to help collect viable profiling data. You can modify the optimize_for_size code paths back to the default "/Os" to help limit code bloat for the final build if desired, though YMMV on performance. Further testing probably is needed.
----------------
I also need to do further comparison testing for PGO builds with FullLTO+Polly versus ThinLTO. While I prefer FullLTO+Polly, if there is not much real-world difference, ThinLTO with its heavily multithreaded LTO is much faster to build on my 32-core system.
----------------
@Jerry Thanks as always!
@Aargl: Chromium 72.0.3626.81 was built with Xcode 10.1 and SDK 10.14; I'm surprised that it's still working on 10.11.
I thought the standard procedure was to unpack and manually install/update extensions.
You may remember that I had the case when I was still running 10.9: the first of your 68 dev build was working, then the next wouldn't. ;-)
So I guess I must expect that your next MacOS builds won't run on 10.11... :-(
@RobRich: COMDAT fix works with clang 9.0.0 - built clang with VS 2019 then subsequently built Chromium. At the moment, VS 2019 is the only way that I can build a fully functioning version of clang 9/llvm that is capable of building Chromium with LTO.
Just completed a internal ThinLTO PGO build. Looks decent, but the lack of SIMD autovectorization could be affecting at least one graphics benchmark.
Speaking of SIMD, I am also weighing my inclusion of AVX support across all optimized code paths.The benefit can be a huge YMMV depending upon code and hardware.
For example, beyond just the reported potential for AVX throttling on certain Intel chips....
https://www.agner.org/optimize/blog/read.php?i=415
Sandy Bridge, Ivy Bridge, Haswell, and Broadwell = 70 clock cycles for AVX state switching for mixed VEX and non-VEX code
Skylake (and perhaps later) = 14µs warmup for 256-bit AVX code if upper 128-bit half is powered down
And as for AMD....
https://en.wikichip.org/wiki/amd/microarchitectures/zen
Zen = 256-bit AVX split into two 128-bit micro-ops, plus stores done as 128-bit chunks
Hmmm.
I *suspect* SSE and 128-bit AVX are not factored into specific code-based (more like execution unit, but anyway) scalings, thus why the thermal issue seems more applicable to AVX2/512 code. That said, first-gen AVX can include 256-bit instructions as well, the overall situation is a mixture of the various codes and execution units.
Look at Skylake, which as noted apparently throttles the upper 128-bit of the AVX pipeline, which is fine for VEX-encoded SSE and 128-bit AVX. Execute a 256-bit SIMD instruction, and it will need to wake up the the upper 128 bits regardless if the instruction encoding is AVX or AVX2.
I was wondering if I could build it myself but only have 4GB RAM, I don't suppose I could cheat and attempt a build with a very large pagefile? :)
Thanks again.
Chromium 72.0.3626.96 (Official Build) (32-bit)
Revision 84098ee7ef8622a9defc2ef043cd8930b617b10e-refs/branch-heads/3626@{#836}
OS Windows
No Sync - WebRTC - Widevine - ThinLTO
clang/llvm 9.0.0-r353374
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
Ungoogled-Chromium-72.0.3626.96-Win32.7z (7-Zip archive)
Is this a new feature for security ?
Would it be possible for you to add Installer compilations to your build process?
I don't understand the process and therefore have no idea if that would be too much additional work or not. If it is too much, please disregard. I figured I would ask though because I prefer to do System Level ( --system-level) installations of Chromium in general.
Thank you for your time.
Thanks for the 32-bit build of ungoogled-chromium, it is much appreciated!
You probably won't believe it but your nosync builds are syncing! :-o
I've noticed that, back in November, when I switched from MacOS 10.9 to 10.11 and chose easiness over security and used your sync build for not having to reinstall all my apps/extensions/params/theme.
I was surprised when I came back to the nosync build that it was recognizing the connection to my account and seemed to sync. I've waited the next builds before warning you and this situation is still the same with your last 72.0.3626.96.nosync.
Is it the way I set up my #google-api-keys, as described there? I don't know, but I've just tried on a Mac where Chromium has never been installed before and it synced everything as if it was the sync version — It's quite overwhelming to see that Google doesn't give you a chance to deselect things at first launch, I see that my bookmarks and passwords have been uploaded to my account, back in November... :-( (but not after I unchecked everything in the prefs, of course)
I've then tested your ungoogled build and I wasn't able to connect to my account, as expected. ;-) That's the build I'll use from now on. Thanks!
@Aargl: Since I've been doing the ungoogled builds, I've notice that the traditional method of obtaining a no-sync build is incorrect. The ungoogled build passes a null key to the respective api keys, and as such there is an api keys missing message that has to be suppressed with a patch. I thought that on my latest mac stable no-sync build that the ungoogled method had been used. In the future, no-sync builds will be done the ungoogled way.
I don't have a Google account, nonetheless, I appreciate the feedback.
Nonetheless thank you for your ungoogled-chromium Windows builds!
So if someone wants to directly install extensions, starting ungoogled-chromium with '[...]\chrome.exe --extension-mime-request-handling=always-prompt-for-install' would be the way to go. (This works for all the other flags as well.)
Any location is fine, I use a folder under Program Files and it only needs read permissions (user profiles are stored in the usual %appdata% location).
Chromium 72.0.3626.109 (Official Build) (32-bit)
Revision fae8db7ab9280fa6704a59980263c804f809ebd5-refs/branch-heads/3626@{#857}
OS Windows
No Sync - WebRTC - Widevine - All Codecs - ThinLTO
clang/llvm 9.0.0-r353374
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
Ungoogled-Chromium-72.0.3626.109-Win32.7z (7-Zip archive)
Are you on a mobile form ? Weird resolution ?
@Anon4328: Your #comment-4332 is very interesting.
@Anon4344: Ok. Thanks for your feedback! ;)
@marmaduke: Now, you can update your "32-bit ungoogled release" info on the site yourself. Thanks a lot! ;)
1) Have you/can you try the patch to build the latest without safe browsing?
https://github.com/Eloston/ungoogled-chromium/blob/master/patches/inox-patchset/0001-fix-building-without-safebrowsing.patch
2)Is there any way of disabling the 'default to https' patch short of recompiling?
https://github.com/Eloston/ungoogled-chromium/blob/master/patches/ungoogled-chromium/default-to-https-scheme.patch
Some sites I use giving browser ssl warnings, it seems it is the sites fault for not setting up ssl certs correctly (I recall some regarding 'invalid site name for cert' or similar? No worries if not possible to disable the default behavior with a flag or parameter :)
Thank you again
I use the extension "HTTPS Everywhere", but i will still apply the 'default to https' patch.
Chromium still a no go without safe browsing.
Personally, I'm not too concerned about the inclusion of safe browsing and think that it's sufficient just to disable it. Brave browser redirects safe browsing requests to its own server.
ninja: error: loading 'build.ninja': The system cannot find the file specified.
Any assistance is appreciated.
64-bit • 74.0.3684.0 (626039) • Friday, 25 Jan 2019 • Marmaduke
Any updates, guys?
==============>
Chromium v72.0.3626.119-r612437-And64
Chromium for 64-bit Android - Friday, 22 February 2019
Chromium 72.0.3626.119 (Official Build) (64-bit)
Revision 9a65993e2cde1b5797ec98da4cd9abcea464cd7b-refs/branch-heads/3626@{#876}
OS Android 9: ONEPLUS A6000 Build/PPW29.116-16
OS Android 64-bit
only for Android 64
official build
All Bromite patches applied (ungoogled, additional CODECS)
HEVC
No Sync • No Widevine • ThinLTO • Bromite • HEVC
Chromium_Android_64.zip
====
Chromium branded, what the hell is a git binary patch?
You took up the case of UnGoogled Chromium and now an Android version!
It suits me particularly because I actually have Bromite but it seems to drain very quickly a lot of battery on my phone so your Android version will give me a chance to investigate whether it is a Chromium’ source or patch problems !
Hereby I express a very big thank you to you for your curiosity and your great variety of builds for everyone on any kind of OS!
----------------
The power supply fix worked; for the few minutes the system was booted anyway.
Had swapped in a known working 8-core Opteron back when troubleshooting the system. Just damaged multiple socket pins when getting ready to swap back in one of my two 16-core Opterons. :/
I have tried fixing socket G34 pins on a couple of occasions. Forget it with my hands. Found and ordered a new replacement motherboard, though it could be the beginning of March before it arrives.
----------------
Anyway, on to builds. Windows 32-bit ThinLTO is located in the build listings above.
Below is a interim Windows 64-bit ThinLTO build. I built it on my Kaby Lake notebook for my Kaby Lake notebook. I modified the default x86-64 target in LLVM to set Skylake scheduling and to enable AVX2 SIMD support. Benefits? Not much, if any IMO. Perhaps some performance regressions, too.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v74.0.3716.0-r634982-win64
A complex FullLTO+PGO+Polly build might be pushing it right now, but in the meantime, I will try to have an updated Windows 64-bit ThinLTO build with AVX enabled later this weekend.
chrome.exe - Application Error
The application was unable to start correctly (0xc0000142). Click OK to close the application.
CPU-Z is a freeware utility to check such CPU features:
https://www.cpuid.com/softwares/cpu-z.html
https://github.com/RobRich999/Chromium_Clang/releases/tag/v74.0.3717.0-r634998-win64
I have a FullLTO+Polly build cooking. Probably Monday for release assuming it builds.
v74.0.3717.0-r634998-win64
Same app error. And there is 74.0.3716.0.manifest in archive.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v74.0.3717.0-r634998-win64
----------------
Looks like something is breaking linking for my FullLTO build. Hmmm. Will try to take look tomorrow.
Finally, av1 videos on youtube play without problems.
I tried the Chrome 72.0.3626.119 and they don't seems to apered.
Acutally I don't know what cause this problem, because I was able to reproduce it with clean ungoogled profile and no extensions. For me seems to be some scroolling problem with the chrome 72.0.3626.109 because when i disabled the flag "Threaded Scrolling" there are no scrolling problems.
I just pulled a fresh LLVM revision and cooking a fresh build with asserts enabled to perhaps narrow down it down.
Otherwise, I might have to go back to ThinLTO builds in the meantime.
------------------
Something I tossed together while experimenting with a modified LLVM build, new pass management, synthetic counts, etc. YMMV, especially on performance.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v74.0.3721.0-r636362-win64
On the other front, it appears I probaby have Polly and PGO working. A build is cooking. Next step will be seeing if FullLTO is going to work.
----------------
Building LLVM with Visual Studio 2019 RC.
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang;lld;polly;compiler-rt -DCOMPILER_RT_BUILD_BUILTINS=OFF -DCOMPILER_RT_BUILD_SANITIZERS=OFF -DCOMPILER_RT_BUILD_XRAY=OFF -DCOMPILER_RT_BUILD_LIBFUZZER=OFF -DCOMPILER_RT_BUILD_PROFILE=ON -DCOMPILER_RT_BUILD_XRAY_NO_PREINIT=OFF -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_C_FLAGS="/MD /O2 /Ob3 /DNDEBUG /GS- /Gw /arch:AVX2 /favor:INTEL64 /MP1 /cgthreads4 /Qvec-report:1" -DCMAKE_CXX_FLAGS="/MD /Ob3 /DNDEBUG /GS- /Gw /Ob3 /arch:AVX2 /favor:INTEL64 /MP1 /cgthreads4 /Qvec-report:1" -DCMAKE_C_FLAGS_RELEASE="/MD /O2 /Ob3 /DNDEBUG /GS- /Gw /arch:AVX2 /favor:INTEL64 /MP1 /cgthreads4 /Qvec-report:1" -DCMAKE_CXX_FLAGS_RELEASE="/MD /O2 /Ob3 /DNDEBUG /GS- /Gw /arch:AVX2 /favor:INTEL64 /MP1 /cgthreads4 /Qvec-report:1" -G "Ninja" ..\llvm\llvm
Adjust /arch:AVX2 /favor:INTEL64 /cgthreads4 according to the local system. Of particular note is /Ob3, which enables more aggressive code inlining in 2019 RC. :)
----------------
I have modified LLVM to disable duplicate symbol reporting, disable certain inalloc reporting, enable aggressive instruction combining at lower opt levels, and enable a tail cail elimination pass during LTO.
As to building Chromium, I am further experimenting with the newer "simple" loop unswitcher with non-trivial unswitching, conditional branch folding, partial inlining, register scheduling, register assignment, register bank selection, instruction scheduling, vector legalization, additional polly options, etc.
I am currently building an updated LLVM release to attempt multiple-stage, context-sensitive PGO as well.
-O3 was breaking it, but whatever, I can build at -O2 with little to no appreciable real-world difference.
Now it is griping about a Machine CSE issue. :/
If required, I simply will move Win64 builds back to ThinLTO in the meantime until the FullLTO issue is resolved.
----------------
As to my build box saga, the replacement motherboard should be here like Monday or Tuesday.
I can't connect to existing database (successfully use with stable-codecs-nosync before): nothing happens when click on "Connect"...
Thanks.
No-sync, all codecs with no Widevine
https://github.com/cyberrufus/Chromium/releases/
use_thin_lto = true
thin_lto_enable_optimizations = true
nik and marmaduke tend to release new Windows dev builds when there is a version change, ostensibly, to mitigate any changes in ffmpeg or in the source code in general.
I thought you were running Chromium on a vax-11
Test system (A demanding Hackintosh that theoretically is not capable of running Mojave!)
System Version: macOS 10.14.3 (18D109)
Model Name: iMac
Model Identifier: iMac13,1
Processor Name: Intel Core 2 Duo
Processor Speed: 3.16 GHz
Chipset Model: Asus GeForce 210 1Gb
Command Line /Users/xeon/Desktop/Chromium - Stable/Chromium.app/Contents/MacOS/Chromium --user-data-dir=/Users/xeon/Desktop/Chromium - Stable/Data --incognito --disable-sync --disable-sync-backup --disable-sync-rollback --disable-sync-app-list --disable-sync-types --enable-sandbox --isolate-extensions --isolate-sites-for-testing=* --process-per-tab --process-per-site --safe-plugins --disable-webgl --disable-reading-from-canvas --disable-presentation-api --disable-ipv6 --disable-webgl-image-chromium --disable-speech-api --disable-java --disable-breakpad --ppapi-flash-path=/Users/xeon/Chromium-plugins/Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=32.0.0.101 --allow-outdated-plugins --ssl-version-min=tls1 --flag-switches-begin --flag-switches-end —-cipher-suite-blacklist=0xc007,0xc011,0x0066,0xc00c,0xc002,0x0005,0x0004,0x000a
Executable Path /Users/xeon/Desktop/Chromium - Stable/Chromium.app/Contents/MacOS/Chromium
Profile Path /Users/xeon/Desktop/Chromium - Stable/Data/Default
Tested: ungoogled, stable sync and no-sync
Chromium 72.0.3626.121 (Official Build) (64-bit)
Revision da3787ba355f18db7db52abf75c42afb408d656f-refs/branch-heads/3626@{#883}
OS Mac OS X
Chromium runs correctly.
if anyone else is having problems, I would like to know. Appreciate the feedback.
@glynis37: Welcome on this site! I put the content of your #comment-4387 on a pastebin (or text storage site) because it is very long and this site is not for debug. Hope you understand! ;)
@Marmaduke: Now, you can update your Android "ungoogled-chromium" info yourself. Make sure "ungoogled" is present in the download URL like your other releases. You forgot it. Anyway, thank you very much for your all releases and help! ;)
@cyberrufus: You're welcome to share your release here. Contact me if you want to add it on this page! ;)
@D: Since the version 71, Chromium (and all Chromium-based browsers) use Material Design. You cannot disable it. chrome://flags/#top-chrome-md and the old source code were removed.
@RobRich: I cross the fingers for your computer! :)
Reference: Chrome Dev Channel release 3-5-19
No-sync, all codecs with no Widevine
https://github.com/cyberrufus/Chromium/releases/
Is it possible to know a little more about your builds?
How did you discover Woolyss?
On which type of machine does you build?
What type of argument do you use?
And finally: why building and sharing your own Chromium?
Thank you for you share !
https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop.html
@marmaduke: Thank you for looking at it, hopefully, I'll figure it out.
@Anon4394: Yes. Chromium and all Chromium-based browsers have this fixed bug since version 72.0.3626.121
@glynis37: It is ok. Do not worry! ;)
I grabbed @Marmaduke's up-to-date build as a drop-in replacement for Chrome with no-sync but the ungoogled bits are breaking a lot of things for me (chrome webstore is the biggest problem since my users want to be able to install/manage their extensions). I was able to re-add google search for url bar search.
since days it is well-known that all Chromium / Chrome versions before 72.0.3626.121 are endangered by a dangerous safety gap.
Since it should not be harmless to use some of the Chromium versions available here at the level of January or February?
https://github.com/RobRich999/Chromium_Clang/releases
I've been around here long before developers began linking their builds (2016?). I'm just using basic arguments for no-sync with codecs and any meaningful changes will be noted. Computer is also pretty basic (4-core with 16 RAM). Went away from Chromium for a bit to Canary due to inconsistency of releases and figured out the best solution to it would be to build myself.
74.0.3728.0 x64 for Windows
No-sync, all codecs with no Widevine
Reference: Chrome Canary release 3-7-19
https://github.com/cyberrufus/Chromium/releases/
what's your build setup and what guide did you use to get started? i've been thinking about doing my own builds, mostly because of the delays that have been happening between builds on here lately. i don't think i'd need to go over the top with the optimization and testing like some builds on here, but staying as up to date as possible is a priority for me in general.
that said i more than appreciate the resources and time put in by everyone who does submit their builds, whenever they do.
https://github.com/henrypp/chromium/blob/master/building_chromium_gn.md
https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
I used Nik's very good guide to building as well as the Chromium instructions as a starting point. Only issue I have is the long build time but that's just my computer.
@cyberrufus: Thank you for feedback. You came on this site in June 2014 (https://chromium.woolyss.com/?all=1#comment-171)! ^^
Thanfully I do have the replacement and upgrade parts for the build box now. I just need to get them installed. I am hoping tomorrow if I feel up to it.
I probably will be transistioning build types again due to build times and related. Likely ThinLTO again, though perhaps with partial PGO.
@RobRich: It is ok. We understand. Do not worry! ;)
@marmaduke: Thank you for your latest releases! ;)
@TAK: About the serious error (CVE-2019-5786 - https://bugzilla.suse.com/show_bug.cgi?id=1127602), only the builds released after February 28 have this fixed bug. The stable versions are clean since 72.0.3626.121
I should have a Win32 build tonight or tomorrow.
----------------
@Jerry Drop the FullLTO, Polly, and PGO tags on my Win64 build for now due to various issues. Add back the ThinLTO tag. Thanks!
I know where some regressions likely are occurring. Hopefully the numbers will look a little better with the next Win64 build.
No-sync, all codecs with Widevine
--------
@Jerry: after digging around a bit, it looks like the commit was first included in 74 with 74.0.3721.0 on Mar 1.
@earthsound: It is fixed for 12 days now. Check the source code of the STABLE version (72.0.3626.121).
Screenshot:
Source code: https://chromium.googlesource.com/chromium/src/+log/72.0.3626.121?n=50
Debian security tracker: https://marc.info/?l=bugtraq&m=155229051918261
Chromium for 64-bit Android - Wednesday, 13 March 2019
Chromium 73.0.3683.75 (Official Build) (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Android 9: ONEPLUS A6000 Build/PPw29.116-16
OS Android 64-bit
- only for Android 64
- official build
- All Bromite patches applied
- HEVC
No Sync • No Widevine • ThinLTO • Bromite • HEVC
arm64_ChromePublic_HEVC.apk
One bug I had with previous build 74 were sporadically crashes-to-desktop. But it didnt happen too many times, so it didnt bother me too much.
@ball: Chromium is generally not signed...because it is not free for developers (#malware)
@olle: Thank you for your feedback. About changelog for new build 75, check the commits:
https://chromium.googlesource.com/chromium/src/+log/75.0.3731.0?n=1000 (Long page!)
However, you had said:
"About the serious error (CVE-2019-5786 - https://bugzilla.suse.com/show_bug.cgi?id=1127602), Chromium and all Chromium-based browsers have this fixed bug since version 72.0.3626.121. Each release on this site is clean because its version is greater than or equal to 72.0.3626.121"
But that's incorrect. Builds older than 2/28 do not have the fix (even if they are a higher version number than 72.0.3626.121) and are not "clean". Marmaduke just updated his Android build, but there are 5 that remain vulnerable to that security bug.
2¢
Thanks for insisting!
I remember these builds used to be updating more frequently... has this changed?
Last release was 74.0.3689.0 (627581) • Wednesday, 30 Jan 2019.
Thanks @Jerry for rectification. However, this shows how dangerous it can be to use developer versions of Chromium from here, that have not been updated for a long time.
For me, Chromium 75 from Rob works very smooth and stable. Do you have an idea, why Chromium refuses to safe login informations for certain sites (a.e. forumbase.de)? I didnt experience this issue on previous Chromium builds. What I see is, that password is stored in Chromium (when I go look in settings). But when I try to login to site, it doesnt fill out the fields and I have to type it instead. But I only experienced this issue on one site so far respectively I didnt try out all my prefered sites with login yet.
But thats only a little issue. Respect to the work of people like Rob, Nick, Marmaduke, etc who does all this efforts so we have nice browsers :)
@Dustyn: nik is probably busy.
@olle: You use a development version. It can be a revision issue or site bug. This bug is currently on only one site. I do not know.
@TAK: Yes. Exactly. Like earthsound said in his #comment-4419, there are 5 vulnerable builds here. I highlighted them with an automated red tag.
Also, it is fantastic that there are multiple build developers here now sharing with this community and providing different types of builds for different purposes. (Testing, stability, efficiency, security, etc.)
Excellent work, everyone! Cheers!
@Kevin: > add codecs to robs builds?
You needn't. The RobRich's builds have all standard codecs + H.264/AVC (MP4) + AAC. It is enough to navigate on the Web. They haven't the H.265/HEVC, MPEG-4 and AMR codecs but... H.265/HEVC will soon be replaced by AV1 (already supported by Chromium) ; MPEG-4 (Xvid in AVI) is rarely used ; AMR is for smartphone. To add non-standard codecs, you must compile Chromium. Test codecs at https://tools.woolyss.com/html5-audio-video-tester/
@RobRich: Thank you. Note I add a new "codecs+" tag for your builds! ^^
No-sync, all codecs and Widevine
https://github.com/cyberrufus/Chromium/releases/
https://chromium.googlesource.com/chromium/src/+/5845e3041f028f5ca90e79d5e730a11fefbcd18c
"We previously relied on the *DecoderConfig to be "invalid" for
unsupported codecs. But this is fragile and hard to document and we
already have utilities to answer what codecs are supported."
I suppose it's only a matter of time before Sita ceases to sing the blues, and Google embraces neo-Luddism.
https://bugs.chromium.org/p/chromium/issues/detail?id=942869
@marmaduke: Ok. Thanks for info ;)
@Evan: Keep cool! ;) I explain in my previous #comment-4432 that on the Web we need all standard codecs + H.264/AVC (MP4) + AAC. The others ones are secondary and mainly used for #chromium-os
@Anon4436: Yes. I see. This effect changed beetween v72 and v73. Google Chrome (73.0.3683.75) is similar. I also search info about that.
@olle: Thanks for the report!
Info on the bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=911823
It seems if you have visual effects for your OS disabled it respects that settings in the browser, but I have never seen this happen in the past and have always had the animation setting in OS it refers to disabled, strange!
Anyway I only see this as a problem because if you open a tab too fast and animations are disabled, if you start typing in the address bar it can take 1 second for the page to become 'active', so any typing you did is erased.
@Anon4445: Ok. Thank you very much for the report and your explanation.
> I have never seen this happen in the past
Agree. Never seen before.
ungoogled-chromium is my preferred browser. But, my release schedule is determined by Eloston's, which is presently v 72.0.3626.122
It doesn't really matter which version of Chromium you use as long as it is at least v 72.0.3626.121. To a certain extent, an ungoogled build can be approximated by using PAC files and Gorhill's products - uMatrix, etc.
In short, if the current build of ungoogled-chromium is consistent with that of Chromium I will tend to build it. I've tried to apply the existing ungoogled-patches to the current release of Chromiun, but am not particularly interested in attempting to rectify any patch failures.
Thanks very much for the reply, I will be sticking with your builds of ungoogled-chromium then which I appreciate you creating for the community.
The ungoogled-chromium builds feel at least 50% snappier than other chromium builds for windows, maybe it is because my machine is over 10 years old or the removal of components and their maintaining (chrome://components) but I really feel that difference in speed.
Cheers.
@marmaduke: Ok. Thanks for info.
I tried twice "installing" your latest 64bit portable 75.0.3735.0 release, but I'm not able to launch it because Win10 says the chrome.exe application can not be started (application error 0xc0000142). Maybe something is wrong or missing in my system?
In my case, I can confirm latest portable chromium 75.x release from RobRich works fine for me on Win10 64bit.
Thanks for your useful hint.
My PC actually dates back to 2010 (i7 860), so probably the cause is just that.
Therefore my system DOES actually... lack something: a newer version of itself! :]
@olle
Your PC proves to be younger than mine, then. Thanks for your kind answer, anyway. :]
No-sync, all codecs and Widevine.
https://github.com/cyberrufus/Chromium/releases/
Is it possible to add Ungoogled by Marmaduke to repository like F-Droid or Aptoide for simplify the update of Chromium browser?
Thanks
Maybe it's just a whim of mine, but I prefer using, when available, 64bit software.
@RobRich
Thanks for your explanation.
Do you think in my case your Win32 version could be, performance wise, an overall better choice?
----------------
Looks like Windows builds finally are moving to the LLVM libc++ library, so expect performance changes. I actually noted some regressions in an internal builds here. so YMMV. Probably means me looking into even more aggressive optimization strategies. o.0
----------------
I have FullLTO+Polly back building. I have a successfully completed build, but broken HTML rendering. I was testing floating-point fast math optimizations, so it is not too surprising. ;)
well, I actually AM using this browser; I've been using it for a few years now, in various portable versions (I like portable programs).
I have already used also "modified" builds (from this site); this time I encountered a problem I had never met before and so I posted my question, quickly getting useful and exhaustive answers. :]
Actually is more like FullLTO+Polly along with various optimizations for register allocation, register scheduling, gvn hoisting, code inlining, vectorization, etc. I might even have a little more headroom on Polly optimization opportunities, as I am running default delicm-max-ops and dependences-computeout thresholds right now.
Even with the libc++ migration, I have performance back to my general expectations.... and then some for a few benchmarks.
Basemark Web 3.0 posted one of the highest scores I have seen on my test system, IIRC.
MotionMark still is down from its peak scores for whatever reason, though I am suspecting more along the lines of project code changes instead of my build optimizations. Anyway.
Immediate downside? The build took about *9.5 hours* to compile. Admittedly, the build was not done on my 32-core build box, either, but FullLTO basically does single-threaded linking so I still expect several hours even building on it.
Given the build times involved, I have getting PGO back into the mix on the backburner for now. Maybe later.
----------------
@Anon4463 If ever implemented for a public build, it likely would be for certain components where strict FP compliance is not a requirement. Like media codecs for example.
Naturally I compile much of the Win32 build codebase at -Os to keep memory use down, but I did increase the inlining thresholds for select code paths I build at -O3, so feel free to let me know if memory usage becomes an issue.
Did you by any chance find out how to re-enable animations in version 73, described in #comment-4445?
Thanks
I suppose injecting the following CSS into pages might workaround the animations issue.
@media (prefers-reduced-motion: no-preference) {}
——
@Anon4471 Welcome. :)
-----------
Admin: My intent with the above post was to display my dismay and concern with an old vulnerable version being "hosted/linked" to on the Chromium Woolyss page. It is not to bash, discredit or show any ill will towards anyone here on this great site. I've used Nik's Dev versions for a long time now and have greatly appreciated the rewards of using a highly stable rich featured dev version of Chrome. But sadly, in my opinion, I feel they are not updated enough now and should not remain up on the site for months without updating. It defeats the purpose of a dev build. I've moved forward with Google Canary for now as it is a fantastic substitute, even if it does have the Google evils attached to it. Thank you, good day. :)
No need to hope, I did not take your reply in the wrong way. Not at all. :]
No-sync, all codecs and Widevine.
https://github.com/cyberrufus/Chromium/releases/
@cyberrufus: Thank you. If you want to share your versions on this site, contact me! ;)
Read the comment above yours, they were removed as they contained public vulnerabilities.
AppVeyor is free for open-source projects, as I understand it. If Nik was to setup his Stable channel build projects via AppVeyor, in such a way that whenever a Stable patched build was released upstream, it could trigger a source update and compile Stable channel build automatically and update binaries/archives to Github. This would make things easier in the long term for Nik and also provide security updates to users promptly.
Has anybody else had any thoughts or ideas about a more automated approach to building Stable branch builds?
One might keep pace with "stable" version builds using Azure or EC2 for like $10-$20 per month, which admittedly is a *huge guesstimate*, plus my assuming default code path optimizations and probably not relying upon LTO.
@nik May the Azure Pipelines be an option, it offers unlimited CI/CD minutes for open source
No-sync, all codecs and Widevine.
https://github.com/cyberrufus/Chromium/releases/
With dark theme ( --force-dark-mode) menus are now black on black... So it's quite hard to read
Same for me for a while now. The only way is to install from google store, then copy the extension from the profile folder.
Then it can be installed locally on anywhere. I think its the new manifest file that is messing everything up.
Really annoying imo
Ok I found where my problem comes from : new version of chrome require CRX3 extension file while dowloading crx websites gives you CRX2.
Someone knows how to catch CRX3 files frome chrome store?
Thanks
On that note, I have updated Opteron processors on the way. Later generation and faster clocks, so hopefully a little faster build times.
Appears the recently failed power supply damaged the thermal probes (and perhaps more) on the existing procs. Even with the new motherboard they are no longer reporting core temperatures, which means no boost and full 8000RPM+ proc fan speeds. o.0
At least G34 system pull procs are rather affordable these days.
----------------
On to Chromium itself, a quick FYI for those building with....
use_thin_lto = true
thin_lto_enable_optimizations = true
....on Windows. The instruction import limit has been dropped to *one-tenth* of the LLVM default to help limit ThinLTO code bloat and improve build times. The downside is there could be minor to moderate performance regressions, so YMMV. You can comment out "-mllvm:-import-instr-limit=10", in depot_tools\chromium\src\build\config\compiler\BUILD.gn to return the default ThinLTO limit if desired.
Also note libc++ has been disabled on Windows builds due to currently broken debugging in VS. If not concerned about a debug build, libc++ can be enabled by reverting the code edits in the following commit:
https://chromium.googlesource.com/chromium/src.git/+/27026b5f155273f8e0721cd56a7f384a32b24e84^!/#F0
Disregard the container_type_operations.h edit, as the file was removed earlier today.
Is this behavior normal, or were you just pushing it beyond its limits the whole time?
Actually, it probably was more a combination of a likely failing power supply and an upgrade to a higher wattage video card. An eventual serious hardware failure after a few years of a system building large software projects is not too unexpected.
New 1000w power supply, new dual-proc G34 motherboard, new cooling fans for proc heatsinks, and now waiting on two "new to me" Opteron 6378 procs to arrive. The procs are supposed to arrive Thursday, though it would not surprise me to be more like Friday or Monday.
This should enable you to download any extension using its [EXTENSION_ID]:
https://clients2.google.com/service/update2/crx?response=redirect&prodversion=73&acceptformat=crx2,crx3&x=id=[EXTENSION_ID]%26installsource%3Dondemand%26uc
The relevant part here is "acceptformat=crx2,CRX3".
In the multithread benchmark, your score is 4009 and it says a Ryzen 7 1700 score is 3903.
So does that mean a first gen Ryzen 7 1700 would build Chromium using pretty much the same amount of time as you would?
Or does it not work that way?
The reality can be more complex when it gets into number of compiler processes, number of files, etc. Plus there is the situations with ipc, numa, thread management, etc.
NInja defaults the job count to Cores+2 when building Chromium. The clang-cl.exe compiler binary is single threaded. ThinLTO linking can be set to use however many cores. Conversely, FullLTO linking is largely single threaded.
I rebuilt my Opteron system due to the availability of affordable procs and already having 64GB of registered ECC memory. ;) I bought those two Opteron 6378 procs for under $50 shipped for both.
On the annoying side, I have given up on fan management for now. It is disabled, and I even bypassed my case fan controller. The system is loud, but at least I am rarely in the same room using the system since I mostly rdp into the box anyway.
Grab a few of those crazy 10,000 rpm fans and you should be right.
Thanks.
https://www.bleepingcomputer.com/news/software/major-browsers-to-prevent-disabling-of-click-tracking-privacy-risk/
I don't see how any of this is good.
Use uMatrix
#reduced-referrer-granularity states that pages can bypass it by setting an explicit referrer policy. Are many websites doing so, is this flag useful?
https://github.com/Manvel/Privacy-Manager has 24K users at CWS, but only 10 stars at GitHub. Is it any good?
What is the most secure way to use KeePass with Chromium? All extensions are old and abandoned except https://github.com/keepassxreboot/keepassxc-browser with 3.5/5 rating.
https://www.microsoftedgeinsider.com/en-us/download
Microsoft Edge Dev is version 74.1.96.24
Microsoft Edge Canary is version 75.0.121.1
https://www.neowin.net/news/these-are-the-google-features-that-microsoft-turned-off-in-chromium-edge
https://thirdpartysource.microsoft.com/download/Microsoft+Edge/75.0.121.1/Windows+x64/chromium.zip
edge_build_instructions.md
It would be nice to have "playready" in Chromium...and to omit safe_browser...and to see if Edge can be amended or even built!
Homebrew for the FreeSMUG Chromium builds
To install do:
brew cask install freesmug-chromium
I've read thousands of words of drivel espousing Microsoft's nascent browser. Basically, apart from Microsoft's special crud, the only noteworthy attributes are PlayReady and 4k Netflix.
I've "built" MS Edge from source! Don't waste your time. The build process is a joke: there is no (meta-build) ability to configure the build - just a collection of object files to assemble and link!
The build could be configured by amending the Ninja build files, but that defeats the purpose of using Ninja.
https://chrome.google.com/webstore/detail/keepass-tusk-password-acc/fmhmiaejopepamlcjkncpgpdjichnecm
It's github repository is here:
https://github.com/suBDavis/Tusk
It should work well for most set ups.
https://chrome.google.com/webstore/detail/keepasshelper-password-ma/jgnfghanfbjmimbdmnjfofnbcgpkbegj
I still use chromeIPass, but thinking about tying someting else
Long story short? It looks like Win64 is going back to ThinLTO for the foreseeable future. I will try to get a build pushed tonight or tomorrow.
As before, I will move the FullLTO+Polly builds back to experimental status for if/when I feel like dealing with them.
----------------
BTW, speaking of browsers integrating portions of Chromium, I am posting this comment via Falkon.
https://en.wikipedia.org/wiki/Falkon
https://wiki.qt.io/QtWebEngine
The biggest personal concern is ThinLTO currently does not support autovectorization, and it is one area I have been trying to target for recent performance optimizations.
On the plus side, ThinLTO is faster to build. I can set ThinLTO linking to use up to *32 threads* on my build box, versus FullTO linking is largely single threaded. Now factor those numbers against a project the size of Chromium.
https://clang.llvm.org/docs/ThinLTO.html
For me? I tend to like often having the fastest modern Win64 browser in several benchmarks. ;) Basically a numbers thing, I suppose.
----------------
@Anon4532 Same here. :) I am still running my Win64 r643164 public build as well.
----------------
Win64 ThinLTO build now available. There are some performance regressions, but I have some possible ideas.
I will keep the Win64 FullLTO+Polly builds in the comments until if/when their build process ever stabilizes.
@Jerry Back to the ThinLTO tag for my Win64 build. ;)
...and thanks also to all developers and users.
- site https://www.microsoftedgeinsider.com/en-us/?form=MO12FO&OCID=MO12FO
- download(s) https://www.microsoftedgeinsider.com/en-us/download
- coming soon for Windows 7, Windows 8.1 and macOS (page recognize Your actual Windows used)
void PassManagerBuilder::addLTOOptimizationPasses(legacy::PassManagerBase &PM)
....
PM.add(createLoopVectorizePass(true, !LoopVectorize));
AFAIK, the issue with Rpass is it being a fronted directive, and the actual autovec pass is being done during the backed portion of LTO codegen. So for Windows, lld-link.exe when using LTO will accept:
"-mllvm:-pass-remarks=loop-vectorize"
It does not identify the specific code being vectorized, but at least it does confirm vectorization is occurring.
Going a step further, I now also have confirmed Polly can be run in the early position with ThinLTO enabled.
Ideally I prefer Polly in the late position before the loop vectorizer. I *might* be able to add a hook into the LTO pass manager. Something to poke at later.
Now to see if Chromium builds. ;)
----------------
Cleaned the build directory, and vectorization remarks now are tagging most of the applicable code. Still a few "unknowns" due to line zero stuff, which I have seen before in LLVM. Anyway.
Example: https://pastebin.com/fA49ugzT
FYI. I am running a subset of my LLVM and Polly optimizations for now to establish a working build.
---------
If anyone else is noticing possible graphics performance regressions in recent dev builds, consider disabling BlinkGenPropertyTrees.
chrome://flags/#enable-blink-gen-property-trees
It is knocking about 10% off my Basemark Web 3.0 scores. YMMV on how it might affect other performance indicators.
BGPT is currently enabled in the field trial testing configuration (as of this post). Looks like devs are working on a fast-path for transform changes, which should help or perhaps even overcome the affected graphics regressions.
got a chrlauncher "Error while checking update..." error when prompted to update Marmaduke's "dev-codecs-nosync-experimental" ver: 75.0.3768.0
Is there an update soon for Ungoogled Android64 ?
If yes , is it possible to ad one very stronger blocker of pop_up in the adblocker ?
Thank You...
https://pastebin.com/3nN7QXg7
---------------
Win32 ThinLTO+Polly now available.
Currently includes....
Setup LLVM for loop distribution, loop interchange, simple loop unswitching, non-trivial loop unswitching, gvn hoisting, etc. Modified LTO optimization pass management to enable loop distribution during LTO codegen.
Polly is handling multi-level tiling, register tiling, schedule tree optimization, loop interchange, stripmining vectorization, invariant load hoisting, additional early inlining, increased precision for inbounds assumptions processing, folding memory accesses for potentially more delinearization opportunities, etc.
Other assorted tweaks include global sized deallocation functions, LLD tail merging, manual inclusion of the compiler-rt 386 builtins library (fixed an intrinsics issue with my build setp), LTO instruction import limit restored to 100, greedy register bank selection, local reassignment optimization for greedy register allocation, etc.
On the idea list....
I am currently not using partial inlining, through it is disabled by default anyway. As comments in the pass manager indicate, it probably as configured is not in an ideal placement for LTO. I am thinking about either moving it to or adding a second partial inlining pass to the LTO optimization passes.
There is a loop fusion pass now available in LLVM, but it is not in the pass managers, yet. I did not have much luck last time I tried poking at a possible pass management placement, at least when placing it during LTO codegen. I assume it might end up placed before loop distribution, as that would roughly follow the IBM XL compiler loop optimization pipeline.
The IBM XL compiler also has a couple of loop unroll and jam passes in the loop opitmization pipeline. It could be worth a quick investigation since LLVM has a loop unroll and jam pass available as well, though it is disabled by default.
----------------
@Jerry You now can add the Polly tag to my Win32 builds as well.
------------
I just tossed the Win64 build through Basemark Web 3.0. Performance with BlinkGenPropertyTrees *enabled* (the default) now is higher than with it forced to disabled. I will take a look at MotionMark and Speedometer in awhile.
Anyway, the numbers so far look decent, especially considering I have tweaked my usual optimization levels to drop a few MB out of the build to potentially improve processor register allocation, caching, data locality, and similar.
I know that @Nik used to provide that, but not anymore...
However, you still can add your own #google-api-keys to enable sync if desired.
Chromium 74.0.3729.108 (Official Build) (64-bit)
Revision daaff52abef89988bf2a26091062160b1482b108-refs/branch-heads/3729@{#901}
OS Android 9: ONEPLUS A6000 Build/PPw29.116-16
OS Android 64-bit
- only for Android 64
- official build
- All Bromite patches applied - Apart from "AV1-codec-support.patch": YouTube would not work. I'm sure that Android now natively supports AV1
- HEVC
Personally, I think that v73 is better and that my time would have been better spent compiling the latest revision of v73. AV1 does not work: I'll try to resolve the situation. I'm sticking with v73!
No Sync • No Widevine • ThinLTO • Bromite • HEVC
arm64_ChromePublic_HEVC.apk
I'm seeing the Google logo and the + Add shortcut button below, but no Google Search bar in the middle of those two.
I checked Google Chrome's own 74.0.3729.108 Stable channel build for comparison and it still showed the Google Search bar within the New Tab Page. I also checked and compared my chrome://flags settings to ensure there was nothing different between the two. So at the moment, I have no idea what is causing this and wanted to see if anyone else has noticed this issue.
It seem the bar exist but it’s hidden by css rule. See
Probably a chromium revision problem, bug or thoughtlessness…
Dark mode works on Windows 7:
Cheers.
This is likely a Field Trial / Variation which is often different between Chromium and Google Chrome. By default, they both have different variations going on.
Actually, I just confirmed in another tab right now where this is taking place. See below:
Source: https://chromium.googlesource.com/chromium/src/testing/+/master/variations/fieldtrial_testing_config.json#4141
This is what I suspected immediately after your shared code snippet (thank you). This means that this Chromium build is using a new field test to trial the Local NTP (new tab page). I had previously seen nearly a dozen different NTP-related flags in chrome://flags before but did not mess around with the Local NTP before. There is actually quite a bit of neat things (doogles, etc.) that we can do with the Local NTP now via flags. And also Local NTP likely loads faster in comparison to fetching the NTP from the web.
Anyway, this can be fixed by Disabling: chrome://flags/#remove-ntp-fakebox
@Yuliya and @Anon4558: Thanks for your feedback.
@WildByDesign: Very interesting info. Thank you! ;)
@Anon4560: Thanks to him! ;) marmaduke does not use Widevine but compiles Chromium with its relative settings. Please read comments at #comment-2164 (This link will show you all comments) for few info. I checked chrome://components in its ungoogled-chromium release and see "Widevine Content Decryption Module" has "Version: 0.0.0.0". It is probably a recent issue! :/
@Anon4561: there are different options to install an updated version of 32-bit Chomium on a GNU/Linux distribution:
- use Snappy and install Chromium (https://snapcraft.io/chromium). For Arch Linux: https://wiki.archlinux.org/index.php/Snap
- use a distribution like (or based on) Ubuntu, Debian, Fedora, Gentoo.
- use the official development versions : https://download-chromium.appspot.com/?platform=Linux&type=snapshots
@Jerry
I believe the reason widevine and other components are version 0.0.0.0 on the components page is because ungoogled-chromium prevents updating of them, as it would allow downloading of binaries that have not been 'ungoogled'. As the initial update process installs them they do not exist on ungoogled-chromium installs/profiles.
If anyone is curious you can get the same behavior on normal chrome/chromium builds using the ' --disable-component-update' switch. This also prevents flash being installs.
Thanks.
Also: Underneath Marmaduke's MacOS dev build, you list a bullet for "Use an #updater-on-mac" but that homebrew cask only downloads/updates the stable build. Is there an updater for Marmaduke's dev build on MacOS?
Accordingly I have been playing around moving Polly in pass management, though keeping it in the front end passes. The issue has been dealing with fixing one breakage and causing another. ;) I am not fond of the default early placement, as I end up running extra inlining to improve SCoP detection (and bloat code in the process), so I have been pushing it further down in the passes.
There is a session with a delay for my comment system. I choose this system because it is very robust to avoid spammers and bots (on a non-moderated comment system, before display on the site)
Also, thank you for info about --disable-component-update
@earthsound: > Did something change since January?
Yes. Nik stopped to share his DEV builds with sync because there were more and more patches to maintain. (https://chromium.woolyss.com/?all=1#comment-3574). He prefers to concentrate his efforts on the STABLE versions.
I understand you really miss the sync but you are the only one person who need it on DEV versions. No feedback except yours. Sorry.
Marmaduke, RobRich, Cyberrufus... can you make one DEV build with SYNC?
About "Use an #updater-on-mac", there is no updater for Marmaduke's dev builds on MacOS...but updaters are open-source. So anybody can create it and improve existing tools. Maybe this note should be removed.
I have not done a complete build, yet, but LLVM r359944 appears okay so far.
-------------
Another FYI. Win64 builds might need to set v8_win64_unwinding_info = false as a Chromium build argument, perhaps depending upon various build options.
====
Chromium for 64-bit Windows - All Codecs - Sunday, 05 May 2019
Chromium 76.0.3786.0 (Official Build) (64-bit) - Dev
Revision 544c8350724e16d3483c611dab5cfd0a8da27cd7-refs/heads/master@{#656670}
OS Windows
Sync - WebRTC - Widevine
SDK 10.0.18362.1 (Visual Studio 2019 16.0.1): October 2018 Update version 1809
clang/llvm 9.0.0-r358823
chrome.packed.76.0.3786.0.7z
Chromium for 64-bit Windows - All Codecs - Sunday, 05 May 2019
Chromium 76.0.3786.0 (Official Build) (64-bit) - Dev
Revision a1d37694c5664e900bb86e7080645bbfc30cbdcc-refs/heads/master@{#656687}
OS Windows
Sync - WebRTC - Widevine
- SDK 10.0.18362.1 (Visual Studio 2019 16.0.1): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
chrome.packed.76.0.3786.0-rev1.7z
Revision a1d37694c5664e900bb86e7080645bbfc30cbdcc-refs/heads/master@{#656687}
OS Windows
Sync - WebRTC - Widevine
- SDK 10.0.18362.1 (Visual Studio 2019 16.0.1): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
chrome.packed.76.0.3786.0-rev2.7z
Why not just use Google chrome beta/canary. It's loaded with Sync and all the google stuff you'd want and it's dev release?
At most, you'll just be missing out on custom build args the devs use here.
@nik: thanks for the help in getting it built w/ sync
@Anon4582: chromium builds don't have "all the google stuff" and that's what I prefer
@Jerry: you should probably add Edge to the proprietary forks list
Should be resolved for now. Some revisions have been reverted. I think part (or all) have been fixed and awaiting relanding.
The other problem over the weekend was a break in V8. Not sure of status. If fixed, I will try to have builds later today or tomorrow. If not and assuming it can be bypassed, I might even consider turning off context creation just to get fresh builds out.
On to other topics, I am trying Polly during loop optimization in the inliner cycle. I get the benefit of LLVM already doing canonicalization and similar, plus not having to resort to using Polly's own early inlining pass.
Thanks for the feedback, and acknowledging Nik's involvement. I appreciate all the help that Nik and RobRich have provided.
@RobRich
In order to get a successful build of Chromium 76.0.3786.0 thinlto was disabled.
ninja: Entering directory `out\LKGR_x64'
[253/253] LINK v8_context_snapshot_generator.exe
FAILED: v8_context_snapshot_generator.exe
ninja -t msvc -e environment.x64 -- ../../../../clang-9.0.0a/bin/lld-link.exe /nologo /OUT:./v8_context_snapshot_generator.exe /PDB:./v8_context_snapshot_generator.exe.pdb @./v8_context_snapshot_generator.exe.rsp
lld-link: error: undefined symbol: CrashForExceptionInNonABICompliantCodeRange
>>> referenced by lto.tmp:(Default_Builtins_UnwindInfo)
ninja: build stopped: subcommand failed.
Comment out as follows:
// w->DeclareExternalFunction(CRASH_HANDLER_FUNCTION_NAME_STRING);
// w->DeclareRvaToSymbol(CRASH_HANDLER_FUNCTION_NAME_STRING);
As to what seems to have happened:
D:\depot_tools\chromium\src\v8\src\unwinding-info-win64.h
https://chromium.googlesource.com/chromium/src/+/fb4ab3be3fc0024d00358d5b7816d3215a8ff20c
https://chromium.googlesource.com/v8/v8/+/969cb0c7a58b4c8b53ff411adde5fc4a5a6785e4
----------------
Win64 updated. This build was mostly about getting Polly moved further down the pass pipeline and configuring its various options. I will restart work on getting other low-level LLVM optimization options back in to the mix for upcoming builds. Due to how ThinLTO currently handles codegen options, I likely will be enabling some options directly in the LLVM source versus passing CLI-derived compiler arguments.
Win32 is building. Probably Wednesday before pushing to public.
----------------
BTW, if anyone is having troubling building current LLVM checkouts due to build errors while compiling Polly, try reverting this change:
git revert --no-commit a1a4adf4b9195799c19e5787e7821f9cf200495a
@RobRich, Nik and Marmaduke: Great releases. Thank you very much for your all work and support!
I'm sharing some benchmarks I did just now for curiosity since it's been a while.
/// Info
Fresh default profiles, no added extensions, settings or flags changed.
Windows 10 64-Bit, 7700K, GTX 1070, 16GB DDR4, SSD.
/// Basemark Web 3.0 - https://web.basemark.com/
Marmaduke UnGoogled Chromium (74.0.3729.108)
Score: 1408.97
RobRich Modified Chromium (76.0.3788.0)
Score: 1349.61
Vivaldi (2.5.1525.40)
Score: 1251.47
Microsoft Chromedge (Beta Version) (75.0.139.7)
Score: 1222.83
Firefox Nightly (68.0a1)
Score: 918.56
/// JetStream 2.0 Benchmark - https://browserbench.org/JetStream2.0/in-depth.html
Marmaduke UnGoogled Chromium (74.0.3729.108)
Score: 151.113
RobRich Modified Chromium (76.0.3788.0)
Score: 150.163
Vivaldi (2.5.1525.40)
Score: 146.009
Microsoft Chromedge (Beta Version) (75.0.139.7)
Score: 144.994
Firefox Nightly (68.0a1)
Score: 107.110
----------------
@Warren Thanks for the feedback! :)
One note. There have been some regressions in Basemark Web 3.0 as of late due to devs default enabling of BlinkGenPropertyTrees back in March to continue testing, refining, and optimizing BGPT for an planned official launch in M75.
https://www.chromium.org/teams/rendering
If comparing to older revisions or branches when benching BW3, disabling BGPT has been the workaround for me.
chrome://flags/#enable-blink-gen-property-trees
----------------
On a more general note, if anyone is interested in testing graphics only, MotionMark probably is a "better" benchmark for expected browser workloads these days: canvas, css, svg, etc.
----------------
I reported the V8 bug regarding LTO building. There were a couple of ideas for an actual fix. Looks like they probably will go with a dllexport declaration.
https://chromium-review.googlesource.com/c/v8/v8/+/1601423
Disabled BGPT for both builds below.
/// Basemark Web 3.0
RobRich Modified Chromium (76.0.3788.0)
Score: 1592.54
Marmaduke UnGoogled Chromium (74.0.3729.108)
Score: 1494.49
/// MotionMark 1.1
RobRich Modified Chromium (76.0.3788.0)
Score: 741.45 ±1.16%
Marmaduke UnGoogled Chromium (74.0.3729.108)
Score: 674.50 ±1.52%
The 'archive' download of ungoogled-chromium uses the usual chromium profile location in %appdata% so it will conflict with any other version of chromium. I cannot say for the portable version but I assume it uses some frontend to contain the profile within the 'portable area'. Someone else has to confirm that.
----------------
Speaking of performance opportunities, I have started a developer discussion on maybe getting lld-link to pass along llvm polly args when doing lto.
The idea is to hopefully get polly working before the loop vectorizer during the thinlto pipeline, thus potentially improving polly via increased interprocedural optimizations.
https://en.wikipedia.org/wiki/Interprocedural_optimization
Basemark Web 3.0 approximately 5% better than non-polly.
Polly parameters:
"-mllvm", "-polly",
"-mllvm", "-polly-position=early",
"-Xclang", "-Rpass-analysis=polly",
"-mllvm", "-polly-parallel-force",
"-mllvm", "-polly-allow-nonaffine=1",
"-mllvm", "-polly-ast-detect-parallel",
"-mllvm", "-polly-vectorizer=stripmine",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-opt-maximize-bands=yes",
"-mllvm", "-polly-run-dce"
Chromium for 64-bit Windows - Ungoogled - Saturday, 11 May 2019
Chromium 74.0.3729.108 (Official Build)
Revision daaff52abef89988bf2a26091062160b1482b108-refs/branch-heads/3729@{#901}
OS Windows
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly
https://github.com/macchrome/winchrome/releases/download/v74.0.3729.108-r638880-Win64/ungoogled-chromium-74.0.3729.108-1_windows.polly.7z
do you have a timetable for when you build new ungoogled-chromium? or perhaps just wait until major releases?
thanks
@marmaduke Nice bump with Polly. We might get ya' even a little more with a few Polly tweaks. My build box is powered down right now, but I will post my latest set of Polly tweaks in awhile as I might push a further modified build from last night anyway.
You might need to revert the following commit if building a current LLVM revision, as yesterday it was breaking Polly for my particular Chromium build config.
git revert --no-commit 2698390c68b5af71d8d46854148115084b8b24a5
My current Polly configuration. It might add a "little" to build times.
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-allow-dereference-of-all-function-parameters",
"-mllvm", "-polly-analysis-computeout=8000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-delicm-max-ops=100000000",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-max-ops=10000000",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-position=after-loopopt",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
If running Polly early in the pass manager, I suggest also enabling Polly's inliner pass. You will get a slight code bloat as a result, but it typically increases SCoP opportunities since Polly at early runs before the standard non-PGO LLVM inlining pass(es).
"-mllvm", "-polly-run-inliner",
Despite not being recommended in most cases, I run Polly later in the pass manager so LLVM already has done its usual canonicalization passes without relying upon Polly's running its own list of several canonicalization passes. I actually moved Polly around in the pass manager, but its own after-loopop position seems okay for my purposes. I started a casual discussion on maybe getting it into the ThinLTO passes near the loop vectorizer, which is already the default Polly position in non-ThinLTO builds.
The polly-opt-maximize-bands option already defaults to yes, so you can skip setting it.
The various parallel stuff can be skipped since we are not using OpenMP at this time. It is something I previously have considered trying to implement for Linux builds, but I have not dealt with building Chromium for Linux in quite awhile.
I find trying to maximize loop fusion tends to lead to potential Polly crashes during building. Not always, so YMMV. After experiencing enough crashes over the years in already long build times, I just leave it at minimum these days.
Stripmining outer loops *usually* works okay, but I have seen it seemingly hang on some multimedia code despite computeout and similar limits. Another YMMV.
About the limits, I upped delicm by 100x default, though a few functions still overrun zone analysis. o.0 The others are upped by 10x default. However, if building takes a ridiculous time due to Polly, dropping all the custom limits and the two precise options - just remove the various clfags - should be acceptable enough for what we are doing with Chromium.
If desired, you might also consider enabling AVX support for SIMD vectorization, though it does break backwards compatibility with older processors lacking the instruction set. It might require some experimentation, which I should get around to doing some day, as performance results can be variable depending upon various optimizations, specific processors, etc.
I set AVX in the x86 target description when building LLVM, but it is also possible to get clang to pass it as a feature. When adding Polly to Chromium's common_optimize_on_cflags, just add the following cflag.
"-mavx"
Other instruction set options are available via clang cflags at build time and/or editing the X86.td config before building LLVM.
If you want to keep tabs on vectorization with ThinLTO enabled, you can add the following ldflag. Note it is not realtime per-function scrolling like with clang, but lld instead pools and later emits the remarks at once.
"-mllvm:-pass-remarks=loop-vectorize",
You likewise might as well also verify vectorization (and enable AVX if desired) in the NaCl compiler build config file, too. Note that NaCl does not use LTO, Polly, etc. In fact, NaCl is (was?) planned to be discontinued this year.
"-mavx",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass=loop-vectorize",
///Info
Windows 10 64-Bit, 7700K, GTX 1070, 16GB DDR4, SSD.
Fresh default profiles per test, no extensions added or browser settings changed.
(chrome://flags/#enable-blink-gen-property-trees -> disabled for both per RobRich' advice #comment-4589)
RobRich Modified Chromium (76.0.3791.0) (658675)
Score: 1533.9
https://web.basemark.com/result/?4QEG1gpc
Marmaduke Experimental Polly Build (Ungoogled Chromium) (74.0.3729.108) (656670)
Score: 1545.59
https://web.basemark.com/result/?4QEGCuvg
// MotionMark 1.1
RobRich Modified Chromium (76.0.3791.0) (658675)
Score: 718.02 ±1.16%
Marmaduke Experimental Polly Build (Ungoogled Chromium) (74.0.3729.108) (656670)
Score: 673.47 ±1.49%
/// JetStream 2.0 Benchmark
RobRich Modified Chromium (76.0.3791.0)
Score: 150.299
Marmaduke UnGoogled Chromium (74.0.3729.108)
Score: 150.810
Previous benchmark: #comment-4590
With respect to ungoogled, I build the initial release, (usually) ignore the first update, then time permitting build the subsequent updates.
@Warren
Thanks for the independent testing.
@RobRich
Really appreciate your feedback. There are very few examples of polly being used in a real world context.
http://xdabloger.blogspot.com/2016/05/xda-devdb-part-1_10.html
Here's an experimental build using your parameters. The build time is considerably longer!
==
Chromium for 64-bit Windows - Ungoogled - Sunday, 12 May 2019
Chromium 74.0.3729.108 (Official Build)
Revision daaff52abef89988bf2a26091062160b1482b108-refs/branch-heads/3729@{#901}
OS Windows
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly: RobRich parameters
https://github.com/macchrome/winchrome/releases/download/v74.0.3729.108-r638880-Win64/ungoogled-chromium-74.0.3729.108-1_windows.polly-rev1.7z
SHA1 8120CA97BB6ECAAECE684B83CE6CCA00BFD813D7
http://pollylabs.org/publications.html
https://llvm.org/devmtg/
Realistically, given what we are doing with Chromium, I suspect the following config would be plenty acceptable for a ThinLTO build.
"-mllvm", "-polly",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass-analysis=polly",
My current Polly config is *way overdone* and still needing checked for possible performance regressions, but as ya' likely can tell, I like trying out the various options. o.0
My current r658675 build has started to once again roll in some of my usual LLVM tweaks for loop optimizations, vectorization, register allocation, etc. I might try breaking them down later, as many are being set by modifying LLVM source code instead of dealing with passing lots of cflags and ldflags from the Chromium build config files.
Right now I am poking at induction variables transformation, possible additional loop distribution opportunities, upping check thresholds in couple of loop-related passes, enabling newgvn, and replacing the traditional gvn passes in the Polly codegen cleanup stage with newgvn.
"-mllvm", "-polly-opt-outer-coincidence=yes",
*Ideally Polly needs to be the in late position as currently intended by its devs, as it can do delicm transformations anyway, but that is not an option for ThinLTO building right now since LLD does not know about Polly.
I am also revisiting some of my previous internal experiments with the Polly early inliner pass, like tweaking the inlining threshold. I am not too concerned about code bloat, but I will have to watch out for performance regressions. Fun stuff. Again, another reason Polly works better in the late position after LLVM is done with its own inlining passes.
One that same note, I am also checking into the profitability detection threshold. I am likely "optimizing" way too much at a 40 instruction minimum. and by "optimizing" I mean wasting time processing lots of trivial loops that LLVM passes can already handle easily enough. Some advanced optimizations on relatively simple or otherwise trivial code even can incur performance regressions. That again is getting back to the previous dialog about getting around to more seriously benchmarking these types of changes.
I am still out on implementing NewGVN. It breaks (well, more like hangs) the building of at least one component during the LLVM pre-ThinLTO pass(es). I can and already have worked around that specific issue if need be, but I am not there are many (any?) significant benefits for us. Again, perhaps something to further examine later.
------------
Let's drop dependancy analysis back to sane levels, especially since we are not doing heavy lifting for something like parallel optimizations for OpenMP anyway.
Same thing for the various pass thresholds and instruction profitability threshold; at least for now.
Let's drop phi normalization. It was implemented to deal mostly with gvn loadpre, and we are not running the gvn pass before Polly at early.
Let's drop treating all function parameters as dereferencible. It appears to largely be a workaround for dragonegg, which we do not use. Otherwise, Polly by design is supposed to treat invariant load hoisting conservatively anyway.
DeLICM likely is not needed much at the Polly early position, but I left overapproximate writes for now in case of potential partial accesses.
The precise options are staying pending further evaluation. I know Polly documentation suggests they do not scale well, which is basically an issue for build times, but I can see their possible benefits. Now as to if they are benefiting our purposes is another question.
------------
For the TLDR crowd....
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
Thank You for :
Chromium for 64-bit Windows - Ungoogled - Sunday, 12 May 2019
But if you can.
Think to 32bit users.
Thank you.
Will push a conventional 32-bit build.
=================
Chromium for 64-bit Windows - Ungoogled - Tuesday, 14 May 2019
Chromium 74.0.3729.157 (Official Build)
Revision 7b16107ab85c5364cdcd0b2dea2539a1f2dc327a-refs/branch-heads/3729@{#998}
OS Windows
No Sync - WebRTC - Widevine - All Codecs (x64) - ThinLTO - Polly
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
- SDK 10.0.18362.1 (Visual Studio 2019 16.0.1): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
ungoogled-chromium-74.0.3729.157-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v74.0.3729.157-r638880-Win64/ungoogled-chromium-74.0.3729.157-1_windows.7z
SHA1 A4934905FB37CE959912DA5E00DAA9979245FA2F
Ok.
Too bad Ungoogled is the best for old PC.
Thank you for all your work.
Is there any way to download your builds as standalone package without nay installer nonsense? The way https://download-chromium.appspot.com/ does it.
https://github.com/RobRich999/Chromium_Clang/releases
----
@marmaduke The 32-bit build is calling an intrinsic that apparently is not available with the particular build config. It is the 32-bit intrinsic issue I mentioned awhile back.
You can provide it with the 32-bit compiler-rt builtins. Considering I have no immediate interest in building 32-bit compiler-rt libraries, I simply extracted the needed builtin library from a recent 32-bit LLVM snapshot build.
https://prereleases.llvm.org/win-snapshots/
Extract clang_rt.builtins-i386.lib and pass it as a ldflag via the Chromium compiler or windows build config file. For example:
ldflags += [ "/defaultlib:D:/src_builds/llvm-monorepo/llvm-i386-files/clang_rt.builtins-i386.lib" ]
please
i hate new google design for chrome/chromium from version 71 and latest
i need chromium version 70 or 69
please say me where can i download this?????????
VERY IMPRORTANT
Here are niks releases
https://github.com/henrypp/chromium/releases
And specifically here is the last version 70 built by him
https://github.com/henrypp/chromium/releases/tag/v70.0.3538.110-r587811-win64
----------------
Other than maybe some minor tweaks, which I will post about if significant, I probably am done with configuring with Polly for awhile!
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
Polly at early runs before gvn-pre and loop licm, so let's disable delicm. Delicm is more beneficial when Polly is running further down in passes. It also can be an expensive pass with limited returns for our config, especially with the high threshold values needed to not overrun zone analysis on a few functions when building Chromium. Polly ran without a delicm pass for several years back when it defaulted to the early position anyway. I would rather spend the time difference in dependence analysis and similar to hopefully build successful and quality SCoPs.
I am not seeing much (any appreciable?) difference with operand tree forwarding enabled. The TLDR, it was implemented a couple of years ago and has continued development to move certain types of instructions between statements to help avoid scalar dependencies. I can see the benefit for HPC-class or similar code, but from a casual glance, our successful SCoP rate when building Chromium seems about the same without it. Toss it.
I turned off dependence simplification. It removes domain constraints to help decrease time spent by the ISL schedule optimizer. It can offer a huge compile-time difference when building complex code, but again, we are not dealing with HPC-class or similar complexity here. The trade-offs when enabled also can be affecting other transformations and/or even limiting the ability to find a successful schedule. I am not seeing a significant Chromium build time difference with it disabled, so let's toss it.
Likewise I unbounded computeout on dependencies. I am not seeing a substantial change in build time, so again, we might as well spend the seemingly little extra incurred time building hopefully successful and quality SCoPs.
I dropped the precise options. One or both, as I did not check, were hanging the building of at least one multimedia component for *hours* without SCoP generation when opting for unbounded dependence computeout. SCoP rate casually looked about (or likely) the same, so whatever IMO.
Perhaps the biggest change is dropping the Polly early inlining pass. Chromium does involve lots of templated code, but I found the inlining pass largely pulled in libc++ code, which often returns unsuccessful SCoPs due to low complexity and/or low profitability. Let's skip wasting time on those functions and instead target important functions that Polly still successfully optimizes, such as various functions related to cryptography, multimedia, rendering, etc.
Looking forward, I might experiment with allowing non-affines and/or again lowering the profitability instruction limit, but I have a feeling doing either largely will waste build time by adding lots of otherwise unsuccessful SCoPs to analyze.
----------------
My build box is cooking a Win64 build right now. Win32 next. Assuming no unforeseen issues, I should have updated for both later today. :-)
----------------
Not that it usually results in significant performance differences, or more like sometimes even regressions, but I *might* have an updated AVX2 experimental build ready for public testing today or tomorrow.
----------------
Head's up. Basemark Web 3.0 finally returned better performance with the BlinkGenPropertyTrees flag at default rather than manually disabled in a couple of quick runs with my Win64 r661418 build. I did not do multi-pass testing or check other benchmarks, so YMMV.
----------------
Experimental Win64 AVX2 build available. Polly, ThinLTO, etc. as usual. Since the AVX2 target includes FMA, I have enabled -ffp-contract=fast support as well. AMD Zen, Intel Haswell, or later x86-64 processors with AVX2 support required. AMD Excavator is a "maybe."
https://github.com/RobRich999/Chromium_Misc/releases/tag/v76.0.3801.0-r661521-win64
Speaking of -ffp-contract=fast, I have filed a bug to get it enabled for Skia's own AVX2 codepath on Windows to match Linux, MacOS, etc. A project dev has already picked up the bug report. :-)
Scroll down to the bottom and check for any logged diagnostic messages. If there are errors, use the copy report to clipboard button at the top of the gpu page, paste it to somewhere like pastebin.com , and post the link here.
Without any diagnostic data, it looks like corruption with hardware acceleration IMO. For a quick check, go to settings and disable hardware acceleration.
If disabling hardware acceleration fixes it, you can try using a different ANGLE backend as a temporary workaround to re-enable at least some level of hardware acceleration support. For example, Chromium on Windows usually opts for D3D11 if possible, so try dropping it down to D3D9. It might be slower or not support certain options, but it probably still is preferable to software rendering.
I'm using an up-to-date 1809 installation, with the latest Intel driver.
Wen't to the site that caused the issue and I've attached the chrome://gpu log
https://pastebin.com/paaiXk8i
Thanks
Chromium 74.0.3729.169 (Official Build) (64-bit)
Revision 78e4f8db3ce38f6c26cf56eed7ae9b331fc67ada-refs/branch-heads/3729@{#1013}
OS Mac OS X
only for macOS 64
with codecs (h264, h265, flac, xvid, AV1, etc..)
official build
Xcode 10.2.1
macOS SDK 10.14
clang/LLVM 8.0.0-r348396
ThinLTO
Polly optimised
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly"
Sync • WebRTC • Widevine
Chromium.74.0.3729.169.sync.app.zip
https://github.com/macchrome/macstable/releases/download/v74.0.3729.169-r638880-macOS/Chromium.74.0.3729.169.sync.app.zip
SHA1 E0BBE44307C497AA8A4DE329FDA8F2AACBEB0B4F
No Sync • WebRTC • No Widevine
Chromium.74.0.3729.169.nosync.app.zip
https://github.com/macchrome/macstable/releases/download/v74.0.3729.169-r638880-macOS/Chromium.74.0.3729.169.nosync.app.zip
SHA1 F4B366E7A4BEECD61781560094D37785BD358E1D
Intel awhile back changed over to a DCH "universal" driver platform for Windows 10, thus perhaps why you might not have received an update. Version 26.20.100.6861 is the current driver release.
https://downloadcenter.intel.com/download/28783/Intel-Graphics-Windows-10-DCH-Drivers?product=80939
BTW, The Intel graphics configuration app is separate now, too. You from the Microsoft store.
Quote: "The JetStream 2 JavaScript benchmark saw 2~3% lower performance with the AMD systems while the Intel systems with their default mitigations could be easily lower by 10% or more."
Source: The Performance Impact Of MDS / Zombieload Plus The Overall Cost Now Of Spectre/Meltdown/L1TF/MDS
https://www.phoronix.com/scan.php?page=article&item=mds-zombieload-mit&num=10
I'm still on a stock Intel 7700K (Spectre & Meltdown patched) but have not updated or applied the recent Intel patches or disabled hyper threading and not sure I will as I've seen other reports showing up to *40% performance hits in certain applications and games that utilize hyper threading.
Example, Hyper Threading Disabled:
* "As ZombieLoad leaks loaded values across logical cores, a straightforward mitigation is disabling the use of Hyper-Threading. Hyper-Threading improves performance for certain workloads by 30 percent to 40 percent."
Source: https://www.pcworld.com/article/3395439/intel-hyper-threading-zombieload-cpu-exploit.html
"to make sure any exploits can't affect Chrome users, Hyper-Threading is now disabled by default." (Not sure if this also means Chromium 74+)
https://www.androidcentral.com/mds-vulnerability-chrome-os
https://sites.google.com/a/chromium.org/dev/chromium-os/mds-on-chromeos
I update my CPU every 5 years but I'm really considering moving to AMD as this is getting old and tiresome, it's that or get a 9900K, bye $$$....
Comparison Exploits: AMD vs Intel:
Not sure if there's anything you can do RobRich in your build config to gain back that 10% loss but thought I'd share this anyways, Take care.
----------------
@Warren Most of these side-channel attack issues are at the hardware and/or OS level, and much of the performance losses depend upon the particular code being executed. For example, while JetStream 2 is a good JS benchmark, it is not indicative of a typical page load workload experience.... unless you only surf JS benchmarks.
The browser Chromium can not disable HyperThreading. It needs to be done at the firmware or OS level, thus the discussion of the operating system ChromiumOS. I know there are proof-of-concepts for portsmash, tlbleed, etc. Simultaneous multithreading probably was not a great idea even back in the day, except maybe on paper or during the single-core Pentium 4 era. These days is quite different IMO, and most users outside of HPC or similar roles are unlikely to notice any appreciable difference between, say, an 8c vs an 8c/16t processor on the same architecture anyway. SMT was not a huge concern even when buying my current Kaby Lake notebook, thus it was a native 4c i5 instead of a similar 4c/8t i7.
Chromium does support site isolation, which reportedly helps immensely with side-channel attack mitigation. BTW, while usually disabled when building on platforms with site isolation support, technically it is possible to also manually enable "v8_untrusted_code_mitigations" when building V8 if desired.
https://www.chromium.org/Home/chromium-security/ssca
Beyond just benchmarks, for now anyway. it is not a clear case of AMD versus Intel for x86 systems. Practically any out-of-order processor using speculative execution with branch prediction could be a hypothetical target for side-channel attacks. Sure, there are supposed to be serious hardware mitigations for meltdown and spectre with Intel Ice Lake and AMD Zen 2, but are those mitigations going to offset future possile SCA vectors? It is a huge YMMV; seriously.
Performance impacts are hardly uniform either. For an example regarding Meltdown, Intel Haswell and later processors with INVPCID support running an OS capable of using the hardware feature in conjunction with dual page tables generally should have a much lessened impact compared to using older Intel processors using the dual page tables mitigation alone.
On the Spectre v2 (BTB) side, you are looking at a mix of mitigations including indirect branch restricted speculation, single thread indirect branch predictors, and/or indirect branch prediction barrier. Admittedly, those can lead to significant performance impacts; again depending upon workload. The later the processor architecture; probably less the impact.
On a plus note for AMD plus Intel Broadwell and earlier processors, Microsoft finally is rolling out retpoline-based Spectre v2 mitigation support along with with an import optimization feature in Windows. These are expected to substantially offset the performance issues for affected architectures compared to Windows' existing Spectre v2 mitigations.
https://www.bleepingcomputer.com/news/security/boost-windows-10-performance-with-retpoline-spectre-mitigation/
https://www.bleepingcomputer.com/news/microsoft/windows-10-update-kb4482887-released-with-performance-fix-for-spectre-bug/
----------------
Speaking of JS optimizations stemming from JetStream 2 analysis, this patch just landed in Chromium trunk about an hour and half ago when pulling in V8 7.6.303. :-)
https://chromium.googlesource.com/v8/v8/+/734c1456d942a03d79aab4b3b0e57afbc803ceea
This little note to say that your builds still work ok, and to thank you again. :-)
But I came back using Waterfox as my main browser, a few months ago, because I had a lot of small boring issues with Chromium in general, on a few sites I use a lot. It's very likely that those sites are badly built too (some of them fire never ending captchas in Chromium... :-( ) or some extension have issues, etc. so there was no need to bother you with those itches. ;-)
I still use Chromium as an excellent secondary browser, though.
Thanks again.
https://github.com/uBlockOrigin/uBlock-issues/issues/338#issuecomment-495936668
Since a few versions, I can't see recaptch
https://patrickhlauke.github.io/recaptcha/
Box shows but not the images in it.
Latest win 64 ungoogled version
Any clue? Thanks!
Corrupted browser profile?
Any content filtering extensions loaded? Disable one by one if so to find a possible culprit.
Have you tried refreshing your WAN IP address(es)? Banned IP addresses and ranges are possible.
Using a proxy or VPN? There can be banned IP issues and similar there, too.
Chromium 77.0.3814.0 (Official Build) (64-bit)
Revision c956417e38d37def6b4a30d2b3a919323212383f-refs/heads/master@{#665522}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.0.1): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
- ThinLTO
- Polly
- WebRTC
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
No Sync - No Widevine
https://github.com/macchrome/chromium/releases/download/v77.0.3814.0-r665522-Win64/Chrome-bin.7z
Chrome-bin.7z (chrlauncher formatted)
SHA1 CCAFF1AD1E8276D1A74500EE4EA567B0BA604E41
Sync - Widevine
Chrome-bin-sync.7z (chrlauncher formattedhttps://github.com/macchrome/chromium/releases/download/v77.0.3814.0-r665522-Win64/Chrome-bin-sync.7z)
SHA1 FEE9A18C2F7D63701637F3C3604E98EE01D698A9
https://cryptmode.com/best-vpn-for-security-privacy-anonymous-highly-secure-vpn-no-logs/
https://tech.co/vpn/zenmate-vpn-review
https://www.comparitech.com/vpn/reviews/zenmate-review/
I've been using premium ZenMate for a few years and I find it satisfactory in terms of privacy.
Hello , do you foresee a new Ungoogled 75.0.3770.80 ( 64bit and 32 bit ) ?
Thank You...
Yes. I'll turn my attention to ungoogled when I've finished messing about with my new macOS Catalina build system.
======
Chromium for 64-bit Android - Thursday, 06 June 2019
Chromium 75.0.3770.82 (Official Build) (64-bit)
Revision 8c7f0c80fc7a24ae5d4f05276ef61949e13dccbe-refs/branch-heads/3770@{#957}
OS Android 9: ONEPLUS A6000 Build/PPw29.116-16
OS Android 64-bit
- only for Android 64
- official build
- All Bromite patches applied (AV1 test streams do not work!)
- HEVC
Personally, I still think that v73 is better if you want comprehensive CODEC support.
No Sync • No Widevine • ThinLTO • Bromite • HEVC
https://github.com/macchrome/droidchrome/releases/download/v75.0.3770.82-r652427-Ungoogled-And64/arm64_ChromePublic_HEVC.apk
arm64_ChromePublic_HEVC.apk
SHA1 E4BD7BC2C9E4C251FA321DAFA8A4BC2858875035
Your last build, which is again 74.0.3729.157-1 has this patch, which is causing browser crashing.
.\../../content/browser/tracing/tracing_controller_impl.cc(199,40): error: use of undeclared identifier 'coordinator_'
tracing::mojom::kServiceName, &coordinator_);
A crude fix is to comment out any function which contains "coordinator_" - If you replace "coordinator_" with "drainer_" then build you will get errors, take note of the errors and amend the code accordingly.
For a successful build do not apply the safe browser patches AND:
debian_buster/fixes/alignof.patch
debian_buster/warnings/enum-compare.patch
debian_buster/warnings/explicit-constructor.patch
I used xsmile's revised common patches.
@Anon4640
I'm aware of the issue, which I ignored because the issue didn't affect me when tested.
I made a benchmark tests between marmaduke's 74.0.3729.157-1 and 75.0.3770.80 and the v74 is much faster in the benchmaks.
I have big big question, which Intel driver are working best for you guys?
v75 is not polly optimised. Future versions will be.
In the Secure Preferences section, you leave a note about Brave portable (PortableApps::Brave portable). Portapps is not part of PortableApps so can you change it with something like Portapps::Brave portable and put the following link instead of the GitHub issue : https://portapps.io/app/brave-portable/#infos
Thanks!
As of now, I didn't receive 75.0.3770.80 version from Chrlauncher yet, using stable-codecs-sync build. Is this normal? Can I force a check for updates?
Thanks!
Does Chrlauncher check for updates even if the flag "ChromiumCheckPeriod" in the .ini is set to 0 (disable update checking)?
I downloaded the portable version for stable-codecs-sync (Nik build) and by default this flag is set to 0, but I remember getting updates to new Chromium versions automatically before. However, for 75.0.3770.80 version, I didn't get the update until I set this flag to -1.
@Portapps: Yes. Exactly. My apologize. I changed the name and link to Portapps::Brave portable in #secure-preferences
@Anon4647: Thank you for your report. I see their latest version is https://chocolatey.org/packages/chromium/74.0.3729.169
@Anon4648: In Chrlauncher, if "ChromiumCheckPeriod=0" → there is no update. Put a number to update... or "-1" to force the update.
IMO, it should allow us to completely disable any update check and act just like a "shortcut"
Sorry for my mistake and thanks for your help, WildByDesign!
I'm running Chromium 75.0.3770.80, it is very stable build on Windows 7 x64 SP1.
The only problem is that Emojis are not loading on site like instagram.com (emojis are replaced with squares).
About Emojis on Windows 7, this is not a problem with Chromium. I have got colored Emojis on Windows 7, on all websites.
This is the way:
- Make sure https://support.microsoft.com/en-us/help/2729094/ is installed.
- Now, download the "Segoe UI Emoji" font from Microsoft Windows 8.1 at https://www.wfonts.com/font/segoe-ui-emoji and put the TTF file in your system at C:\Windows\Fonts
- Restart your computer
- To check if all works normally, go to https://getemoji.com/ and https://emojipedia.org/
You can find squares but most of Emojis works! 😉👍
Followed your instructions and it works out of the box! 😉 😊
https://chrome.google.com/webstore/detail/chromoji-emoji-for-google/cahedbegdkagmcjfolhdlechbkeaieki
Chrlauncher updates this number to indicate the last time it checked for updates.
Chromium 75.0.3770.90 (Official Build) (64-bit)
Revision a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}
OS Android 9: ONEPLUS A6000 Build/PPw29.116-16
OS Android 64-bit
- only for Android 64
- official build
- All Bromite patches applied (AV1 test streams do not work!)
- HEVC
No Sync • No Widevine • ThinLTO • Bromite • HEVC
https://github.com/macchrome/droidchrome/releases/download/v75.0.3770.90-r652427-Ungoogled-And64/arm64_ChromePublic_HEVC.apk
arm64_ChromePublic_HEVC.apk
SHA1 8617D9E51CCB4461A1B19C81C97028E773F42BA5
Be somewhat surprised it has worked this long, and I would not be too surprised to see the PNaCl version discontinued even in Chrome at some point. PNaCl support was supposed to be discontinued in Q1'19 except for Chrome Apps, and technically Chrome Apps support was supposed be discontinued last year except for ChromeOS. Apparently the schedule has been pushed back to Q2'19; as in the current quarter.
https://developer.chrome.com/native-client/migration
A Microsoft product manager has confirmed the new Chromium-based Edge browser is affected as well. Google reportedly is blocking via user agent sniffing.
https://www.bleepingcomputer.com/news/microsoft/microsoft-pm-explains-why-chromium-edge-can-t-run-google-earth/
As for the migration path, Google Earth was demonstrated running atop WebAssembly back in 2017.
https://medium.com/google-earth/earth-on-web-the-road-to-cross-browser-7338e0f46278
As of May 2019 regarding the WASM migration, a Google Earth project manager claims, "We look forward to sharing preview access in the coming weeks."
https://medium.com/google-earth/performance-of-web-assembly-a-thread-on-threading-54f62fd50cf7
In the meantime you might trying using an User Agent extension to change Chromium's UA string to instead report the current stable Chrome release version as a potential temporary workaround. As I often say about these things, YMMV.
Thanks for the Chrome-bin-sync.7z builds!
Scott
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce"
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
[Edited by Jerry: Jun 17, 2019 07:45 - Good luck Rob! ;)]
Another builder FYI. Hopefully we eventually will be able to run Polly at the currently preferred "-polly-position=before-vectorizer" with ThinLTO.
There is a LLVM extension project in development with Polly as the initial support target. I recently let Polly devs know about needing to initialize and register Polly passes in LLD to enable running Polly before vectorization during ThinLTO codegen, and it has been mentioned to the dev working on the extension code.
---------------------
I have Google Earth working in Chromium Win64 77.0.3828.0 r669546 without having to modify the user agent string.
Force enable the following flag:
chrome://flags/#enable-nacl
PNaCl has been moved to a reverse origin trial for phased deprecation. Manually forcing NaCL restores the previous (P)NaCL behavior. Appears 12/3/2019 is the currently expected phase out date.
Microsoft Edge for Windows 7, 8.1, 10 and macOS on Canary Channel (Updated daily) https://www.microsoftedgeinsider.com/en-us/download/
I did some benchmarks and tests and unfortunately with the 75.0.3770.80 and 75.0.3770.90 I have browser crashing with the "aw, snap" message with profile without any extensions. I didn't have similar problem with the previous releases.
Marmaduke, it's there any chance if you can make polly version with the 74.0.3729.169-1 or with the 73.0.3683.103-2. I know there are older releases..... but at the moment the Chromium v74.0.3729.157 is much faster than the 75.0.3770.80 , 75.0.3770.90 and 73.0.3683.103.
I don't know but I think the polly version of the 73.0.3683.103-2 will be the fastest from the ungoogled builds.
I really don't want to do reto builds. Which operating system are you using, and which benchmarks are you undertaking?
I have Windows 10 1809 build. For example MotionMark at https://browserbench.org/MotionMark1.1/ or https://web.basemark.com/
Using Windows 10 1803 x64: Chromium 75.0.3770.90 (Official Build) (64-bit) - Ungoogled
I managed to run both benchmarks, https://browserbench.org/MotionMark1.1/ and https://web.basemark.com/, successfully. But I had to disable all of my extensions, and used a minimal command line:
Command Line "C:\Local Programs\Chromium x86\App\Chromium\x86\Chrome.exe" - --user-data-dir="C:\Local Programs\Chromium x86\Data\ChromePortableData" --ppapi-flash-path="C:\Local Programs\Chromium x86\Data\PepperFlash\pepflashplayer64.dll" --ppapi-flash-version=32.0.0.156 --disable-presentation-api --disable-java --save-page-as-mhtml --lang=en-GB --flag-switches-begin --flag-switches-end
I'll compile future 75.0.3770.xxx ungoogled builds using the v74.0.3729.157 polly parameters: v75.0.3770.90 was compiled using RobRich's latest parameters:
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce"
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
For completeness, I'll probably compile 74.0.3729.169 using the same build system as 74.0.3729.157, time permitting.
Since you start building the ungoogled versions, I am doing representative benchmarks and test them on daily basics for overall stability and performance. Offcourse that depends not only from your side but and from the changes made by the Chromium team and Eloston. You did a massive step with this builds in this learning process!
I think you're aware of that but Eloston recently reported for tab crashes with the 75 version, which he reproduce them on LinkedIn under Debian OS. Currently on my system the version 75.0.3770.90 is crashing not on regular basics and pages from time to time and that's without any extensions. I think since version 74 I start to using a flag under the chrome://flags/#enable-filesystem-in-incognito and I don't know if that mean something. The only think which I see with the 74.0.3729.157 is the browser crashing under the Clear HTTP auth cache which is known issue with the ungoogled builds. That issue doesn't effect the usage of the browser on daily basics.
Try this - I've tried to use the same build criteria as 74.0.3729.157. Build 74.0.3729.169 has the same build error as v75:
content/browser/tracing/tracing_controller_impl.cc - error use: of undeclared idenitifier 'coordinator_' - which I've worked around and could possibly be introducing instability.
For build 74.0.3729.157, I patched the core code myself, for subsequent builds I've used Eloston's standard core patches, and where necessary amended the Windows specific patches.
===
Chromium 74.0.3729.169 (Official Build) (64-bit)
Revision 78e4f8db3ce38f6c26cf56eed7ae9b331fc67ada-refs/branch-heads/3729@{#1013}
OS Windows x64
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly - 64-bit
ungoogled-chromium-74.0.3729.169-windows-x64.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v74.0.3729.157-r638880-Win64/ungoogled-chromium-74.0.3729.169-windows-x64.7z
SHA1 32EA14FBF2A06C4F723C13D7A927B1C24591DB03
Thank you for your effort. I will test the 74.0.3729.169 and I will let you know what is the result.
A chance to have a version 32 bit-windows of ungoogled-chromium-74.0.3729.169 ?
Thank you...
I'm experiencing some video playback issues on YouTube, but only with certain videos, using Nik's latest 64-bit stable version.
Screenshot:
Link to video: https://www.youtube.com/watch?v=K9ZgPn1rJ9k
There is some artifacting on 4k resolution, but 1080p is completely unwatchable. 720 and 1440 work great though. Other videos work great on any resolution.
On the left of my screenshot it is Nik's Chromium Version 75.0.3770.100 (Official Build) (64-bit)
On the right it's the portable (PAF) Google Chrome Version 77.0.3824.6 (Official Build) (32-bit)
OS is Win10 LTSC 1809
If encountering the issue, try disabling out of process rasterization as a temporary fix.
chrome://flags/#enable-oop-rasterization
————————
The blacked out page rendering issue appears to be a bug with Skia's GLSL (shader) program caching. Trunk builds from 7/18 to 7/25 potentially could be affected.
A temp fix landed in trunk about an hour ago to disable the associated caching mechanism until the underlying issue can be resolved.
https://earth.google.com/web/?beta=1
I did some further testing:
This problem on Nik's builds started with v74.0.3729.108-r638880-win**. It occurs on both 32 and 64 bit versions. This problem appears to affect only Intel GPUs, Nvidias work fine. Idk about AMD.
Nik's v74.0.3689.0-r627581-win64 is the last build to not have this problem.
Marmaduke's Version 75.0.3770.90 (Official Build) (64-bit) does not have this problem either.
Hope it helps in troubleshooting.
To further ease troubleshooting, use this:
youtube-dl -f 248+251 https://peter.sh/experiments/chromium-command-line-switches/#merge-output-format webm https://www.youtube.com/watch?v=K9ZgPn1rJ9k
to store a local copy of the file in question. You'll need youtube-dl and ffmpeg (I used the 32-bit version, if it matters) in the same folder.---------------
Curious, does anyone here actually have a specific need for (P)NaCL support? If not, I am seriously considering going ahead with deprecating it in my builds.
Let's add register tiling back to the mix, as apparently it can do optimization similar to an unroll and jam pass. If it actually is doing anything for us, someone else can collect the stats if seriously interested. ;p Otherwise, I am just enabling it as another possible optimization option.
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
----------------
I am somewhat remiss to recommend running Polly among the LLVM loop optimization passes since Polly devs do to recommend it either. In particular I had previously configured the after-loopopt position to use DeLICM, which can slow building and even hits its default limit on parts of Chromium codebase; and even at rather high manually set limits.
After a little testing, disabling DeLICM does not seem to significantly change ScOP rates for our purposes, and the actual overall (successful?) SCoP rate likely is up due to moving Polly after code inlining anyway. As usual, YMMV.
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=after-loopopt",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
IIRC, I built the release Win64 files a couple of times due to changed build args. My build box is offline tonight, but I will check the files later today (Monday), plus try to get a Win32 build out.
On my windows system the v74 has the best benchmark and performance compared to the present versions of ungoogled chromium.
I didn't have a single crash for that time, like I has with the v75 releases so for me the 74.0.3729.169 is a stable release.
It is not my intention to imply responsibility, but merely as a way of saying thanks.
----------------
Otherwise, just pushed the corresponding 32-bit build, too.
Usually new tab has a couple of icons in the center screen as well as a search bar. Mine just has a Google logo (google doodle?) and that's it.
------------------------
@Anon4698: The new tab page (NTP) might be (and probably is) undergoing changes.
Disable the "Remove fakebox from the NTP" config flag to get the search box back if desired. I suspect the box will be removed since you can search from the URL bar anyway,
chrome://flags/#remove-ntp-fakebox
Shortcut icons on the NTP are based upon history. They are working in my current public Win64 build for me. Have you tried clearing your history, cache, and similar? If that does not work, perhaps try a new profile?
Conversely from you, I am not getting the Google doodle on the NTP page. Well, to be technical it briefly will appear on the first manual NTP load, then disappear for the rest of the session.
https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb?h1=en
It works in Chromium without sync as well.
https://www.google.com/search?q=old+search
75.0.3770.90 (652427) • Friday, 14 Jun 2019
https://github.com/macchrome/winchrome/releases/tag/v75.0.3770.90-r652427-Win64
-----------
If we install a "sync" version (chromium-sync.exe), a message may appear that Google Api-Keys are missing. How can we change a "sync" to a "no-sync" (remain anonymous)?
We write three lines in the command console (cmd):
setx GOOGLE_API_KEY "no"
setx GOOGLE_DEFAULT_CLIENT_ID "no"
setx GOOGLE_DEFAULT_CLIENT_SECRET "no"
+ Enter
Now the error message no longer appears and we are more anonymous.
The big issue is running Polly correctly with LTO enabled. FullLTO does a potentially "better" job since it places Polly before the vectorizer during the compiler codegen phase. However, LLD does not know about Polly, so it can not initialize it during either type of link-time codegen phase. There is work being undertaken to change how LLVM initializes Polly (and similar) into tools. No set ETA, though, AFAIK.
FWIW, I am still recommending Polly at early with ThinLTO. I am just not sure currently if it is worth spending much "extra" computation time in Polly, along with risking potential build breakage with various advanced and often niche options.
Naturally build times tend to vary by system, so YMMV on what others want to do with their Polly configs. I suspect baseline actually is fine for now until LLD knows how to initialize Polly, then we can get back into the advanced options.
"-mllvm", "-polly",
"-mllvm", "-polly-position=early",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
I would call the inlining pass optional for our purposes. It tends to bring in lots of libc++ code, inflates code size, and spends build time on a litany of otherwise unsuccessful scops.
"-mllvm", "-polly-run-inliner",
Likewise, one can even drop DeLICM with Polly at early if experiencing substantial build time regressions. Polly at early ran without it for years anyway, and I doubt the real-world performance difference is much given our target codebase. Someone might check scop rate differences if inclined, but I am not that concerned, so whatever.
"-mllvm", "-polly-enable-delicm=false",
I am not promising baseline is exactly how my config while be as I continue to poke at optimization opportunities, but it should be okay for our general purposes IMO.
On a side note, LLVM is making more moves to bring the new pass manager online as default. IIRC, opt and maybe clang might work currently with individual parts of Polly when using the NPM, but there is no umbrella "-polly" support at this time. I suppose the project devs will cross that bridge when they get there.
Chromium for 64 and 32-bit Windows - Ungoogled - Tuesday, 16 July 2019
Chromium 75.0.3770.142 (Official Build)
Revision 8d93477bd18154c67a70a67019cb8032382c55dd-refs/branch-heads/3770@{#1160}
OS Windows
No Sync - WebRTC - Widevine - All Codecs (x64) - ThinLTO - Polly Optimised
- SDK 10.0.18362.1 (Visual Studio 2019 16.1.6): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
cflags = [ "/O2", "-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly" ]
Standard build of Eloston's ungoogled-chromium. All patches applied, apart from "Safe Browser". Linking failed due to safe browsing being removed, so I decided not to remove any element of safe browsing.
ungoogled-chromium-75.0.3770.142-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v75.0.3770.142-r652427-Win64/ungoogled-chromium-75.0.3770.142-1_windows.7z
SHA1 25B9E1EBF425F1D8CABC2872AAD72B75BD7AD0FA
Ungoogled-Chromium-75.0.3770.142-Win32.7z (32-bit) - Codecs+
https://github.com/macchrome/winchrome/releases/download/v75.0.3770.142-r652427-Win64/Ungoogled-Chromium-75.0.3770.142-Win32.7z
SHA1 2F0650C5AC79735658AD90403CAF7E532322A290
Much appreciated, I hope you will re-do V76 build with this loophole fixed as I always browse in private mode.
@Jamie R: Thanks for letting us know about that website, I see it is able to tell me if it detects private mode or not making it handy to know once the loophole fixed is implemented. It also has many other handy info, very useful indeed.
@Anon4713
=============
Chromium v78.0.3866.0-r681261-Win64
Chromium for 64-bit Windows - All Codecs - Friday, 26 July 2019
Chromium 78.0.3866.0 (Official Build) (64-bit)
Revision 9a897aa9e12415e1351d0ae2081550673ba7bc82-refs/heads/master@{#681261}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.0): October 2018 Update version 1809
- clang/llvm 9.0.0-r358823
- ThinLTO
- Polly
- WebRTC
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
No Sync - No Widevine
Chrome-bin.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v78.0.3866.0-r681261-Win64/Chrome-bin.7z
SHA1 B11B78F7D5FA0628E1DA6ACBBD742427335648DB
Sync - Widevine
Chrome-bin-sync.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v78.0.3866.0-r681261-Win64/Chrome-bin-sync.7z
SHA1 CD3D3C532D44D8F796FFCDD4523E4A87280D68FF
Win32 just finished building. Need to do a quick test, move some files, then upload to GitHub.
Chromium 78.0.3868.0 (Official Build) (64-bit)
Revision 6e3d1613e99b04b21712d14eb5d044b955b496b4-refs/heads/master@{#681662}
OS Mac OS X
only for macOS 64
with codecs (h264, h265, flac, xvid, AV1, etc..)
official build
Xcode 10.3
macOS SDK 10.14
clang/LLVM 8.0.0
ThinLTO
Polly optimised
"-O3",
"-flto=thin",
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=after-loopopt",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly
Sync • WebRTC • Widevine
Chromium.78.0.3868.0.sync.app.zip
https://github.com/macchrome/chromium/releases/download/v78.0.3868.0-r681662-macOS/Chromium.78.0.3868.0.sync.app.zip
SHA1 B946F49ECFA7BDFA9AD75D3A10CA227E074E7DAB
No Sync • WebRTC • No Widevine
Chromium.78.0.3868.0.nosync.app.zip
https://github.com/macchrome/chromium/releases/download/v78.0.3868.0-r681662-macOS/Chromium.78.0.3868.0.nosync.app.zip
SHA1 CD6693215A1C5B14E7EFEDBABE077F0180EB75BD
I see at #comment-4717, you don't have permission to access. Strange!
Please, check your mailbox. I sent to you an email.
For info, I updated manually your releases (win64 and macOS) on the site. Thanks a lot for your work.
Looks like you've put the links for Marmaduke's MacOS dev versions where the stable versions are supposed to be. ;-)
[EDIT Jul 28, 2019 by Jerry: Thanks a lot @Aargl. My apologies! Updated site]
@Jerry
Hi!
Problem sorted: have to use "--data" now.
Does the sync builds use those?
@marmaduke: SwitchySharp is unmaintened. You should use SwitchyOmega instead. Anymay, good luck for your builds. Hope your issue will be simply resolved. Thanks for all.
@Anon4727: Yes but the Google-internal file containing official API keys must exist.
https://chromium.googlesource.com/chromium/src/+/master/google_apis/BUILD.gn
More info: https://github.com/henrypp/chromium/blob/master/building_chromium_gn.md
As Jerry linked to his guide, third-party developers and/or end-users instead have to setup their own API keys. Those API keys then can be supplied at build time as build arguments or at run time as environment variables. Some features could have quotas, so YMMV on sharing them outside your personal use depending upon what features you or your build's users... well, use. ;-)
If supplying as environment variables, you even can turn a Chromium no-sync build into a sync build. Sync actually is not disabled in no-sync builds. It is just the API keys are explicitly set to "no" at build time, thus it does not work unless API keys are supplied at run time.
----------------
@nik I have enjoyed your efforts with Chromium, and especially so during my earlier build days. Thanks! :-)
Definitely please do not be a stranger here. We appreciate your ongoing insights and experience even if you are not actively building at this time. I also look forward to you hopefully obtaining another build box in the near future.
BTW, I noted your are using Ubuntu. Would you be interested in me restarting public Linux builds? Just let me know.
I hope the building instructions can be more explicit next time around.
"Is there any option, may be in compiling process, for reduce height of tabs, omnibox and bookmarks bar? It's ridiculous, how many useless space in this panels in chromium compare to other browsers. Sorry for bad english, not my native language."
In chrome v13, there used to be a flag you could set for "Side Tabs"
It was an experimental feature which was never made widely known. Google said that because not enough beta testers were enabling it and trying it out that it was not a popular enough feature to keep.
So from a very limited crowd of people, and without any fanfare it was available, google squashed the idea. Methinks google just didn't like the idea pushed by one of their coders because it went against the very strict design of chrome, so was purposely only given a brief airing to a niche audience.
For laptop screens side tabs was brilliant, but did not really solve the amount of vertical space taken by the title bar / url / bookmarks because the title bar still had to be there even with tabs down the side.
I think a Bookmarks Side Bar would be good and would help. There was an extension to do this but I dont think it works anymore. Would rather it was natively coded in chrome personally, doubt if we will see such a thing though. We will forever be viewing forums with bags of empty space at the side of the browser and little verticle space for all those ad banners etc blocking what you want to read, especially on news sites.
As it's updating it says "Current version <not found>" meaning it doesn't know where it's pointing to.
How do I fix this?
Thanks
-------------------
I should add that I'm updating an older version of Chromium on my USB stick. This is not a fresh install.
@scorpiogreen: Why not directly put chrlauncher on the USB stick? chrlauncher is a portable software (no install).
But if you choose chrlauncher on C:\ and Chromium on I:\, edit the chrlauncher.ini file: Put full path where necessary (ChromiumDirectory=*** and ChromiumCommandLine= --user-data-dir=***\profile)
I should say I'm using PortableApps on that USB stick.
What can I do next?
Chromium 76.0.3809.87 (Official Build) {Stable}
Revision 111fe1e15d5ced26080a7dc239bcfe70f6c49aad-refs/branch-heads/3809@{#967}
OS Windows
Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly Optimised
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.0): October 2018 Update version 1809
- clang/llvm 10.0.0-r367199
cflags = [ "/O2", "-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly" ]
Chromium-76.0.3809.87-x64.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.87-r665002-Win64/Chromium-76.0.3809.87-x64.7z
SHA1 F63DD32CAFAAA5FF593D862B9DADFD9FD2ACBFF7
And super quick release coming in record time after Google's own Chrome release today. I am very impressed. As well all know, this is quite necessary and important since Nik's stepping back now without a build box.
Do you have any plans to provide a installer build as well as your archive builds?
The installer builds include some important Chrome/Chromium install directory ACL security details that does not come along with the archive builds.
Chromium 76.0.3809.87 (Official Build) 64-bit
Revision 111fe1e15d5ced26080a7dc239bcfe70f6c49aad-refs/branch-heads/3809@{#967}
OS Windows
Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly Optimised
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.0): October 2018 Update version 1809
- clang/llvm 10.0.0-r367199
mini_installer.exe
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.87-r665002-Win64/mini_installer.exe
SHA1 6A5FDF6465A9B859BE694B3E4A7C2A84F35DED0F
====
[Drag 'n drop Widevine folder]
@Anon4741
Will post when completed.
Oh boy, his installer for 64 bit windows is all I ever use
Is there someone else with the knowledge and time to take over?
I would consider it, but I do not have an use for the stable build, H.265 video, and/or widevine at this time.
If you do not need H.265 and widevine support, dev builds typically are plenty stable for daily use. AFAIK, I have not bothered with building Chromium stable in a long time.... years, perhaps?
Since 75.0.3770.142 (652427) • Tuesday, 16 Jul 2019 is marked "last-release" does that mean this great website will no longer make stable versions of Chromium available to those of us who are not compliere? If so, then I'm very sad. :(
Thank You
Dan Whitehead
Irving, Texas, USA
wth from Switzerland
A P.S. Will you still be compiling 32-bit versions with archive and installer? I'm still using a 32-bit system (believe it or not) due, quite frankly, to finances.
Thank you again.
Dan Whitehead
Irving, Texas, USA
Thank You.
All thanks given apply equally to Jerry, Nik, RobRich, Carl (Bromite) and Eloston & associates (Ungoogled).
@Anon4756
My Ungoogled for Android is based on Bromite with the addition of HEVC and some other Codecs. AV1 does not work. I don't know if I've broken it or that just is the case!
===========
Chromium for 64-bit Android - Friday, 02 August 2019
Chromium 76.0.3809.89 (Official Build) (64-bit)
Revision 875a9f7de5d3a7aff4cb5c5ffec2849622368289-refs/branch-heads/3809@{#973}
OS Android 64-bit
- only for Android 64
- official build
- All Bromite patches applied - AV1 playback does not work (v73 works OK)
- HEVC
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
https://github.com/macchrome/droidchrome/releases/download/v76.0.3809.89-r665002-Ungoogled-And64/arm64_ChromePublic_HEVC.apk
arm64_ChromePublic_HEVC.apk
98333C083FD52FEF976F326601A4DA96D68FD289
See the #malware section.
15 Scanners, all reporting no virus found.
i installed chromium for android (switched form another open version). I like the adblocker and everything else. Only missing setting is the dark theme. Is is only in latest for android 10 or is the flag turned off (64 bit)? (i don't talk about incognito)
@wth: First of all, I explained in the #malware section that all software without signature are suspicious by antivirus/anti-malware. To simply check if the installer (exe, dmg) or archive (7z, zip) is infected, use Jotti or VirusTotal services.
My way:
1. Get hash sum (sha1, sha256, md5...) of the file. (You will see the hash sum of any file, on this site, in each colored box)
2. Go to VirusTotal, for example
3. Get the result.
Example:
Chromium mini-installer 76.0.3809.87 (665002) • Wednesday, 31 Jul 2019
sha1: 6a5fdf6465a9b859be694b3e4a7c2a84f35ded0f
- https://www.virustotal.com/gui/file/4a9b6c81f57c498e81a65784a69d95d5b100844a59083f4d45c8069326aa6315/details
- https://virusscan.jotti.org/en-US/filescanjob/cs0a49z9km
- https://www.hybrid-analysis.com/sample/4a9b6c81f57c498e81a65784a69d95d5b100844a59083f4d45c8069326aa6315
Result: No virus found by 68 antivirus → So, it is a false positive of your antivirus.
Kaspersky Application Advisor
https://whitelisting.kaspersky.com/advisor?lang=en#search/6A5FDF6465A9B859BE694B3E4A7C2A84F35DED0F
Result: No virus found by Kaspersky → So, it is a false positive of your antivirus.
@marmaduke, @RobRich, @carl, @henrypp and all other developers:
BIG thanks for your all work, time and help!!!
@nik: You are always welcome! ;)
Chromium is fine.
Thank you for the great website and efforts building chromium!
Is it possible to use marmadukes stable build with chrlauncher?
An when yes how to do it?
Cool! Thank you very much for your effort! :)
I just noticed Marmaduke also builds an unstable x64 with all codec, no sync (and no widevine too? it would be great imo as I have no need for this). Will give this version 78.0.3866.0 a try too now, as I like using the latest Chromium builds :)
Note I updated the site. So now, chrlauncher will update to the latest stable 64-bit version (Marmaduke release).
To force it, set "ChromiumCheckPeriod=-1" in the "chrlauncher.ini" file. Then relaunch chrlauncher.
Gonna have to learn to make my own builds, as the updates from the few folks who provided them are few and far between lately.
I don't know if discussions are allowed here but I would like to know what advantage you see over chrome? So why do you use chromium instead of chrome? And do you still use the google account to sync passwords?
> what advantage you see over chrome?
Mainly, the advantage of open-source against closed-source (proprietary) software! ^^
Note I am not a fundamentalist "librist". When an appreciated proprietary software does not have an open-source equivalent, I use the proprietary software.
- https://opensource.com/article/17/8/enterprise-open-source-advantages
- https://www.gnu.org/proprietary/
> why do you use chromium instead of chrome?
I answer you by a question: why to use a limited (in the sense of, handcuffs) proprietary software which is a fork of a powerful open-source software? ;)
> use the google account to sync passwords?
Never. I use my own way for passwords. No browser sync, no password manager.
So you're not using the sync at all? Also not for bookmarks or settings etc.?
It is always interesting how others deal with the topic and what their workflows are like. :)
I have reported the "false positive" described above to Kaspersky, the investigation is not yet finished there. But it seems to be so now: The file "chrome.exe" from Chromium 76.x Win/64bit contains fixed two extensions which are obsolete and should not be used anymore. One of them contains a security hole (stealing personal data):
- Chromium PDF Viewer
- CryptoTokenExtension, CryptoToken Component Extension
These extensions are no longer included in the 78.x versions by RobRich and Marmaduke. Nevertheless, the corresponding features regarding PDF viewing and Saving Payment data and Autofill can be selected here optionally, individually, locally (without cloud) in chrome://settings/. Codecs for H.265 and .swf (without special extension) are even available by Marmaduke 78.x. Very good!
Chromium 76.0.3809.100 (Official Build)
Revision ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS Windows
Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly Optimised
Chromium-76.0.3809.100-x86.7z (32-bit)
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.100-r665002-Win64/Chromium-76.0.3809.100-x86.7z
SHA1 B3A9C7BFAF220BA2F0868047E1043B74246A9C96
mini_installer.x86.exe (32-bit)
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.100-r665002-Win64/mini_installer.x86.exe
SHA1 D82F75FA44A7FA081A5AFD137CD28E3EE2544736
Didn't pull that build because the page displayed with a reload. That regression is fixed in the most recent build (78.0.3876.0-r684597).
Chromium for 64-bit Windows - Thursday, 08 August 2019
Chromium 76.0.3809.100 (Official Build)
Revision ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS Windows
Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly Optimised - ungoogled
ungoogled-chromium-76.0.3809.100-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.100-r665002-Win64/ungoogled-chromium-76.0.3809.100-1_windows.7z
SHA1 7AC11A40F09CC9AA240FEB5A60CBB94515026E30
Ungoogled-Chromium-76.0.3809.100-Win32.7z
https://github.com/macchrome/winchrome/releases/download/v76.0.3809.100-r665002-Win64/Ungoogled-Chromium-76.0.3809.100-Win32.7z
SHA1 398715C2C05760E10E48186DD87E30D484BE6957
@wth: Thank you for your report about the Chromium issue with your antivirus.
@Jack: Which OS? Which architecture (64 or 32-bit)? Which #updater? Which Chromium version?
@Yuliya: For info, chrlauncher also uses the "Archive" file (7z or ZIP) but unzip it, install and update Chromium automatically. On the other hand, Chocolatey uses the "Installer" file (EXE)...which is also a self-extracting 7z archive! 😉
chrlauncher 2.4.3 64-bit.
I am also seeing the Chrlauncher unable to update issue, trying to come from 75.0.3770.142 (stable-codecs-sync like @Jack). It downloads the new build but then never actually goes to install it properly, even after clicking the install button. Windows 10 1903, 64bit, 32gb RAM
Other machines using the installer are working perfectly! Thanks again!
I can't find that name in my environment variables though.
Curious, are you running Wireshark? Looks like it uses a "SSLKEYLOGFILE" environment variable.
More info: https://bugs.chromium.org/p/chromium/issues/detail?id=991909
Curious, are your running Avast? Apparently it hooks "SSLKEYLOGFILE" into the Chrom(e/ium) process to setup a local HTTPS filter proxy.
https://twitter.com/ericlaw/status/1159850783862640641
https://twitter.com/WilliamJozef/status/580827680775520256
Adding "-ssl-key-log-file" to the Chrom(e/ium) command line and/.or setting the "SSLKEYLOGFILE" environment variable can trigger it, too.
sslkeylogfile isn't in my environment variables or a command line I put in, so it must be that.
Thank you so much for tracking that down Rob!! Very much appreciated! :)
As Nik's builds are now discontinued, I'd like to update for use Marmaduke's one. How can install system-wide Chromium?, and Is straightforward the update or Marmaduke version won't recognize (previous current user level) Nik install profiles?
Thanks in advance!
avast without webfilter (even disabled avast for test)
same warning about --sslkeylogfile
I tried to install as per https://martinrotter.github.io/it-programming/2016/07/17/install-chromium-system-wide-windows/ (mini_installer.exe --system-level), however, it installs to Program Files (x86). It is an issue with installer?
Chromium 76.0.3809.115 (Official Build) (64-bit)
Revision 8c9783f256a82b1c632a9c4d900f17749fe5d0b6-refs/branch-heads/3809@{#1005}
OS Android 9: ONEPLUS A6000 Build/PPw29.116-16
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9
- android_sdk_build_tools_version=27.0.3: Oreo 8.1.0+ & Pie 9
- official build
- All Bromite patches applied apart from AV1 [ Carl ]
- HEVC [ Macchrome! ]
- "No Search" option [ shamelessy lifted from Ungoogled ]
- Domain substitution, tracking and blocking [ Eloston & (the brilliant) wchen342 ]
- CFI & LTO
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
https://github.com/macchrome/droidchrome/releases/download/v76.0.3809.115-r665002-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
arm64_MonochromePublic_HEVC.apk
SHA1 BCEAF03ABEE0813E0D68D0C76C0229F327F66678
In some cases, depending on server configuration, the browser will take me to an unrelated site, or simply fail to connect, because the website doesn't use HTTPS. Is there a setting, or flag, or switch, or something that will make Chromium try HTTP in case HTTPS doesn't connect? I've searched Stack Exchange and the extension store to no avail.
Please read up on this issue. You are spreading misinformation.
Good news (maybe only for me ;-) ) in Chromium.76.0.3809.100.nosync: I'm using a utility that pops up a menu when clicking in the empty area of the menu bar and until now it wasn't working in Chromium. With this build it does! :-)
For the rest, it works perfectly as always.
Thanks.
In the meantime, the Redirector extension from the Chrome store will allow you to bypass the HTTPS "assumption" of the URL / Omni bar.
Thx!
@KZ Not sure. Check my lastest builds and let me know if it persists. TIA!
----
Windows builds updated. Win64 appears okay. Win32 performance might be (and probably is!) YMMV. I attempted to reduce some of my modified builds' usually incurred code bloat, but a couple of SunSpider runs are looking quite a bit slower than its Win64 counterpart. I might redo Win32 and release an updated build in the next day or two.
I also have a Win64 AVX2 build cooking. Not really expecting much benefit as usual, but it is an ongoing occasional experimental build anyway. Maybe tomorrow for release assuming it builds and works.
https://github.com/chocolatey-community/chocolatey-coreteampackages/blob/master/automatic/chromium/update.ps1
@tianwen2976: Nik is gone. Marmaduke will maybe can help you. You can also contact SeriousJack at https://www.reddit.com/r/Chromium/comments/c7s6f1/
For info: the support of H.265/HEVC is currently replaced by AV1 in Chromium, Firefox and all web browsers. Google and all companies prefer to support AV1. https://en.wikipedia.org/wiki/AV1
The only version that does work fine it's the old 72.0.3626.81
Why is it always a problem to get the newest version of Chromium and why dows it take so long?
Where can i find Chromium 76.0.3809.132 for Windows 64bit ?
They also have a recipe for fries, and cake that you can put jam on!
Nonce Andrew.
Sorry, but waiting nowadays more than 3 days for an updated Chromium version is totally unacceptable for such a huge community.
Since i've installed Chromium this has always been THE issue. It's a big shame.
No hard feelings but I'm going back to Vivaldi.
About the STABLE version of Chromium, @Anon4836 said perfectly that third-party developers compile their Chromium builds on their spare time, freely!
If for you "3 days for an updated Chromium version is totally unacceptable", why not use Google Chrome directly? Vivaldi has always a version behind Google Chrome.
@wth: You are free to use the web browser you need! Just for info on Android, Kiwi Browser is a good Chromium-based browser with support of Chrome extensions. Bromite is also excellent and has an ad blocker.
@ the whining ungrateful bunch: I can't believe it! "3 days... totally unacceptable" ??? All those nice people spending their time, freely, and you have the nerve to complain as if they were your employees? :-o Even if I switch daily between browsers, I consider it a blessing to have these Chromium builds available, without Google's stuff invading my computer — and with codecs.
Ok, it would be better if we had the builds in sync with Chrome releases, but "totally unacceptable" is excessive: time is the price we have to pay for it. And you won't die because you don't have the latest of the latest... ;-)
As for Vivaldi, not only does it use an older version of Chromium, but it has historical issues with some video codecs (on Mac). You might also think of Brave, but it has more issues than the builds here, in my experience.
https://www.cisecurity.org/advisory/a-vulnerability-in-google-chrome-could-allow-for-arbitrary-code-execution_2019-086/
Google Chrome is not trustworthy.
OK my words have been a little bit harsh, but it would be nice if STABLE Chromium versions would be updated much faster, I have to apologize.
I didn't know that Vivaldi lags behind the newest Chrome, that's also not good.
I would use Firefox but this browser also isn't trustworthy anymore (Pocket and some other crap integration,ads, etc), uses too much RAM (it's a big momory hog ) and has many problems with some video files.
Sadly, it's really hard to find a good browser today (than Chromium).
https://github.com/RobRich999/Chromium_Clang/releases/tag/v78.0.3896.0-r691405-win64-avx2
Built with AVX2, FMA, etc. instruction set support. Intel Haswell or later required. YMMV as usual.
--------------------
Just pushed the intended Win32 update, too. The performance issue with the previous Win32 build should be resolved now.
Thank you very much for thinking about our old 32bit P.C :)
But with your latest build there is an issue for me.
Installer or Archive.
This Prog... is not compatible with your windows version.
https://www.reddit.com/r/Chromium/comments/cz30c7/
I will kickstart a new Win32 build shortly. Thanks for the FYI.
@wth: The releases of Kiwi Browser follow Google Chrome
@Mark: It is ok. Do not worry! The most important thing is the MAJOR version of Chromium (https://www.chromium.org/developers/version-numbers). Note the latest DEVELOPMENT versions are more secure than the STABLE ones. And about your "it's really hard to find a good browser today", I complelety agree with you. Personally, my best browser should be a blend of Chromium and Firefox: ! ^^
@A: Note I cleaned your comment and also answered you at Reddit. The last STABLE Chromium build with old UI Tab changes is https://github.com/henrypp/chromium/releases/tag/v70.0.3538.110-r587811-win64 Then go to chrome://flags/#top-chrome-md and change to "Normal". Relaunch Chromium. This is the old UI before the Material-Design UI. (https://i.imgur.com/1RmZSiJ.png)
@Jerry As always, thank you for this site and your efforts. :)
https://github.com/henrypp/chromium/releases/tag/v71.0.3555.0-r591690-win64 is the latest version compatible with chrome://flags/#top-chrome-md
Also, something that i noticed a while ago is that i no longer have the "create clip" button on Twitch while using Chromium:
With other browsers (Chrome, Firefox) it work fine.
Btw, i'm not reporting here to "force" Rob to build another revision, i will just revert to previous build by him, no worries! I guess we're used to expect such problems from theses dev builds at this point :)
Thank you so much ; with 32bit : 78.0.3901.0 (692535) • Tuesday, 3 Sep 2019 .
All is Ok now ;)
I keep my fingers crossed for all who eagerly await a stable build (Win64/Win32) based on 76.0.3809.132
A very strong "thank you" to Jerry, Nik, Marmaduke and Rob for all their commitment and dedication they're showing
towards providing all these Chromium builds.
Yeah, 3901 is very buggy. I also returned to 3896.
Since your API seem to work again for me here is my updated page that use it :
https://www.murielfrenchcouture.fr/Chromium
Note that the following URL are valid BUT are redirection to the above URL :
https://www.murielfrenchcouture.fr/Chromium.php
https://www.murielfrenchcouture.fr/chromium.php
https://www.murielfrenchcouture.fr/autres/Chromium.php
https://www.murielfrenchcouture.fr/autres/chromium.php
Let me know if there is something wrong with this page or if you want that I shut it down.
Regards !
[EDIT 05 sept 2019 by Jerry: URLs corrected]
I can't watch on waipu.tv some of the TV stations anymore, i get a "DRM error message" instead:
The same for the Livestream on n-tv.de
Now the stream stays black and no sound either:
I believe that the WindVine folder can also be located within the Chromium profile too. It can be used within the program directory or profile from my understanding.
I'm using the "Portable" Stable version.
Last version, it all worked, since the newest updated version not anymore.
The "Archive" version has the same problem with DRM content, it doesn't work either.
So, something is wrong with this current version: 76.0.3809.132 (665002) • Wednesday, 4 Sep 2019 • Windows 64bit
---------------------
I just wanted to add that the "Chromium ungoogled version" (64bit) has no problems with these DRM streams, it plays them just fine.
Only the normal Chromium version (64bit) (which I'm always using) has these issues. That's very strange, so something isn't right since the last update.
any guess how to install it via mini installer?
https://chromium.googlesource.com/chromium/src/+log/76.0.3809.132..77.0.3865.75?pretty=fuller&n=10000
Time for new build! :)
It works now perfectly - also with extensions (Ublock Origin etc.).
Very good job!
Hello.
When you have time.
Can you compile a Ungoogled v78 for Android ?
Thank you.
And thanks for the update Ungoogled Windows.
Sorry for the typo.@ Marmaduke
Ungoogled v77 for Android.
If possible...
> missing text in latest build
Disabling hardware acceleration in settings has resolved this issue for me
- the DRM Live-Streams on n-tv.de and waipu.tv are working again!
(with ungoogled Chromium version it already was working all the time).
Thanks and very good job Marmaduke.
Thanks for the very stable sync dev versions you've provided for Windows 64-bit! ((78.0.3866.0 (681261) • Sunday, 28 Jul 2019))
Out of curiosity, are you still pushing new dev updates here or are you taking a little break?
I only ask as I was sorry to see Nik leave the compiling of dev builds. I'm impressed with your work on the dev builds so far!
Hope you decide to keep compiling! :)
Can you please check the mini installer for the latest Chromium you have built to make sure it is for version 77.0.3865.75 and not 76.0.3809.132? It is probably my fault, but I downloaded the mini_installer exe and it appears to be v76.
Thanks for everything you do!
@Mark: Previously, I used the wrong configuration, and failed to check for Widevine compatibility. Ungoogled is my main stable build. The conventional stable build is a temporary solution until Nik resumes normal service.
@Dustyn: In order to mitigate changes to the code-base of future stable builds the respective dev has to be (contemporarily) compiled. Dev builds are done time permitting.
@Anon4877: A right click "details" suggests that mini_installer.exe is v77.0.3865.75. The file 76.0.3809.132.manifest can be deleted, and is a remnant of the previous build.
Hello.
Ok , thank you.
Just a suggestion when avalaible new chromium base for Android.
If possible to uptade the user-agent.
To 77 , or latest chrome user-agent for Android.
Like that web site will not say obsolete browser.
Thanks. Best regards...
Maybe I'm just asking stupid things here, but what are the steps to get your build of Ungoogled Chromium on 64-bit Windows 10 systemwide? And the other question goes for the extensions, as I got some trouble installing them.
Cheers
Spoofing the user agent is an integral part of the Bromite browser: https://github.com/bromite/bromite/blob/master/build/patches/User-Agent-anonymize.patch
The Bromite browser is easy to configure and compile. Use git to apply the (binary) patches.
@Private Lives Matter
Basically, the generic ungoogled patches are at: https://github.com/Eloston/ungoogled-chromium
The bespoke Windows patches are at: https://github.com/ungoogled-software/ungoogled-chromium-windows
The Windows' patches are mostly out of date and many of them are not applicable. I manually patch and by "trial and error" see which patches are actually required.
Further, the "safe bowser" patches are obsolete and I do not apply them: Carl - the main guy at Bromite - is working on using Chromium's internal adblocker, which relies on elements of safe-browser, as a general adblocker that could easily be incorporated into ungoogled; therefore am not too concerned about the safe-browser patches not being applied.
My build process is bespoked and basically follows Eloston's procedure.
Eloston considers the removal of safe browsing to be an integral part of ungoogled. I'm not too concerned: safe browsing is easy to eliminate; but its tight integration with chrome cleaner - which is particular to Windows - is not. I disable the safe browsing and chrome cleaner via build policies.
https://github.com/NeverDecaf/chromium-web-store
====
Chromium for 64-bit Android - Monday, 16 September 2019
Chromium 77.0.3865.81 (Official Build) (64-bit)
Revision 1a16d01ac4fbb26c813db1b330fb5d382712cc3b-refs/branch-heads/3865@{#796}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9
- official build
- All Bromite patches applied (Apart from AV1 patch.)
- HEVC
- "No Search" option
- Domain substitution, tracking and blocking
- CFI & LTO
- 64-bit Webview and processes
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
arm64_MonochromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v77.0.3865.81-r681094-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
SHA1 91F51DD4355F33938EC8DCD3BB6AC276CD7ADCDA
I have a 32-core build box, so I suppose "whatever" for my builds. However, those locally building on quad-cores or similar mainstream consumer systems could be looking at significantly increased build times without Jumbo support. YMMV, as usual.
BTW, hopefully new builds later today.
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/NqI5UDSJW2g
That explains a build failure that I've been having recently. Rather than turn off jumbo, I amended the code. I only have 24-cores and a non jumbo-build is unacceptable.
I know that Google has open-sourced Goma, and had a feeling that jumbo's days were numbered. That's is why I've been experimenting with ccache and sccache: both are unacceptable for my needs.
The way forward for Windows builds is distributed cross-compilation:
https://blogs.igalia.com/hferreiro/2019/01/cross-compiling-chromium-for-windows/
The Chromium Authors' time would be better spent developing a macOS ld64 linker that is compatible with clang-10 and LTO.
Great. Thank you for Ungoogled Android 64bit.
I can't compile.
Don't have Linux OS.
Thank you very much again...
:)
Compiler caching and ThinLTO caching are unlikely to help unless you are doing minimally changes or otherwise closely versioned iterative builds. About the same end results with incremental building as well.
----------------
If not already, definitely look into changing the ThinLTO jobs limit to improve link-time codegen parallelism.
D:\depot_tools\chromium\src\build\config\compiler\BUILD.gn
Depending upon platform and linker, the current project defaults are:
/opt:lldltojobs=8
-Wl, --thinlto-jobs=8
-Wl,-plugin-opt,jobs=8
Also if not already, look into trying the "enable_precompiled_headers = true" build argument, too.
compile - probably race conditions. On the Mac build, I've always used maximum cores for building without an issue.
Snapshots, I think, are only an issue on initial launch. Nothing beats a Windows native build.
« […] Spoofing the user agent is an integral part of the Bromite browser […] »
Real version ➜ 77.0.3865.81
Spoofing version ➜ 74.0.3729.157, Galaxy S9, Android 8.0.0
Time for new builds! :)
Any chance it will be enabled for reduced memory usage? (Along with compiling in -Os ?)
>>BTW, hopefully new builds later today.
I'm very much looking forward to that. ;)
I've poked around the console, I get different errors depending on how Chromium is feeling that day, I guess. Today, it's:
"Illegal invocation: Function must be called on an object of type StorageArea" on content.js. In Incognito mode (all extensions disabled) I get:
GET chrome-extension://invalid/ net::ERR_BLOCKED_BY_CLIENT on remote.js.
I have searched, and searched, high and low for a possible solution to this, and gotten nowhere. I've asked the Chrome subreddit, and searched Stack Exchange. I'm lost. Halp.
(Chromium 77 on macOS Sierra 10.12.6. With or without extensions, doesn't matter. If this is the wrong place to look for support, I apologize, and the admins can delete this post as they wish.)
I don't mind proper issues. I'll take a look it, and report back.
-------------------------
10.12.6
Tested 77.0.3865.90 ungoogled: sdk 10.14 no problems and a dev v79 built under Catalina, using GM seed xcode 11 and sdk 10.14 no problem. Test consisted of watching 1080p Nicki Minaj videos on YouTube!; so. it was avery robust!
The only suggestion I can make is to do a (fresh) portable install.
Interesting... out of curiosity, this was the one I was trying to watch, and it still seems to be broken: https://www.youtube.com/watch?v=jkKL7uJd2no. (I'm aware it's...ridiculous, but I promise this happens on legitimate learning about...plants and stuff?)
Hopefully that one will fail for you? If not, I don sackcloth and throw ashes onto my head.
Now as the "hours" mentioned above, that would be a byproduct of removing Jumbo build support.
I build locally on a 32-core Opteron system with 64GB memory, enterprise-class SSDs, etc. It is somewhat outdated, but it is still far above a typical consumer-class system and works fine for building Chromium with jumbo support. I am not an active project developer, but I have contributed a few bug reports and comments over the years, including some LLVM ToT-related issues.
I know it is not the case as hard decisions managing a project the size of Chromium are made all the time, but I almost feel like the project is telling individual enthusiasts (like me), small project developers, and possibly even thrid-party SMB-size developers using the Chromium codebase to deal with it or go away. Could I spend the money the offset the issue? Quite possibly yes, but I am not inclined to toss thousands of dollars of my own money at a project backed by multiple, multi-billion-dollar corporations when a working off-the-shelf solution for locally building the projects' like ~20GB of complex source code already exists.
I suppose the real annoyance for people like me is it looks like Opera is (was?) prepared to continue supporting Jumbo for the project, though there dev(s) did not seem to get too far after the decision was made, either.
I expect my Windows releases to continue since setting up even a modified build only takes a few minutes of effort like every couple of weeks. it is just *highly annoying* my local optimized build times will now be measured in hours instead of minutes. It is like going back to FullLTO build times, but without the actual benefit of full link time optimization(s).
Going back a few posts, we had some comments about Linux-to-Windows cross builds. It looks like V8 devs have snapshot and embedded builtins features now working for the process. I have not bothered doing a Linux-to-Windows build, but I have seen comments about Linux being faster for building Windows releases.
My local issue is no real desire to migrate my build box to Linux. I even used a virtualized environment back when doing the occasional Debian/Ubuntu x64 build. I might look into seeing if a dual boot environment is worth the effort. I suppose one could try tossing the cross build process at WSL2 as well, though as I often say, that likely is a huge YMMV.
Spidey functions correctly. I recommend youtube-dl and ffmpeg. Could be a router problem as well.
@RobRich
Building Chromium in MacOS with a Linux icecc cluster works quite well. But, polly and LTO does not work. I'm going to give a macOS-to-Windows (distributed) build a try.
As to my latest Win64 internal build, the ongoing linker error is present. Hmmm.
LINK initialexe/chrome.exe
FAILED: initialexe/chrome.exe
LLVM ERROR: assembler label '.LBB0_-1' can not be undefined
https://cs.chromium.org/chromium/src/build/config/win/BUILD.gn hit the history button
Threadrippers are nice but they don't play nicely with macOS, and I don't particularly like the architecture. In Homage to Greta, I think old enterprise servers are the way forward.
Rob, as always, totally understand your perspective on the situation and appreciate the work you have done and continue to do. I know that you've been hesitant if not against the idea before of having some sort of Patreon or Donation option set up, but I feel that it would be relatively successful and would make the overall process hopefully less stressful or tedious. Your time and effort is valuable, and it just seems that the writing may be on the wall for various builds of this project if other aspects aren't looked at. Anything to keep legitimate browser projects alive in this day and age is a cause worth supporting, IMO.
Just my two and a half cents!
Chromium 79.0.3920.0 (Official Build) (64-bit)
Revision 7484bf0aa5482eb7398490f0df9bbc1dbeb79502-refs/heads/master@{#698759}
OS Windows
-
- macOS Mojave 10.14.6 (icecc linux cluster) cross-compiled
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.3): October 2018 Update version 1809
- clang/llvm 8.0.1
- v8_use_snapshot = false
No Sync - No Widevine
Chrome-bin-79.0.3920.0.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v79.0.3920.0-r698759-Win64/Chrome-bin-79.0.3920.0.7z
SHA1 A586182875037C107768FAEA5F8D03F0936190D3
===
Purely proof of concept. A negligible amount of the processing was done by the Icecc server.
=====
=====
@Anon4905
77.0.3865.90 almost certainly contains critical vulnerabilities. Probably, next week.
While looking through recent bug reports, there might have a way to get PGO working without the ridiculous file sizes.
---------------------------
Checked the builds. A relatively baseline build completed. Looking like something in my own modified config.
---------------------------
Updated Win64 build pushed. Win32 to build, which hopefully should be ready later today.
Expect possible performance differences! I was able to do the Win64 build at O3 for both clang and lto codegen, but to get a working build, I dropped many other LLVM-related options I typically configure. Also it looks like I probably did not modify LLVM to enable AVX support for the default x86-64 target, so it is likely a SSE2 build instead. I will revisit Win64 after getting an updated Win32 build pushed.
---------------------------
Builders do not get too excited, as it currently is just checking out the source. I *suspect* the build process should work as intended, but I doubt Chromium devs are targeting WSL for cross building. ;) I seriously doubt it will build quicker, but it is something different to give a try in the background.
BTW, that is WSL1 for now as I am running the current Win10 release build instead of a preview build with WSL2 support.
---------------------------
^Forgot to manually edit .gclient to set Win support. o.0 Oh well. Maybe later. It was only running in the background on my notebook anyway.
---------------------------
Updated Win32 build pushed. Please let me know if it gets really "squirrely" or whatever, as I enabled C++17 support for building. Been awhile since trying that, and building to mini_installer.exe appears generally okay after adding -Wno-microsoft-exception-spec to the project build warning parameters.
Tooltips broken and not showing
Update Google Chrome Browser to Patch New Critical Security Flaws
Started rolling out to users worldwide this Wednesday, the Chrome 77.0.3865.90 version contains security patches for 1 critical and 3 high-risk security vulnerabilities, the most severe of which could allow remote hackers to take control of an affected system.
Wondering if you can create win64 ungoogled based on 77.0.3865.90 or later ASAP.
Tried same download with Opera 63.0.3368.94- 64 bit: it works !!
Why download on Chromium do not works ? How solve this ?
FYI. Performance could be down a little. Given recent local build issues, I am more focused on stability than outright performance right now. The builds still are optimized higher than stock; just not at my typical level. Hoping I can start adding back more tweaks in upcoming builds.
https://support.google.com/chrome/thread/15235262
No, it most likely wouldn't. The other thing is, at the time you compile finished, there will be new version already :)
do you mean no more 32bit builds (just noticed your 64-bit new build)?
Subjectively, I feel so to: built without lto, polly or jumbo.
@Anon4925.
At the momemt, I'm limiting my builds to 64 bit ungoogled. It's taking 3x longer to do a non-polly, non-lto and non-jumbo build. The problem is the Windows build, there is no way to do a distributed build. I thought that a cross-compiled Windows distrubuted build would be possible, bit icecc is not capable of doing that.
perfectly understandable, any builds you produce are greatly appreciated by the community! and to the naysayers demanding releases asap i say be damned! :D thanks!
Extension can be found here => https://github.com/NeverDecaf/chromium-web-store
Please, can you consider only polly versions for the final releases for each branch?
I thought about going with a quad-socket Xeon 40c/80t system, but that would be with dated Westmere-EX chips, which do not even support AVX and various other later instructions. That feels like going too far backwards even from the perspective of my now dated 32c Opteron Piledriver system.
The "solution" for me probably would be a 64c or even 128c EYPC system. That said, just like doing a realistically viable distributed Goma environment, I am not spending that type of money to build a browser. o.0
I eventually should get around to a build box upgrade. I might look into a Ryzen 9 3950X or Threadripper build.... like next year if/when prices stabilize. Until then it will be slow building on my 32c Opteron system.
-----------------------------
Forced a "fix" to my ongoing chrome.exe linker issue when using certain optimizations by outright disabling the error. For our purposes, big deal is an assembler label can not be undefined IMO.
LLVM source file:
https://pastebin.com/eqNmSnm4
-----------------------------
Updated Win64 build pushed. More optimizations restored. I should be back on track for optimizations within the next build cycle or so.
Win32 build cooking currently.
Polly, thinLTO version, do a comparison and convince me:
https://github.com/macchrome/winchrome/releases/download/v77.0.3865.90-r681094-Win64/chromium-77.0.3865.90-polly.7z
@RobRich
Corporate greenwashing arrogance aside. What I object to is the inefficient use of energy resources.
The bigger issue is we are running Polly too early in the pipeline with ThinLTO. It ran early back when introduced, which is what I am forcing it do now with ThinLTO, but it should be running much later in the pipeline right before vectorization during LTO codegen. The LLD linker currently does not support invoking Polly, thus we are stuck for now. It can be run after the loop optimizer, but that is not recommended for most purposes by Polly project devs. There is a possible solution in the works. I should get around to checking the progress.
Otherwise, until something changes, putting Polly back to its late position before the vectorizer passes means opting for FullLTO if using link-time codegen. Then again, we still have the LLD issue. We can move Polly to late during the Clang codegen passes, but Polly is still not being run during LTO codegen. Enabling FullLTO also could push a build into many hours, as its LTO codegen is single threaded. o.0
It could change at any moment, but anyway, here is my current Polly with ThinLTO config:
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
# "-Xclang", "-Rpass-analysis=polly",
Remove # to see Polly working if desired.
Expect breakage IMO, too. See my previous post(s) if the assembler label issue happens during linking.
Another aspect are the build optimization levels, particularly for Win64 where code size typically is not as dramatic of an issue. All build targets should be changed to -O3 ( "-Xclang", "-O3", on Windows) when building with Polly. LTO codegen ideally should be at O3 as well, plus put the LTO instruction import limit back to 100.
There also is the issue of instruction set support. I enable AVX support for my typical Win64 builds by modifying the generic x86-64 model in LLVM, thus hopefully providing the vectorizer passes with more flexibility. Polly subsequently leans heavily on vectorization, so again, we have a YMMV situation depending upon the build target architecture.
Summation for the TLDR crowd? There is not really an "one size fits all" approach to "ideal" optimizations for a software project the size of Chromium, especially with Polly involved. It is more a matter of compromises to find some type of middle-ground where hopefully the positives outweigh the regressions for most end-users.
You also can manually grab it for Win32/64 from Google's own component download server though I suspect the current.txt version indicator file is way out of date. I do not know the current stable version, either, so drop a Google search for more info if interested.
Note, I suspect either technique probably is not strictly license compatible with Chromium, as the above components were instead built for Chrome and its particular licensing.
The MS Chromium Edge public source code build is quite informative.
----------------
BTW, I have moved Polly into the late position and enabled autovec for Clang passes. ThinLTO by default does autovec only during LTO codegen.
Instead I changed pass management to be somewhat similar to FullLTO. Now Clang does it own codegen with Polly and autovec enabled. Then LLD does its own multi-threaded LTO codegen with autovec enabled.
I expect there will be issues to resolve. More FYI on the topic later assuming if/when the idea results out a working Chromium build.
I've created a little update notification extension because none of the updater I've found seemed to work. You just select the platform and tag you want to track and it will show a badge when it detects a new Chromium version. It works by crawling this website every 3 - 3.5h. I tried to contact Jerry and ask for permission, but he never replied. I hope this is ok.
It can optionally also track updates for all of your installed extensions (via GitHub or `update_url` of the manifest) and offer 1-click updates if possible.
You can find it here:
https://github.com/kkkrist/chromium-notifier
Let me know what you think!
–Christian
Tested on Core 2 Duo E7300 and Windows 8.1
https://en.wikipedia.org/wiki/Advanced_Vector_Extensions
@kkkrist: Interesting extension. Bravo! Contacted by email. 👍
@RobRich and @marmaduke: I cleaned your latest comments for a better reading! ;)
I cross my fingers for your build system! ^^ Thanks for your effort. 👍
Did a couple of quick runs of Basemark Web 3.0, and my build box picked up 80 points compared to my currently listed Win64 build. I will need to run more testing to actually verify. Perhaps tomorrow if I feel like it.
For the adventurous types:
https://github.com/RobRich999/Chromium_Misc/releases/tag/v79.0.3929.0-r701220-win64
Default Editor is now Marmaduke and Ungoogled version is added.
Download powershell/batch script here:
https://github.com/mkorthof/chrupd
( sorry if double post, it didnt seem to appear the first time )
Are you doing anything special (except excluding safe browsing patches) for your ungoogled-chromium builds? I ask because I was expecting swiftshader to work with your latest build due to it being enabled again in the repository (Eloston's). See:
https://github.com/Eloston/ungoogled-chromium/commit/7fc5d1a8d064c95f9895bf4ba8f6e1dddb028bc8
chrome://gpu tells me the gpu process is crashed, and https://get.webgl.org/ reports unavailable or disabled. Stable Chrome reports and displays webgl content fine.
Cheers
I've always built ungoogled with Swiftshader. I've just tested Swiftshader and it functions correctly:
https://github.com/macchrome/winchrome/releases/download/v77.0.3865.90-r681094-Win64/GPU.7z
Perhaps try using an older version of d3dcompiler_47.dll
Ahh ok, apologies then, it must be on my end, gonna investigate further. I notice the d3dcompiler_47.dll is a newer version in the working Chrome Stable build but no chance to restart Chromium yet to see. Thanks for your help.
Have you ever considered announcing your builds to the ungoogled-chromium download page (https://ungoogled-software.github.io/ungoogled-chromium-binaries/) or do you not want the extra attention?
Cheers.
I made basic test on some of my machines and I would like to share my current findings.
In the test I tried to compare the 77.0.3865.90 polly against the 77.0.3865.90 non-polly version. The machines are with Windows 10 1809, like the CPU’s are different but all are from Intel. The GPU are different.
I used the same profile for each system, like I only switched between the polly and non-polly version for the purpose of the test.
I made the test using the benchmark at https://browserbench.org/Speedometer2.0/ which measure the responsiveness of the browser by timing simulated user action interactions.
The results on my specific systems are pretty much identical. The polly version is quicker with about 6-10% against the non-polly version. I tried to repeat the test on each machine and the results are almost the same. Every time the scores of the polly version are better than the scores of the non-polly version.
To determine which version is better I think they should be made more tests with different system build configurations.
My System:
Dell Studio 1537 Laptop:
Windows 7 64bit , Intel Core 2 Duo T6400 , 4GB Ram, ATI Mobility Radeon HD 3450 , 1280x800
Results (higher is better):
358, 440, 436, 437, 436, 430, 437, 440 -----> (non polly)
328, 432, 420, 413, 403, 428, 441, 423 -----> (polly)
So, "non polly" was clearly faster.
PU Type Mobile QuadCore Intel Core i7-2760QM, 2400 MHz (Sandybridge)
Three iterations:
https://browserbench.org/Speedometer2.0/
Polly
67.8 66.8 67.2
± 0.92 ± 0.84 ± 1.0
Non-Polly
62.6 62.5 61.8
± 0.64 ± 0.66 ± 0.70
http://www.speed-battle.de/speedtest_d.php
Polly
122.27 736.36 35.31 893.94 <
124.12 762.05 37.24 923.41 <
120.47 744.73 38.64 903.84 <
Non-Polly
124.12 720.18 34.71 879.01 <
120.47 720.18 34.13 874.78 <
120.47 744.73 34.13 899.33 <
========
RobRich said that polly was biased towards polly. Subjectively, I feel no difference.
Maybe for you is better to use the non-polly version or even better is to have 32 bits browser no argumenths here but based on your system specifation, I cannon take this information in considiration. This system is too old and weak. Actually, that's system is from the time when we have the initial release of Chrome.
@marmaduke,
I don't feel difference as well is general browsing but that's a benchmark. Higher number should mean something. The browser will be more capably under load. I cannot say what's the cooking time of polly version vs non-polly but we have clear winner based on achive results. If that time is more consuming, make sense if only the last version of the branch is polly.
More important from the question polly or non polly is the stability of the browser. If there is no stability, please stick to the regular build.
mini_installer.exe still is 77.0.3865.75 (681094) • Friday, 13 Sep 2019
What files need to be copied from previous installation? Backing up both my application and user data folders, I can't find anything missing that should be preventing widevine from working (using Marmaduke's latest sync build)
C:\Users\*username*\AppData\Local\Google\Chrome\User Data
Copy the WidevineCdm directory and its underlying files to:
C:\Users\*username*\AppData\Local\Chromium\User Data
Alternatively, you instead even could set a directory junction or symbolic link.
----------------
BTW, I noticed you are using a MD's sync build, which I assume also means it probably includes the version of Widevine available to be built with Chromium as well. If a previous Chromium build's Widevine worked, obtain the older version, extract the WidevineCDM directory, and replace your current WidevineCDM with it.
----------------
You might also first try the component updater before doing any of the above, but I am not sure it will update Widevine for a Chromium build. Again, it has been a long time since I have dealt with Widevine issues.
chrome://components/
----------------
BTW, Widevine aside, it probably is a good idea to occasionally run the component updater anyway if one is using Chromium "stable" builds, as various components can be and often area updated between stable releases.
I do not intend to debug the actual underlying issue, so I am simply dropping argpromotion from LLVM legacy pass manager. It is only run at O3 anyway, and I doubt it will make much performance difference for our purposes anyway.
By simply disabling it I still can get the opportunities offered by the other remaining O3-gated passes, too.
Devs apparently want to compress name data for debuging, PGO, etc. I not care much about debug building locally, but I would be interested in dramatically decreasing some of the huge file sizes incurred with PGO building.
Assuming it *just works* without (much) additional code plumbing in Chromium, I will try to take a further look into the concept in the upcoming days/weeks to perhaps get PGO back into my public builds.
https://github.com/kkkrist/chromium-notifier
–Christian"
Nice!
Any ideas?
@marmaduke Is there going to be an update to the installer for Chromium 64? I noticed the portable has been updated but the other hasn't.
chrome://settings/?search=Allow+Chromium+sign-in
When trying to open a PDF in a separate tab I get the usual layout (with the three round buttons in the lower right corner and so on) but, after a few seconds, a "couldn't load plugin" message appears.
Maybe some settings have to be changed?
Typically I build LLVM with VS2019 but with various platform-specific tweaks that LLVM devs likely do not test against. I rolled back to the default optimizations used for release builds.
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang;lld;polly;compiler-rt -G "Ninja" ..\llvm\llvm
Appears some previously intermittent issues building Chromium at O3 with Polly and LTO have been resolved as a result. Should know some, as I roll even more tweaks back into the Chromium build configuration.
----------------
Updated Win32 build pushed.
The browser often closes without messages and errors.
All fine with 79.0.3929.0.
I installed 79.0.3939.0, from the er...peach-colored link? And that has solved the otherwise-intractable YouTube problem of crashing tabs. (I enabled error logging and replicated a tab crash from .90, but I'm still...trying to understand it.) I also tried 78.0.3901.0, which also crashes. Vimeo doesn't work on the new 79.0.3939.0, but that could be because it was complied without all the available codecs?
I'll keep researching and report back.
Sorry to bother you again, regarding your results from my query about swiftshader (https://chromium.woolyss.com/?all=1#comment-4945), I looked at your chrome://gpu post and it does not mention swiftshader..the swiftshader renderer is only used if normal hw acceleration is not available, it looks like your hw was supported hence no mention on the gpu page.
It was only recently enabled on Eloston's builds so can you please check your flags.gn does not contain "enable_swiftshader=false" on your next compile?
For reference here are a few lines from my chrome://gpu page on Chrome Stable (WORKING swiftshader) (not posting all so as not to spam, let me know if you would like full result):
GPU0 VENDOR = 0x8086 [Google Inc.], DEVICE= 0x2772 [Google SwiftShader] *ACTIVE*
GL_RENDERER Google SwiftShader
GL_VERSION OpenGL ES 3.0 SwiftShader 4.1.0.7
Window system binding version 1.4 SwiftShader 4.1.0.7
And here are some results from Ungoogled-Chromium-77.0.3865.75-Win32.7z (swiftshader NOT WORKING):
GPU process was unable to boot: GPU access is disabled due to frequent crashes.
GPU0 VENDOR = 0x0000, DEVICE= 0x0000
EGL Driver message (Critical) eglInitialize: No available renderers.
eglInitialize D3D9 failed with error EGL_NOT_INITIALIZED
GLSurfaceEGL::InitializeOneOff failed.
GpuProcessHost: The GPU process crashed!
Thanks as always.
@Anon4975
I'ii be pushing some new builds in the next few days: I'll take your problems/concerns into consideration.
I hope there was nothing to suggest I am anything other than grateful for your extremely hard work, because I am. I'm fairly tech-savvy, but we're getting to the real innards of software in a way that I'm unfamiliar with. That said, if it helps, here are (I think) the relevant entries from the log file, as best as I can tell.
[2449:775:1006/121124.360731:ERROR:gles2_cmd_decoder.cc(18553)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : DoEndSharedImageAccessCHROMIUM: bound texture is not a shared image
[2447:775:1006/121125.650175:VERBOSE1:device_event_log_impl.cc(164)] [12:11:25.650] Bluetooth: EVENT: bluetooth_api.cc:97 BluetoothAPI: Shutdown
[2447:775:1006/121125.656166:VERBOSE1:account_reconcilor.cc(266)] AccountReconcilor::Shutdown
This comes after several lines of "ERROR:gles2_cmd_decoder.cc [blah blah] bound texture is not a shared image", and right after the random Bluetooth event is when the tab seems to crash for good.
I have no idea if any of this is relevant, so if it isn't, I can keep trying to look for what might be.
Hello.
Thank you ; for the latest build.
But i have an issue.
Archive or Intaller 32bit.
" The prog you try to use is not compatible with your version of windows ; etc etc "
Regards...
As to Chromium optimizations, I have moved many back into my current Win64 build, especially with builds now taking quite awhile anyway since Chromium is discontining jumbo support. For example, here is my current tweaked Polly config for ThinLTO builds:
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-analysis-computeout=80000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-max-ops=10000000",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
# "-Xclang", "-Rpass-analysis=polly",
Looks like I missed register tiling. I will try to get it back in there for my next build cycle.
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-analysis-computeout=8000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-max-ops=10000000",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
# "-Xclang", "-Rpass-analysis=polly",
Courtesy of Albert Tang https://github.com/tangalbert919 and Eloston https://github.com/eloston
I present Windows ungoogled-chromium-tinfoil: the full implementation of ungoogled chromium (sans safe-browsing). Ungoogled Chromium is what Chromium should be. I could not care less about Google's Chrome.
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Polly Optimised - Ungoogled - Tinfoil (no safe-browser)
Ungoogled-Chromium-tinfoil-77.0.3865.120-win64.7z
https://github.com/macchrome/winchrome/releases/download/v77.0.3865.120-r681094-Win64/Ungoogled-Chromium-tinfoil-77.0.3865.120-win64.7z
SHA1 350CFD62BB95913D2FE31AB881FD49B0112889DB
Thanks very much for the new builds. Swiftshader is present and active on both 32-bit chromium and ungoogled-chromium builds! I can't test 64-bit but assume it is the same case. Good job getting a build to work without dreaded safe browser too.
uBlock Origin dev build "REJECTED" from Chrome Web Store https://github.com/uBlockOrigin/uBlock-issues/issues/745
For me personally, I will not be able to continue to use Chromium without uBlock.
@RobRich. My pleasure. Thank you. Now all is OK.
@Marmaduke. Thank you ; for the latest 32bit build.
Tinfoil users will have to sideload.
windows-fix-building-without-safebrowsing.patch...
- const bool is_extension_download =
- download_crx_util::IsExtensionDownload(*download_);
-
- //
https://github.com/uBlockOrigin/uBlock-issues/issues/745#issuecomment-539970216
When I try to do it in the settings, Chromium doesn't appear as an option in the list.
@marmaduke and @RobRich: BIG thanks for your builds! ;)
I casually noticed that my Portable 79.0.3917.0 (64-bit) seems unable to open PDF files inside the browser.
When trying to open a PDF in a separate tab I get the usual layout (with the three round buttons in the lower right corner and so on) but, after a few seconds, a "couldn't load plugin" message appears.
Maybe something's wrong with my system?
The extension ID for the PDF viewer is: mhjfbmdgcfjbbpaeojofohoefgiehjai
Obviously it is missing: is it in the regular Chromium Authors' respective build? Do some research and let me know the result. Development builds by their nature are not expected to be stable: I only build them to mitigate changes to future stable builds. If there is a problem report it to the Chromium Authors.
Do some thinking and exhaust all the possibilities.
I'm afraid I'm not skilled enough to perform the search you asked (or did not understand where I should search).
I searched for that ID inside the Chromium (portable) directory and, as expected, I did not find it; however when I searched the directory of the previous build (78.0.3866.0), where the PDF viewer was present and working, I did not find it as well. So maybe it should be elsewhere.
I never had stability issues with your builds, this one (79.0.3917.0) included; the only "problem", this time, lays in the missing PDF viewer.
I wrote here just to be sure that the reason did not lay in my system.
If the extension is expected to be missing in this particular build, then I have the answer I needed. I'll wait for the next one, meanwhile viewing PDF otherwise; it's not such a big sacrifice, after all. :]
Thanks for your kind answer.
Will there be ungogled Chromium too for developer buils one day? :)
Also an updated Win64 build with support for AVX2, FMA, etc. AMD Excavator, Intel Haswell, or later required.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v79.0.3943.0-r705874-win64-avx2
----------------
Current Polly config for Win64:
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-analysis-computeout=8000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-optree-max-ops=10000000",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
# "-Xclang", "-Rpass-analysis=polly",
----------------
Current Polly config for Win32:
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-analysis-computeout=8000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-delicm-overapproximate-writes",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
# "-mllvm", "-polly-optree-max-ops=10000000",
"-mllvm", "-polly-optree-normalize-phi",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
# "-Xclang", "-Rpass-analysis=polly",
I work in the Chromium team at Arm, and recently we've been doing some work on Windows-on-Arm (WoA) - fixing various Chromium issues, testing, etc, with the result that Chromium now builds and runs out-of-the-box for WoA.
This means that users get a Chromium browser that is faster and more stable (because it's not emulated, as is currently the case). We'd like to make native WoA builds more widely available - is this something that you'd be interested in helping distribute?
Admittedly I do not have any native WoA systems at this time, but nonetheless, thanks for the contributions to the Chromium project.
Thanks, I emailed Jerry a few weeks ago but didn't get a reply. I'll ping him again in case it disappeared into a spam folder or something.
Cheers, Dave
Chromium for 32-bit Windows - Friday, 18 October 2019
Chromium 80.0.3946.0 (Official Build) - "Dev"
Revision 855b9ddd4e7c59e92f9fb30f0cf70586e4da934e-refs/heads/master@{#707335}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.3): October 2018 Update version 1809
- clang/llvm 10.0.0-r367199
- ThinLTO
- Polly
- WebRTC
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
Sync - WebRTC - Widevine - All Codecs
Chrome-bin-sync-x86-80.0.3946.0.7z (32-bit)
https://github.com/macchrome/chromium/releases/download/v80.0.3946.0-r707335-Win64/Chrome-bin-sync-x86-80.0.3946.0.7z
SHA1 1C6CEF7A766A0A47015BDFEA9A015DE179CC2E4A
===============
macOS 10.15 [19a602], SDK 10.15, Xcode 11.1 - Saturday, 19 October 2019
Chromium.app.ungoogled-sdk-10.15-77.0.3865.120.zip
https://github.com/macchrome/macstable/releases/download/v77.0.3865.120-r681094-Ungoogled-macOS/Chromium.app.ungoogled-sdk-10.15-77.0.3865.120.zip
SHA1 377E240CC16FD3462CC1C84F665F1B46C513B2E3
You will get a .crx file. You need to go in Chromium extension page and enable "development mode". The just drag and drop crx file into chromium, extension will get installed. After extension will notice you, when there are updates for your extensions available. You will understand quickly how it works :)
---------------------------------
The regression happened yesterday. Thankfully LLVM devs caught and fixed it this evening. :)
LLVM was trying to schedule a SSE3 instruction during codegen despite its generic x86 target being limited to SSE2. Explains why my x86-64 AVX build was not affected, since AVX support implies SSE3 support as well.
Hopefully should have an updated Win32 build tonight or tomorrow.
I installed version 80.0.3947.0, and chromium.exe is now a 32 bit executable, it was a 64 bit executable before.
Regards,
Michel Terrrisse
Are you planning on posting Windows ARM64 builds soon?
Thank you,
Hernan
If you mean the chrome-win32 directory, that is a holdover from how Chromium used to be distributed.
I am away from a Windows system right now, but you can check the browser's internal. about:version page to verify the build. Let me know. Thanks.
Chromium 80.0.3947.0 (Build de développement) (32 bits)
Révision 4e2d8a75dd1fffe19d06a7cc2399d055353bca4d-refs/heads/master@{#707682}
Regards,
Michel Terrisse
Chromium 80.0.3948.0 (Build de développement) (64 bits)
Révision 62c648b961f58eec3b9a183f03d07b312ff32475-refs/heads/master@{#708294}
Michel Terrisse
Does a non-TinFoil version have any reason to exist anyway?
ERR_NAME_NOT_RESOLVED
@Anon5023, yes, because Safe Browsing patch has issues:
https://github.com/Eloston/ungoogled-chromium/issues/834 → Extensions don't install
https://github.com/Eloston/ungoogled-chromium/issues/835 → Crashes at sites login
If enable chrome://flags/#enable-force-dark, all page crash.
To put it mildly, I'm getting fed up with idiotic comments and stupid demands
Problems are on source code of Chromium.
You all need to calm the heck down. They're working on v78.
" Anon5029 24 Oct 2019, 12:05
Both Chromium and official gc stable v78 are completely broken. Short screencap: https://imgur.com/a/VnhF2c8 "
That's strange, the website https://drivetribe.com/ works just fine, also on Incognito-mode no problems.
My system:
Dell Studio 1537 Laptop:
Windows 7 64bit (up-to-date), Intel Core 2 Duo T6400 , 4GB Ram, ATI Mobility Radeon HD 3450 , 1280x800
with latest
Portable Chromium • 78.0.3904.70 (693954) • Wednesday, 23 Oct 2019 • 64bit
It turns out that happens whenever I scroll past a video, specially on social media sites. or literary any other website that has embedded video playing. Apologies if this isn't the right place to post but other chromium-based browsers such as opera/vivaldi/brave does not have the same problem.
@marmaduke: Your builds are greatly appreciated from the (silent) majority of users, thank you.
Your builds are really fantastic: speedly and stable.
Thanks for Your efforts.
Thanks You very much.
This is chromium bug or new feature, not build regression. :)
marmaduke win64 ungoogled relese in github. but not edit and update in here...
An entity even more vacuous than I am. Micososoft's - yes, that multi-billion dollar enterprise incapable of developing its own web browser - contribution towards Chromium: https://groups.google.com/a/chromium.org/forum/?_escaped_fragment_=topic/chromium-dev/FaE0LIhOWEE
Merging chrome.dll and chrome_child.dll by default!
My sister, Kylie builds Chromium form source, and says that the 10% extra link time interferes with her motherly duties and quality time with her beau, TraThick ass a Plank. Khole can't understand why Microsoft does not do something useful, such as developing a distributed version of clang-cl. Surely, the Microsoft cuckoo can lodge in the nest of disctcc or IceCC!
I have to go church with Kanye now.
XX
Othersides, new ungoogled chromium release just seems to work fine. Since I am visiting different forums, now I always have to open keepass to log me in (cannot remember my passwords). Its little annyoing, so I went back to 77 for instant.
----------------
Finally got a working Win32 build. Had to roll back to the project's own bundled LLVM suite, which means no Polly support. Still has my other optimizations and modifications, plus I suspect there will not be much difference since much of the Win32 build is done at -Os anyway.
1) Settings page always opens (seperately) when opening Extension page
2) 'Clear browsing data' is unclickable in incognito mode...sometimes you want to clear data from normal session, no big deal, you can still go into Settings page and clear normally
3) Disabling 'new tab animation' in flags only works half of the time, other half it still shows the animation, most strange!
4) Tab strips (I think that is the name for the new larger tab details?) can be disabled in flags.
Of note, my Win64 build results in a combined DLL that is larger than the 128MB per file prefetch limit in Windows 10 1903. The limit was only 32MB in earlier Windows versions (back to probably Win7), and the file sizes were over that previous limit back with the split DLLs as well, so I doubt much of anyone even will notice.... er, anything worthwhile IMO.
Sorry for inaccuracies, correcting:
3) Disabling the new-tab animation is not possible anymore in v78
4) I was referring to tab hover cards, not tab strips (chrome://flags/#tab-hover-cards)
It's not so much the merging of chrome.dll and chrome_child.dll, which should never have been done in the first place; but, with the withdrawal of Jumbo support and the the merging of chrome.dll, build times are needlessly excessive and energy inefficient.
Ideally, clang-cl (cross-compile) support in iceCC and/or distcc (while not solving the power inefficiency of the Chromium build process) would speed up the compilation process, and be an alternative to the undocumented Goma/RBE.
llvm/clang(-cl) and the Windows SDK is sufficient to cross-compile Chromium for Windows.
That said, I have been building Chromium for years. Think it is slow building now? Go back a few years and expect up to several hours for a MSVC WPO build. Possibly even many hours on consumer-class hardware of the era. Practically double it for PGO; not including the profile runs.
Anyway, another big issue for distributed building lies as much or more with LLD than clang IMO. Even if you distribute and cache clang, LTO codegen is still local. AFAIK, LLVM devs are working actively on a distributed LTO solution.
Update to last ungoogled 64 portable, and it result in an immediate exit :(
I can't launch chromium anymore as long as I keep my profil
Any clur to solve that?
Thanks
Tooltips in bottom-left corner was fixed.
And we finally lost the "overlay scrollbars". So sad.
----------------
Updated Win64 build with AVX2, FMA, etc. support. As before it still targets Haswell for available supported instructions, though I modified LLVM to set the underlying processor instruction scheduling model at Skylake since it is closer to my own Kaby Lake system. YMMV.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v80.0.3953.0-r710251-win64-avx2
Mine developed the same problem after I switched from Marmaduke's ungoogled v77 to Marmaduke's regular v78 and then to ungoogled v78.
If I ever decide to compile Chromium by myself. How long do you think the compilation process will take on my hardware?
i5-3570K, 16 GB RAM
Taking a guesstimate, I would think around 4 to 6 hours for a ThinLTO release build on your system. That is a huge YMMV guess as I typically do not build Chromium with stock optimizations, thus I am used to my own builds taking awhile.
BTW, it is not a substantial upgrade, but if building software you might could consider an used i7-3770 for a quick incremental upgrade to a quad-core, eight-thread processor with more cache. Thermals look the same as your existing chip, so I suspect it would be a drop-in replacement.
> around 4 to 6 hours
Not so bad, I thought it would be worse. Maybe I should try someday. Thanks for the detailed answer.
https://groups.google.com/a/chromium.org/forum/?_escaped_fragment_=topic/chromium-dev/oy36W9qWNAQ
https://bugs.chromium.org/p/chromium/issues/detail?id=994387
Thanks a lot bro, you saved me :)
Thanks for any replies and thanks to the ungoogled-chromium builders/maintainers
Hello.
An update for Android , would be very nice from you.
Thank you.
But why so slow servers - 20 kB downloadspeed - seriously (from amazon Servers)
this makes your hard work useless for me
(Server stops download after about 1/2 hour or so)
I use a VDSL2 connection, never so downloads that slow for years - is this optimized for 56k modems?
Possibly you are missing widevine support (used for drm video playback). Use this page to test if your browser supports drm - https://bitmovin.com/demos/drm (scroll down to EME, check for a plus next to widevine)
you can choose nag screen (every startup) which tries to force you to give your save storage password
or when you finally give your password - you have to do it for every new build
why????
this is worse than (google)chrome
Why is there no real choise - to never give the password and no nag screens (or if it is there - why so well/deep hidden?)
Builds with API Keys needed- developer make builds for developers - why don# t you keep them (ubreleased) without annoyng the users with them.
@Anon5072: Completely agree with you. If people dislike Chromium, prefer Firefox or the proprietary Google Chrome! 😋
@Anon5068: The Chromium releases are stored on Google (googleapis) or Amazon (github) servers. Yes it is well known that these servers are very slow! 😄
Revision f4432508dcc12787a0106d3f856f92a11749b0a3-refs/branch-heads/3904@{#847}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9
- official build
- All Bromite patches applied (AV1 does not work!)
- HEVC
- "No Search" option
- Domain substitution, tracking and blocking
- CFI & LTO
- 64-bit Webview and processes
I don't know if the adblock updater is working; domain substitution, tracking and blocking might interfere with the adblock updater service.
For surfing locally pi-hole is better.
====
Chromium 78.0.3904.90 (Official Build) (64-bit)
Revision f4432508dcc12787a0106d3f856f92a11749b0a3-refs/branch-heads/3904@{#847}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
arm64_MonochromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v78.0.3904.90-r693954-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
SHA1 B2E07CA044F0384DE79B1BF250858A77ED667108
Special Lewis "Still I Rise" Hamilton - 6 times F1 World Champion Edition - Dedicated to Anon5071
Chromium 78.0.3904.87 (Official Build) - "stable"
Revision 20c21f4010010f32462ea8e1d6af30cef66d48c8-refs/branch-heads/3904@{#840}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.2.3): October 2018 Update version 1809
- clang/llvm 10.0.0-r367199
cflags = [ "/O2", "-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly" ]
No Sync - WebRTC - Widevine - All Codecs (x64) - ThinLTO - Polly Optimised - Ungoogled
Standard build of Eloston's ungoogled-chromium. All patches applied (including "Safe Browser".)
ungoogled-chromium-78.0.3904.87-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v78.0.3904.87-r693954-Win64/ungoogled-chromium-78.0.3904.87-1_windows.7z
SHA1 F4716B640E084FC6A3BE9111EC030EFB2972D4BE
Ungoogled-Chromium-78.0.3904.87-Win32.7z (32-bit)
https://github.com/macchrome/winchrome/releases/download/v78.0.3904.87-r693954-Win64/Ungoogled-Chromium-78.0.3904.87-Win32.7z
SHA1 4009429A9AE864B4602024F84F9D833DB3DA0B2A
I found a problem where every time the browser offers to save a password you just submitted, it just crashes / closes.
Can be reproduced with a brand new profile after enabling "Offer to save passwords" @ chrome://settings/passwords
with no extensions installed.
Ok!
Are tangalbert919 users having the same problem; or is this problem just for Windows users?
My preference is to disable safe-browsing using policies; rather than to remove it completely. As far as I am concerned, safe browsing and Chrome Cleaner is an integral part of Chrome/Chromium for Windows. Personally, I would never entrust any browser with a password. The inability to save passwords could be due to a myriad reasons, and not necessarily solely to safe-browsing.
Hopefully, the experience of other ungoogled Chromium for windows users will result in the issue (the ability to save passwords) being fixed.
https://chromereleases.googleblog.com/2019/10/stable-channel-update-for-desktop_31.html
https://chromium.googlesource.com/chromium/src/+log/78.0.3904.70..78.0.3904.87?pretty=fuller&n=10000
This should be your priority considering that there's known exploit in the wild for use-after-free fixed in f1b501721e521a900c37b4f8cce4be8baedae731.
@Jerry Why are the marmaduke builds still linked at the top? The maintainer clearly couldn't care less about keeping it up to date and you are helping in spreading exploitable version as newest available to clueless users. Clearly this should be marked visibly and the maintainer should be shamed for prioritizing Android releases over security issue.
I found that there's already an issue about this, sorry for no looking sooner:
https://github.com/Eloston/ungoogled-chromium/issues/835
Both yours and tangalbert919 build crashing with password remembering. But I frankly I never trust browsers with my passwords either. So i can live with it turned off.
@Anon5084
why are you so negative? This is all done by volunteers, people simply have limited time in their day for building and testing shit.
many thanks for your latest ungoogled build, your constant efforts to provide timely updates is highly appreciated by all of us!
and please, just ignore the very few ignorant users with their impertinent and demanding comments, without a sense of decency.
Yes. Now that I've satisfied Anon5084's polite and dignified request, going to abandon Windows development and concentrate on macOS. Will produce a DEV version in the next few days. Jumbo build has now been discontinued, so should be an interesting build process.
chromium-web-store can help you.
https://github.com/NeverDecaf/chromium-web-store
First of all, thank you Marmaduke for your hard work. Long time user of your ungoogled builds.
I've been testing your recent releases (win x64, ungoogled):
- v77*120 no Safe Browsing patch
- v77*120 SB patch ("tinfoil" release)
- v78*70 no SB patch
- latest v78*87 SB patch
Result is SB patch breaks:
- Ability to pre-install extensions via the registry (as described here https://www.chromium.org/administrators/pre-installed-extensions)
- Ability to configure (under /settings/content): Unsandboxed plugin access, MIDI devices, USB devices, File editing, Clipboard, Payment Handlers (I like to set them explicitly blocked).
So if you ever go back to windows ungoogled builds (and I really hope so man), please consider gifting us with the good old "apart from Safe Browsing patch" builds.
Typical Chromium Win64 builds, including AFAIK all others posted here, do not as they only require SSE2 support.
[EDITED by Jerry 2019-11-06: Typo updated]
Go to my bloody Github site and you'll see that it does. Help yourself to the fries!
Please, ignore the comments which doesn't make sence from specific users. If you decide to skip some branches, that's fine. Peoples like me will understand the process and effort , which you try to put in your free time. There always will be bugs or security vulnerabilitys.
Again, peoples complaining can always used the latest stable version of Chrome with BEST ever security patches or because there BIG brains, can build their releases themself.
Simply, don't lose your time for this people. There always will be people and PEOPLE :)
Why is this not a polly, cfi, lto build?
Chromium have sacrificed cfi in order to build V8 snapshot. My beloved clang/llvm 8.0.1 is no longer fit for purpose: trillion dollar company, Apple, is incapable of producing a (ld64) linker that produces bitcode/IR that is compatible with clang 9/10 - hence no lto: I might be wrong on this, but like Apple, I can't be arsed to check!
Besides, distributed builds don't support LTO/polly. Since clang/llvm 8.0.1 is now obsolete, I had to do a local non jumbo build using Chromium's default compiler, which apart from compiling Chromium is not capable of much.
[35261/35261] STAMP obj/chrome/chrome.stamp
ninja -C out/default chrome 149751.67s user 10778.10s system 776% cpu 5:44:43.56 total
The build time is not too bad, considering ...
Produced new compilers for Icecc: 240 minutes to build a 2-stage production quality compiler for macOS, 40 mins to build the respective linux cross-compiler for icecc. will check functionally in a few days.
The build process itself: changes to Widevine, which the chromium Authors have fixed, so i had to amend my changes; changes to FFmpeg parameters.
Building with macOS SDK 10.15: some guy oh the Chromium dev board produce a fixed; used and ameded it. Also, had to softlink macOSsdk10.14 and macOSsdk10.15 to macOSsdk. Not particularly an issue since I used the same techniques to build a macOS SDK 10.15 version of ungoogled a few weeks back.
To the ignorant and the stupid, I suggest that you listen to Burning Spear's "Man in the Hills".
======
Chromium for 64-bit macOS - All Codecs - Wednesday, 06 November 2019
Chromium 80.0.3962.0 (Official Build) (64-bit)
Revision ab94bc190ac484330d83c12f0c5c4f344f7aeced-refs/heads/master@{#712947}
OS macOS Version 10.15.1 (Build 19B88)
only for macOS 64
with codecs (h264, h265, flac, xvid, AV1, etc..)
official build
Xcode_11.2.1 GM Seed
macOS SDK 10.15
clang/LLVM - Default Chromium
Sync • WebRTC • Widevine
Chromium.80.0.3962.0.sync.app.zip
https://github.com/macchrome/chromium/releases/download/v80.0.3962.0-r712947-macOS/Chromium.80.0.3962.0.sync.app.zip
SHA1 E96A3F8B5028B35D6EB0D2314B31333077A40828
RobRich: Thank you for the explanation regarding the AVX support requirement of your builds. I did not realize this. Makes sense as to why they don't work on my CPU. :)
- Official Build
- Using Chromium default compilers
- Sync enabled
- Widevine support
- Proprietary codecs enabled + H.264
Up-to-date build-time arguments used can be found in source tree for this release.
021f5509b55ea9726dd226249f3bac60dabc7b1c mini_installer.exe
0b5993316d0f4ecb2a3ae36b4c3540da965aab62 chrome.packed.7z
https://github.com/Hibbiki/chromium-win64/releases/tag/v78.0.3904.97
I'll continue to build Windows Dev builds; and to build Windows ungoogled without "safe-browser".
Conventional Windows stable builds: I don't actually use them! Nik abdicated, so, I thought I would provide continuity; but, I am not going to produce anymore V78 builds. If Hibbiki is willing to take over, then I will cease prodciung any Windows stable builds.
Anyway, Linux icecc server is up and running: icecc server did not miss a beat!
Standalone build (80.0.3962.0):
ninja -C out/default chrome 149751.67s user 10778.10s system 776% cpu 5:44:43.56 total
icecc server 24-Cores:
ninja -j 32 -C out/default chrome 9293.53s user 4541.50s system 114% cpu 3:21:56.13 total (Approximately X4 jumbo build)
The objective is get back to a jumbo, non-lto, non-polly build time of approximately 40-50 minutes.
I don't plan on building ungoogled or dev/beta variants however, nor I plan on using additional non-standard flags for building Chromium (or customized compilers for that matter), although the argument set may change in future (generally I plan to commit it if anything changes and then release it, so that the release includes source tree with arguments used).
Niki Lauda style, I take my hat off to you. I purposely did not ask for any assistance; people should be willing to volunteer without prompting!
The lack of curiosity leads to mediocrity.
@Nik
Hope you're doing well. Appreciate all the guidance.
88c257dc0d3a48a905eeb280125ae68cf64c616a sync-mini_installer.exe
0b17ecbf0ce0d6e0714c1b9fbe3535cfb7f422d2 sync-chrome.packed.7z
https://github.com/Hibbiki/chromium-win64/releases/tag/v78.0.3904.97
No-sync release coming in a moment, x86 builds coming tomorrow.
https://github.com/Eloston/ungoogled-chromium/issues/834 - Extensions don't install
https://github.com/Eloston/ungoogled-chromium/issues/835 - Crahes at sites login
As a general rule, make some effort to find the answer yourself before asking.
5a1ab0c044b7b0a7d964676d22a9ef9039eaa89f nosync-mini_installer.exe
1d94a1dc6276e035897657bb55c1d169fb50f02c nosync-chrome.packed.7z
As mentioned before, x86 will land in tomorrow.
@Jerry, will check in tomorrow.
Had to rely on Wikiwand for my Wiki needs, best of luck hunting down the bug.
Symptom of safe browsing. tangalbert919 and Eloston are doing a brilliant job: cut them some slack!
==========
Chromium for 64 and 32-bit Windows - Friday, 08 November 2019
Chromium 78.0.3904.97 (Official Build) - "stable"
Revision 021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.3.8): October 2018 Update version 1809
- clang/llvm 10.0.0-r367199
cflags = [ "/O2", "-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly" ]
No Sync - WebRTC - Widevine - All Codecs (x64) - ThinLTO - Polly Optimised - Ungoogled
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser"
ungoogled-chromium-78.0.3904.97-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v78.0.3904.97-r693954-Win64/ungoogled-chromium-78.0.3904.97-1_windows.7z
SHA1 D01E3120BF7F3926B2528EC08EE94AF850E26004
https://chromium.woolyss.com/?all=1#comment-4826
I tested on your "80.0.3962.0 (712967) • Thursday, 7 Nov 2019" - CTRL+C image then then CTRL+V in the Discord results in blank image. Windows7x64
I've tested "80.0.3964.0 (713988) • Friday, 8 Nov 2019" from "Chromium Authors" and it works is fine so it is something with your build. I did take a lok at chrome://flags but nothing was relevant there (altho I tested some related to clip board and shared data)
@Jerry
Replied to your email.
Dear developers, I hid "thinLTO" and "Polly" tags because:
1) This page needs more simplicity for users.
2) The info is still available on your Github page.
3) Most releases is built with "thinLTO" and "Polly".
Hope you understand. If you disagree, tell me here.
Thanks. Just a note that my releases don't include H.265 patch, as such I think they should be 'codecs+' instead of 'all-codecs').
I am wondering whether I should continue pushing nosync builds seeing that @Marmaduke is keeping up with his ungoogled ones and for people seeking nosync builds they are most likely better choice? The actual difference between sync and nosync builds is almost non-existent without ungoogled patches.
please re-add ungoogled-chromium github url to the ungoogled-chromium builds (for more infos), thanks
@Anon5130: Nothing has changed recently on the site about that:
whoops! my bad, the link was also in the main info box (green area) but i see it is now redundant
do you know if any builds are 'reproducible'? i was reading infos at reproducible-builds.org and wondered if that was possible, it provide ways to check the source is 'clean'?
thanks
- To build a "basic" snapshot for Windows: https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
- To build ungoogled-chromium for Windows: https://github.com/ungoogled-software/ungoogled-chromium-windows
Thanks for the detailed info!
The intermittent crashing is not limited to Wikipedia, seems to happen on other sites as well.
Also, sometimes (randomly as far as i can tell), the browser freezes, until you open the task manager and kill the GPU process.
This is with windows 1903 and the latest nvidia driver (441.12).
but why did you hid this f*cking tags "thinLTO" and "Polly" ??? I'm not understand! (
Does it really matter? You can see compile flags, etc on the corresponding Github page.
Hey! Come now: manners maketh the man. There is no need for that. Be civil.
----------------
The page rendering bug remains in my latest few Win64 internal builds. Hmmm. I was hoping to build past the issue. Now I am going to have to roll a stock build to see what happens.
Here is a known breaking page to test:
https://en.wikipedia.org/wiki/Chromium_(web_browser)
I will file a project bug report in a few.
-------------------
And now it is working in r714284. o.0 Whatever. I will roll another internal build now to check.
[EDITED by Jerry, 2019-11-11: Updated link (Issue with my linkifier!)]
Observing similar issue but happens very rarely and only on RDP on Windows 10, been happening since M78. Usually shows as simple vertical line on tab strip (which is integrated with title bar) in place where closed tab was.
Noobs... but build on macOS tags ThinLTO and Polly no hide, lol xD
----------------
Quick FYI update. Looking at the situation pragmatically, I suspect the page rendering breaker with Polly optimizations could be somewhere in Blink and/or V8. My build box currently is rolling test builds to check. I might not be able to pinpoint the exact break point, but hopefully I can isolate and exclude the specific component when applying Polly.
https://www.phoronix.com/scan.php?page=article&item=jcc-firefox-chrome&num=1
AMD seems okay for now:
https://www.phoronix.com/scan.php?page=article&item=zombieload-v2-taa&num=1
On a related note, there is a TSX Async Abort mitigation for Linux users as well:
https://www.phoronix.com/scan.php?page=article&item=zombieload-v2-taa&num=1
Is there a way to extend the portable version with a third party extension by default?
I would like to distribute this including the virtual keyboard extension (and if possible enable it by default) Can this be done or should i use external scripting for this?
Greetinx stefan
The workaround to add an exception doesn't fix this issue with Chromium breaking though. Currently upgrading the SEP version isn't an options. Is anyone aware of a workaround for this issue with Woolyss Chromium?
https://www.symantec.com/connect/forums/chrome-78-update-symantec-endpoint-protection-issue
Symantec put:
Chrome.exe --disable-features=RendererCodeIntegrity
But for it to work correctly, Chromium command lines are started with a double hyphen not a single hyphen
Therefore the correct example would be:
Chrome.exe --disable-features=RendererCodeIntegrity
Chromium (installed in Program Files) example:
"C:\Program Files (x86)\Chromium\Application\chrome.exe" --disable-features=RendererCodeIntegrity
The group policy works as well but has to be adjusted to work with Chromium correctly instead of Google Chrome from the example.
Key: HKLM\Software\Policies\Chromium
Name: RendererCodeIntegrityEnabled
Type: DWORD (32-bit)
Value: 0
Cheers!
Now I need to see about getting Polly back working on Win32, plus maybe pushing an updated Win64 AVX2 test build.
My experience is a single quote works for parameters, at least for -incognito and -disable-component-update on windows, maybe they allow both but originally used double quotes?
Big Thank you for all your build.
Little issue with latest 32bit.
Installer or archive.
"this version of prog is not compatible with your windows etc etc ..."
Regards...
Also big Thanks to @Marmaduke and @Hibbiki for keeping us updated.
Cheers...
Any update on the image data clipboard pasting issues in your build? The usability of it far too great so it is a complete delabreaker to me, have to use your old 78.x without latest exploit fix. Marmaduke's builds also affected btw.
Odds are if it is affecting mine and others' builds, then it is something needing reported to Chromium devs as a bug report. I can file it, but I will need the exact details for reproducing the issue.
---------------------------
While thinking about Chromium, since we now have an AVX tag, would anyone be *seriously* interested in a Win64 SSE2 build without the AVX requirement so it can run on Atoms and some older x86-64 processors? It is not too difficult to spit out both varieties other than the extra build time involved. Just let me know, and I will ask Jerry to add the needed listing if there is any actual demand.
Also I would like to get around to regularly updated Win64 AVX2 builds as well, though ideally that is going to imply a new build box. I am doing AVX2 builds on my notebook, which is slow go. Not that I need another "desktop" right now, but I might look into an AMD 8c/16t system early next year. Like a MSI B450 Max or entry-level X570 board with a 2700x or 3700x proc, 64GB memory, etc.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v80.0.3970.0-r716030-win64-avx2
I'd be highly interested in a non-AVX Win64 Dev build that is allcodecs/codecs+, sync and Widevine. :)
'"First time here...just wondering if it would be possible to add Hibbiki's chromium 64 bit build to chrlauncher so that it checks and updates to newest version if found? BIG THANK YOU to all the developers your time and skills are greatly appreciated!"
Not a very good first impression; NO "welcome to the forum, are you crazy that cannot be done, oh that's a great idea, nothing just dead air"
Still a big thank you to all the developers!
Have a wonderful day...over and out :-)
Your best bet for sync would be to create and set your own local personal Google API keys, thus enabling sync even for non-sync builds. Jerry has info above. I do not have my own personal Google API keys at this time, and being honest even if I did, I would be hesitant to push public browser builds using my own personal keys anyway. Definitely nothing against anyone here, it is just a potential concern of mine.
On the other aspect, Widevine probably can be enabled locally by simply copying it from Chrome or a stable Chromium build. Unless something has changed, building a *working* Widevine component with a dev build can be rather annoying and quite trying to support. o.0
I know LLVM uses the Sandy Bridge scheduling model for several Intel Core processor architectures, including even back to the Yonah family, but I am interested if the "generic" PostRAScheduler model might be more appropriate (and perhaps faster?) for some of the older families actually predating Sandy Bridge.
I might be interested in using you for a guinea pi.... err, code tester if you are up to trying a few build or few in the upcoming days. I will post here if/when I have something available.
Socket 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Manufacturer GenuineIntel
Name Intel Core 2 Quad Q9650
Codename Yorkfield
Specification Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz
Package (platform ID) Socket 775 LGA (0x4)
CPUID 6.7.A
Extended CPUID 6.17
Core Stepping E0
Technology 45 nm
TDP Limit 95.0 Watts
Core Speed 2995.8 MHz
Multiplier x Bus Speed 9.0 x 332.9 MHz
Base frequency (cores) 332.9 MHz
Base frequency (ext.) 332.9 MHz
Rated Bus speed 1331.4 MHz
Stock frequency 3000 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, EM64T, VT-x
Microcode Revision 0xA0C
L1 Data cache 4 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 4 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 2 x 6144 KBytes, 24-way set associative, 64-byte line size
Max CPUID level 0000000Dh
Max CPUID ext. level 80000008h
Cache descriptor Level 1, D, 32 KB, 1 thread(s)
Cache descriptor Level 1, I, 32 KB, 1 thread(s)
Cache descriptor Level 2, U, 6 MB, 2 thread(s)
FID/VID Control yes
FID range 6.0x - 9.0x
Max VID 1.275 V
https://github.com/RobRich999/Chromium_Misc/releases/tag/v80.0.3970.0-r716047-win64
It is a Win64 SSE2 build with my usual optimizations, Polly, ThinLTO, etc.
Also I modified LLVM to use a "generic" PostRA scheduler instead of using the default x86-64 scheduler that targets Intel Sandy Bridge. A couple of quick benchmark runs looked okay (or slightly better?) on my AMD Opteron box. YMMV, of course.
there seems to be something wrong with the Chromium for 64-bit Windows stable build version numbers at the very top. Perhaps it's just a typo here, but as I assume that part of the page is generated, something is off.
Best regards
1) For all builds, PGO instrumentation phase is now disabled so Chromium will no longer generate and leave default.profraw data around filesystem.
2) For nosync builds Hangouts extensions is now disabled.
@Anon5178: No. It is correct. The patches are different but they are applied on the same version and revision/position of Chromium. https://www.chromium.org/developers/version-numbers
@RobRich: Thank you for your #comment-5177 about Chromium for old x86-64 processors ^^
As far as I can see, this is an issue with chrlauncher not accepting standard output from Chromium build target. All my files come directly from Chromium build process invoked via command like this `autoninja -C out/stable-sync-x64 mini_installer.exe`. I don't process the files in any shape or form. If being double-packed is an issue I can upload chrome.7z instead of chrome.packed.7z, however it's over 200MiB in size as it uses no compression. Would that be fine? I don't plan or want to offer any binaries that are product of some other tool or were post-processed by some other tool other than Chromium's own build system.
https://github.com/henrypp/chrlauncher
^You might contact Henry++ if wanting to see about him supporting a different archive structure.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v80.0.3970.0-r716047-win64
Works very well! I was able to get Google sync working easily as I already have my own API key. :)
I tried copying over the Widevine contents from Marmadukes 64-bit Widevine, Dev, sync install, but it does not work with Netflix. I pretty much expected it to fail. I could try copying it from a stable build instead of a dev build but it's not a big deal by any means as I can use Microsoft Chromium Edge for Netflix.
Thanks so much for the build! Do you require any other type of feedback? Do you need me to check something specific with your build?
That was super fast build and is greatly appreciated!!! Cheers! :)
https://chromium.github.io/octane/
https://www.browserbench.org/MotionMark1.1/
https://www.browserbench.org/Speedometer2.0/
Then we can compare those numbers to an x86-64 build using the default Sandy Bridge instruction scheduler. I will try to roll that build tonight or tomorrow for you to try.
Octane Score: 18548
Motion Mark: 116.98 ±28.47% on a large screen (desktop)
Speedometer2.0: 43.5 ± 1.3
----------------
@Dustyn The other test build is ready. It is the same revision and optimizations except for using LLVM's default x86-64 scheduling target of Sandy Bridge.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v80.0.3970.0-r716047-win64-rev2
Please run the same benchmarks. Again, thanks for participating in the test.
----------------
@Hibbiki I noticed you mentioned PGO. Unlike back in the Visual Studio days with Chromium, I would not expect LLVM PGO to correctly work right without additional intervention in the build files. The better approach IMO is to modify the Chromium code coverage option to do PGO. Modify coverage, build with instrumentation, run Chromium with whatever actions to profile, generate the profile data, collate profile data, modify coverage again, and rebuild with profile data.
The Chromium project does not deal with PGO on Windows at this time. You will note I do not either for release builds. It is a long process to get a properly working PGO build. If I actually was doing it, worse yet I probably would talk myself into context-sensitive PGO, which requires at least three build passes.
----------------
On a related tangent, that is one of the things I like about building the Chromium browser for Linux. Unless something has changed in recent months since I last built on Linux, you can simply use the already provided PGO data generated by the Chromium OS project if desired.
Yes, the PGO is now disabled because of `chrome_pgo_phase`, my previous build has the instrumentation phase enabled by setting it to 1 by mistake.
@RobRich
I'm not touching resulting files, if keeping them under Chrome-bin won't work like for chrome.7z then I guess it's Henry++'s issue, not mine. We'll see on this stable release.
Looks like non-packed version works fine with chrlauncher so that's what I'll keep publishing from now on.
Builds are now updated to v78.0.3904.108.
Any chance that you offer a portable version (with auto-update chrlauncher) so the i can finally discard marmaduke version because i'm sick of it waiting for updates?
Thanks
thanks for the ungoogled update, works good on win 7 32-bit
@Hibbiki: Thank you very much for your efforts. Idem for @RobRich and @Marmaduke! ;)
Check codecs at https://tools.woolyss.com/html5-audio-video-tester/
- default: standard codecs (means "open-source codecs") for builds from the official repository (orange boxes, here!)
- "codecs+" means standard codecs + H.264 + AAC
- "all-codecs" means "codecs+" + H.265 + MPEG-4 + AMR
Below are the test numbers you asked for:
https://chromium.github.io/octane/ (Octane Score: 18623)
https://www.browserbench.org/MotionMark1.1/ (171.44±8.00% on a large screen (desktop)
https://www.browserbench.org/Speedometer2.0/ (43.0±1.1)
Hope you find this info useful.
Build works great!
Let me know if there is anything more I can do! :)
Also I was wondering if you were planning to one day publish these builds here on https://chromium.woolyss.com/ ?
I did not expect such a big difference in MM. It is a multi-pass bench, so it probably is somewhere in the realm of real world performance reality. The other numbers look about what my Opteron procs showed in quick testing.
For Dustyn and those following along, that means I will be leaving the Sandy Bridge scheduler in place for Win64 SSE2 builds.
Let me get my build situation straightened out regarding how I intend to proceed. I might do both SSE2 and AVX builds for Win64. Alternatively, I will do some local tests and see just how much difference AVX even is providing. If the delta is within like a couple of percent, I can just as easily migrate back to SSE2 building. Certain components, like FFMPEG, still will use AVX, AVX2, etc. when detecting available support anyway.
I was alerted early via e-mail to your v80.0.3970.0-r716047-win64-rev2 build early this morning. Awesome!
This will help me keep on top of any updates you may provide if I happen to miss something in the comment section here.
In terms of your build situation no worries. I will be curious to see what you decide to do moving forward. :) Cheers!
i get the same gfx corruption even on windows 10 now, i thought it was only win 7 related but it happens on a new (10) install...starting to think it is hardware related judging by the lack of feedback on googles support forums
anyway not a big deal, im such the chromium team have bigger problems and probably isnt worth me reporting it on what is likely a small number of impacted users
thanks again to all builders
Tried disabling hardware acceleration in Chromium?
chrome://settings/system
The software renderer actually is not all that slow in Chromium for most browsing tasks assuming you have to fallback to it for awhile.
https://en.wikipedia.org/wiki/SSE4#New_instructions
BTW, SSE 4.1 is supported on most mainstream x86-64 processors from Intel Penryn and AMD K10 forward - circa 2008 or so.
source: https://github.com/Hibbiki/chromium-win64/releases/tag/v78.0.3904.108-r693954 (sync version)
exe: https://www.virustotal.com/gui/file/50b839db547d6dde2c58f64fe43fce591346fd777a5146dfd36fdde31784aa50/detection
7z: https://www.virustotal.com/gui/file/5e43b6861958da09352b02984760cfaed9b918d7e28b7cafa73ad72206bb391f/detection
Q1. Does Hibbiki's new Stable Installer - Which lists Codecs+ but not All Codecs - Provide the same browsing experience?
Q2. Can I safely use Hibbiki's new Stable Installer to overwrite Marmaduke's Stable Installer installation I have now, and not lose bookmarks / passwords etc?
Refresher: https://chromium.woolyss.com/?all=1#comment-5124
As a reply to https://chromium.woolyss.com/?all=1#comment-5168
It is not a Chromium issue since official builds do not have such issue
https://github.com/macchrome/winchrome/releases/download/v78.0.3904.108-r693954-Win64/Chromium-78.0.3904.108-x64.7z
Elliot
Marmaduke's had everything I want, and Hibbiki's is as close currently to what I have than any others hence my questions in the last post - The most important one being Q2.
I like the all codec's and no sync, I don't like widevine, widevine just adds to bugs and crashes and problems when I use nothing that needs widevine software, the only feature i would ever rarely use in sync is translate the rest of the features i could never possible use those features like with widevine they serve no real purpose, I have not tried ungoogled but I do kind of prefer things to just work i am running Microsoft windows after all and not Linux and privacy really does not exist on the internet, i also do not want to have to deal with further bugs and problems that would be created by an ungoogled web browser the only perk i have read about is you do not have to update extensions and this is almost never beneficial unless the extension is broken with updates like privacy badger I do not see a reason for web browsers to exist without codec's when chromium is already there and updated ultra fast with no api keys. just some thoughts
The (unpublicised) link is to a "Sync - WebRTC - Widevine - All Codecs - ThinLTO" version. Someone asked me to do a non-polly version, because they thought that polly was causing video corruption.
The .7z archive is derived from the respective mini_installer.exe (with the addition of the Widevine component). If Widevine is not required just delete the folder. Also, sync can be disabled.
If the directory structure of the existing Chromium installation is replicated then the respective files can be replaced with the contents of the .7z archive.
Assuming you've previously installed Marmaduke's version using mini_installer then yes, you can use any other version's installer do update it without losing data.
thanks @marmaduke for the Win64 ungoogled archive build, that's the one I use for myself.
I'm mightily impressed by your personal engagement for the benefit of all of us.
Thank you ! (goes to RobRich too, of course)
I migrated the Blink renderer to its own compiler optimization config. Basic idea here:
https://pastebin.com/LK83gXqM
-----------------
@KZ: Thanks for the refresher. Probably a revision issue. I should have an update Win64 build today or tomorrow.
-----------------
BTW, it is looking like I will be producing two Win64 builds. My AVX build here, plus a SSE2 build that I will host at GitHub in the meantime. I can not promise they alyways will be in sync regarding release timeframes, but I do not mind churning out the occasional SSE2 build for Dustyn and others with legacy processors.
@Duke of Zurich: Welcome.
@Marmaduke: I was also curious about your dev version that you provide everyone with. Are you still updating the "all-codecs"+"sync" win64 build? This is my absolute favorite build of yours that I enjoy using that also contains working "widevine" (although not advertised as such here at woolsys). If your still interested in building this version, how often do you usually update it? I was hoping that it would be updated more frequently, at least once a month? It's just slightly over a month now, but I haven't been paying attention to how often you release this specific version of Chromium. Is it on a set schedule or on a successful build? I'm only curious as it's a very enjoyable experience using this version. I'm thankful for all the efforts for the Chromium options you give us here. Cheers! :)
@Jerry: I lost this entire posting when clicking "Send my comment". :( My fault as I forgot to "select all" and "copy" to retain the post in PC memory. I've just noticed over the last little while that my comments are being lost after clicking "Send my comment". The page will reload and I'm then at the top of this page. I scroll down to the very bottom to see my comment but it never posted? Sometime I have to re-post 2-3 times before upon the last submission the page reloads and takes my to the bottom of the comments section automatically telling me that my comment was posted successfully and is indeed posted. Is this a problem on my end only? This is with Microsoft Chromium Edge and Marmadukes's/RobRich's Chromium dev builds.
I'm still updating the development builds: have to stay abreast of the changes to the sourcecode.
The next dev build will probably be V81. The Chromium (dev) process is now non-jumbo and approximately 3 to 4 times longer; but, I'm mitigating the longer Windows build times by experimenting with Linux cross compilation. LTO works in the cross-compilation environment and I've yet to attempt a polly build.
Windows is an awful (Chromium) development environment. The Linux cross-compilation build times are aproximately 20-30% faster than the equivalent Windows build.
In the future will probably do more development builds: the dev tree is more geared towards cross-compiling: the issue with v8 snapshots has been fixed and the Chromium buildbots have banished cl.exe.
Hopefully, distcc and IceCC can be developed to accommodate clang-cl. I've been experimenting with Mac distributed builds, but am not too impressed with the efficacy of the distributed build process - massive under utilisation of remote cores.
My dev builds are basically proof of concept for futute stable builds. I'm surprised that anyone would want to use them - dev builds - as a regular browser.
Anon5198 here...Thanks for replying, yes, latest video drivers are installed, it's a machine from 2007 though :D No HW acceleration supported anyway according to chrome://gpu (using swiftshader), but I did try disabling it anyway. It's an old Intel chipset, wondering if the other people exhibiting same problems also have Intel IGP's.
Either way stability doesn't seem to be affected so I put it down to less R&D in the ageing PC department at Google.
The project is having build time issues as well. It is one of the reasons devs will not enable ThinLTO optimizations, yet. They still are running ThinLTO at opt level 0 basically as a multi-threaded linker. There is supposed to be a distributed ThinLTO process in the works. No idea on if/when shipping, though.
I have a build currently running to attempt a build time reduction even at -O3 for all optimized targets. Basically I once again am trying the new pass manager, along with simple unswitching plus nontrivial-unswitch enabled. I would like to try getting NewGVN working as well, but it usually hangs builds. I might try isolating the component(s) it is hanging.
One NPM issue is no Polly until further work lands. I am not too concerned as Polly really should be running late in the pass manager right before the vectorizer anyway, which currently is not possible with ThinLTO regardless of the pass manager being used.
@Anon5218 Hmmm. Not sure. I have an older spare notebook with Intel graphics that I need to update anyway. I might see what is happening if/when I have some free time to dust it off and get Windows updated.
BTW, it that a desktop system you have? If it has a PCI-E slot, almost any low-wattage AMD or nVidia card in recent years would be an upgrade. You can find entry-level used and OEM pull video cards on eBay for rather affordable prices. Just spotted a GeForce 730 for ~$24 shipped. Otherwise I *might* be replacing the 730 GT in my workstation sometime in the near future. If your system has a 16x PCI-E slot, I would send it to you for free if/when I upgrade.
These are the changes that I make to thinlto:
+ "/opt:lldltojobs=24",
+ "/lldltocache:C:/standalone/testbuild/thin_lto_cache",
+ "/lldltocachepolicy:cache_size=10%",
- "-mllvm:-import-instr-limit=10",
I don't really expect anything midly creative, innovative or jaw-dropping from the Chromium Auhors; it's not a slight on them - just a consequence of a Luddite, Byzantine development environment. Personally, I think the Chromium development process is 30 years out of date: it strikes me as being visceral, ad hoc and Heath Robinson.
While PIC is used on Linux, it is not needed for Windows. I am wondering if the build config is not accidentally setting PIC based upon the host instead of the target when cross compiling.
Anyway, find the primary compiler build file:
D:\depot_tools\chromium\src\build\config\compiler\BUILD.gn
Again, these should not matter since the target is Windows, but to be safe comment out the PIC flags around line 384.
if (is_linux || is_android || is_fuchsia) {
# asmflags += [ "-fPIC" ]
# cflags += [ "-fPIC" ]
# ldflags += [ "-fPIC" ]
Next, outright disable PIC by adding these below where the compiler flags are initialized around line 246.
asmflags += [ "-fno-PIC" ]
cflags += [ "-fno-PIC" ]
ldflags += [ "-fno-PIC" ]
I do not run a ThinLTO cache, but I am building on Windows, which AFAIK still has some issues with the caching process.
I run the instruction import limit at 100 for Win64 and 30 for Win32. 100 is the LLVM default. IIRC, the Chromium OS team found 30 was a good balance on their platform. I think 10 is a little low, but like with the Android import limit of 5, I suspect it was chosen for build time and file size instead of performance.
----------------
One option is to outright turn off LTO. That puts all the compiler codegen back into clang, which can be cached and/or distributed with distcc or similar.
------------
As to my efforts, back to the legacy pass manager and Polly for now. My NPM test build took about a 10% hit in Basemark Web.
...clang++: error: unsupported option '-fPIC' for target 'x86_64-pc-windows-msvc19.16.0'
I'll attempt to cross-compile a dev build.
It has been quite awhile since I have bothered, but have you looked into the performance difference between ThinLTO at the 10 instruction import level and no LTO at all? If there is not a significant difference at that level, you might consider dropping LTO altogether for Windows builds. It should build (much?) faster without LTO, too.
----------------------------------
Well, this is interesting. The performance drop I noted in Basemark Web is not pass manager related. Apparently ut is Chromium related. Hoping it is only a revision issue, as the revision I built dropped my test system's BW3 scores by around 10%. o.0
Anon5218 here...I'm looking into a full PC upgrade soon anyway but thanks for the kind offer!
I hope I can stick with Win7 for some time, the 'new' hardware is compatible, I worry when browsers will stop support the OS though, that I think is the real we will have to upgrade OS.
Cheers.
clang-cl == clang --driver-mode=cl is the "Windows compiler". clang++ is the native compiler in the cross-compile environment and is used to build the native auxiliary utilities such as mknapshot. In a Linux-Windows cross-compile environment, thinlto builds correctly. The -fPIC issue is a result of trying to incorporate polly into the build process. Polly is not a standard component of the Chromium build process, so it's not really a concern of the Chromium Authors; but it should be one for the clang\LLVM crew: the cross-compile should (be able to) incorporate all the functinality of the respective native compile.
Getting distcc or iceCC to work is not simply a matter of:
sed %s/clang-cl/clang --driver-mode=cl/g
Besides, distcc, iceCC and IncrediBuild is old technology, and I'm not particularly a fan of any of the CI\CD environments.
So what is my solution? Identical build nodes - virtual or physical. A dependency graph (state diagram) of the Chromium process is produced (which is a laugh in it itself, I stopped when the file was about 20Gb), and the jobs are broken into logical compile units and scheduled n-wise to the build nodes. The remote jobs are then consolidated and processed into the final product. When building a stable Chromium build we can assume that all the heavy lifting of testing as been done by Goma, since that is all it's good for.
You might also consider a dual-boot with Linux on a new system. ;)
----------------
I currently run Win10 on my primary systems. The start menu debacle largely has been resolved without needing a menu/shell replacement, and O&O ShutUp10 makes tweaking the privacy options largely a point-and-click affair. The latest release kernel supposedly is better suited to procs with SMT (i.e. hyperthreading) compared to older Windows versions, too.
https://www.oo-software.com/en/shutup10
---------------------
^As I sit here listening to streaming music on a now ancient Powerbook G4 17" notebook running in the background. Think circa 2005 hardware. VLC 2.x works fine for my media purposes, and while certainly somewhat slow due to the single-core processor, TenFourFox generally works okay enough for light browsing. The battery still even holds a change, plus awhile back I bought probably one of the last new-in-box OEM replacement batteries.
---------------------
Eventually my "solution" to the build time issue likely will be throwing more single-system hardware at it. I was thinking a Ryzen 3800x, but a 3950x is going to be a more realistic and significant upgrade from my old 32c Opteron build box. I would consider ThreadRipper, but I do not really need the extra memory bandwidth compared to Ryzen for building most software.... with the premium pricing on the new TR chips. o.0
Speaking of (ridiculous!) build times, I am waiting on a build of LLVM using VS2019 with LTCG (LTO) right now. I now remember why LTCG
is not fun for complex projects, as link.exe still has a limit of 8 threads for LTCG link-time codegen for some reason. There is the same thread limit for cl.exe as well, but it also offers /MP for up to *65536* parallel compiler processes, so that is 8 times however many configured processes. Link.exe does not have such a feature. I submitted a VS feature recommendation to at least up the link.exe /CGTHREADS: limit awhile back. Suppose I should get around to checking on the request.
---------------------
Good stuff for Chromium from the ARM devs:
https://webengineshackfest.org/2019/slides/chromium-updates-from-arm-higher-faster-stronger-by-dave-rodgman-and-adenilson-cavalcanti.pdf
I really don't want to buy a new crap CPU with a lifetime of performance diminishing microcode updates; nor do I a want a build-farm of 8 computers. I'll endure the longer build times, and absorb the additional financial cost. The decision to remove jumbo from Chromium is feckless and indolent.
A potential issue with component building currently is an error when manually disabling (commenting out) "/Zc:dllexportInlines-", which is a compiler flag that disables the exporting of inline member functions. The feature speeds component building for devs, but it also could affect binary runtime performance, too. I need to do some checks.
Another is using the ThinLTO cache for incremental building. I might have to look into cross compiling, though, as I am not sure the ThinLTO caching issues were ever resolved on Windows. Again, something I need to check.
-------------------------
I need to get some builds pushed; hopefully this weekend. I intended to roll them a day or few ago, but I instead have been poking at ideas to reduce build times.
-------------------------
I see no immediate or compelling reason to build the Vulkan backend for Chromium on Windows. AFAIK, it still is in (heavy?) development anyway. Most Chromium on Windows users are relying upon Direct3D hardware acceleration or switfshader software anyway.
enable_vulkan = false
angle_enable_vulkan = false
angle_enable_vulkan_validation_layers = false
dawn_enable_vulkan = false
*Ideally that should shave around 1/8 to 1/4 off build times*, or at least it does on my Opteron build box.
-------------------------
*Drop Polly* for now as well IMHO. It is breaking angle at build time and blink at run time here. I can hack around those issues with separate optimization targets if absolutely required, but that basically means disabling it for those components anyway, so whatever. It should drop considerable time off building depending upon the particular Polly config, too.
-------------------------
Next up is "simple" loop unswitching (plus untrivial tbd) and perhaps NewGVN to possibly further drop build times, but I am going to need additional internal testing for those. Some benches are similar, while others seem a little down. It could be my optimization levels and options need a little more tweaking since retracting Polly, so it could take a day or few to sort out the details.
https://reviews.llvm.org/rL301576
https://llvm.org/doxygen/SimpleLoopUnswitch_8cpp_source.html
https://lists.llvm.org/pipermail/llvm-dev/2016-November/107110.html
https://llvm.org/doxygen/NewGVN_8cpp_source.html
-------------------------
For those wanting an updated Win64 AVX build:
https://github.com/RobRich999/Chromium_Misc/releases/tag/v80.0.3976.0-r718453-win64
Note I am not pushing it to the usual release channel here, as it is a work in progress internal build investigating options to reduce build times more than a performance-optimized build. Nonetheless, it still is optimized to higher levels than a standard build, and it might resolve some recent likely revision-related issue(s) until I can get a (more) proper build pushed.
BTW, note the build size compared to my typical Win64 AVX releases. The mini_installer is down by like *9-10MB*. While they do not account for all the size difference, much of he balance is derived from disabling the Vulkan backend plus dropping Polly with its early code inlining pass.
-------------------------
Since it appears I am into Chromium tonight, I have a quick inquiry for build users. Specifically, what processors are Win32 build users.... well, using? CPU-Z, is a good freeware utility for Windows if wanting to check processor specs. Thanks in advance for any replies.
-------------------------
Is anyone actually using VR in Chromium?! It is relatively small, but toss that as well IMHO.
enable_vr = false
(angle) libvpx-no-polly.patch:
--- org/third_party/libvpx/BUILD.gn 2019-07-29 21:37:01.000000000 +0100
+++ new/third_party/libvpx/BUILD.gn 2019-07-31 09:44:42.712302900 +0100
@@ -70,6 +70,7 @@
cflags = [
# libvpx heavily relies on implicit enum casting.
"-Wno-conversion",
+ "-mllvm", "-polly=false",
# libvpx does `if ((a == b))` in some places.
"-Wno-parentheses-equality",
Given that Vulkan has to be explicitly enabled, and the Chromium Authors admit that Vulkan is only included in testing to stop bitrot, if substanial savings can be made in the build process then probably a good idea to drop it.
Hold off on dropping VR. I have found out it causes a missing symbol error. The build time difference probably is not worth the effort to resolve.
-------------------------
BTW, these should suffice for disabling Vulkan on Windows builds:
enable_vulkan = false
angle_enable_vulkan = false
dawn_enable_vulkan = false
-------------------------
Try:
modularize_vr_native = false
enable_vr = false
The reason I like your Dev builds over "stable" is due to the fact that the stable version you offer here on Woolsys is "ungoogled" and I want those services. Enabling them on your "ungoogled" build is not possible as it appears to be blocked? What am I missing to get that working? Your dev versions however work very nicely with "sync" and has the "allcodecs" and "wildevine" options present. :) "sync" also works nicely with your dev versions as I have my own Google API key. I'd try Hibbiki's stable version, but he is lacking "allcodecs" that your dev version provides. Cheers! :)
That said, I am going to try the third part's suggestion about the VR component, so thanks to whomever. :)
----------------
Given the annoyances with Polly and build times, I am resetting my Win64 baseline config for optimizations. I typically pass various options and settings into LLVM through Clang and LLD, but for the next release cycle or few, I will be building at known established LLVM -O levels while re-evaluating my other more fine-grained codegen features and optimizations.
TLDNR? For now probably most code at -O3 and maybe select code at -Ofast; with LTO codegen usually at -O3. YMMV as usual.
Is the 'all-codecs' really that important to you? 'codecs+' is identical to branded Chrome and on par with Firefox except for AV1. Unless you are doing something very specific, no site should require usage of 'all-codecs' variant to work properly, unless it's purposefully targeting such build.
----------------
IIRC, Dustyn mentioned Netflix, though I am thinking that is more Widevine for DRM. AFAIK, Netflix still supports H.264 or similar.
Not sure what mainstream sites absolutely *require* H.265, especially if they offer AV1, VP9, etc. like YouTube. Anyone notable mentions? Of note, pirated media and prOn sites need not apply. :p
----------------
"The variable "modularize_vr_native" was set as a build argument but never appeared in a declare_args() block in any buildfile."
I is apparently not available or at least not set for my build config, thus arriving back at the symbol linking error. Not a big deal IMO. I did not log it, but I think the symbol was maybe in telemetry, so the underlying code probably simply could be commented out. Maybe later.
----------------
Now to hopefully getting those updated builds done. :) The build box is working on building LLVM as I type this message.
I've been using your "Marmaduke all-codecs no-sync win64" builds (currently 79.0.3917.0 (697525) • Wednesday, 18 Sep 2019) as my main browser, and really enjoying it. Waiting for the next build :)
Royalty issues aside, HVEC is professional broadcast carrier grade quality; AV1 is consumer level OTT.
The morally depraved know how to use HEVC!
Both Firefox and Chrome do NOT support HEVC, only Safari (on macOS High Sierra+ and iOS), IE11 (via HW support) and Edge (via HW support, soon to be discontinued by Chromium-based version) have some level of support for it. No site should require it as they would be basically denying access to users using Chrome and Firefox.
@Hibbiki: I agree with you. So as you see, I changed the tags. Hope it is clearer for all.
@Yuliya & Dustyn: Thank you for your feedback.
@RobRich: I glued your latest comments. Haha!
Dear developers, big thank you for your time, help and effort. Really appreciated!
@RobRich: I think the only thing that Netflix requires is the use of Widevine with H.264 or similar as you mentioned. This was the only reason I requested Widevine to be placed in your SSE2 dev builds. It's certainly not required however as I can use my alternate Microsoft Chromium Edge, Marmadukes's Chromium Dev builds, or Hibbiki's stable Chromium build. :) Plenty of options.
@Jerry: I'm glad you appreciated the feedback. I certainly didn't mean to make things all confusing. lol ;)
@Marmaduke: With your Chromium Stable build you only offer the "ungoogled" build now? I tried to use it yesterday thinking that I could re-enable Google sync and other Google services in settings. I need to do some more of my own research I guess... lol This is something I can do with any of your Dev builds that say "no-sync" as I have my own Google API keys. I guess this is not the case as any attempts to use sync were blocked.
Thanks to all the developers here for answering questions and providing everyone with plenty of Chromium browser options! :)
Cheers!
- builds with no codec mention (= Default builds) → builds with only open-source codecs
- builds with "all-codecs" → builds similar to Google Chrome. Google Chrome has these all codecs and ONLY these ones.
- builds with "all-codecs+" → builds similar to Google Chrome OS. (It means to do more than a web browser!)
cf.: https://www.chromium.org/audio-video
https://github.com/RobRich999/Chromium_Clang/releases/tag/v80.0.3977.0-r718491-win64-sse2
No promises right now, but later I will get with Jerry about a listing and SSE2 tag if I do manage to keep Win64 SSE2 builds on a relatively similar release pace with AVX builds.
----------------
I dropped my LTO instruction import limits down to 30 for Win64 and 10 for Win10 to speed build times. I usually have opted for 100 and 30 respectively. 100 is the default LLVM limit.
The limit of 30 is looking okay for modern Win64 systems. The Chromium OS devs did a study and opted for 30 as well.
"....we got 1% slowdown on speedometer when changing import-instr-limit from 100 to 30."
Chromium by default uses a limit of 10 on Windows when LTO optimizations actually are enabled. That smaller limit should be okay on older 32-bit systems where code bloat can be more of an issue.
----------------
@Marmaduke: Good stuff. :-) That is about what I found, too. I will take the ~25% reduction in build times for the possible minimal performance difference and lack of (currently unneeded) Vulkan rendering support.
They are very much appreciated!!! Cheers! :)
Updated Win64 AVX2 *test build* now available. Requires Intel Haswell or later proc with AVX2, FMA, etc. YMMV.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v80.0.3978.0-r718998-win64
I would *like* to upgrade to a TR 3990X next year for building software, but I probably will be upgrading to a 3800x or 3950X if/when the system is completed. ;)
I am thinking like $3500 to $5000 just for the 3990X proc when released. I will be somewhat surprised if less, as the EPYC 7702P with its likely much lower clocks based upon a rated TDP comparison lists for $4425.
@RobRich (comment #5228): I know you asked about Win32, but my most used Win64 box has an Intel Xeon E5606 (Westmere-EP) that includes the following instruction sets: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x, AES
@Hibbiki (comment #5233) & @RobRich (comment #5234): all-codecs (well, I guess now Jerry's calling them all-codecs+) is useful to me for various reasons. One, in particular, is that one of the hats I wear is to code/test/develop various web tech, including media consumption.
@marmaduke: thanks again for releasing dev builds on MacOS/Windows that include sync, Widevine, and all-codecs+!
----------------
Same question still stands for Win32, assuming any of ya'll (likely few) remaining 32-bit users want to volunteer your system proc specs.
Remains to be seen how coherent sccache would be after a week or so.
You can see some details regarding which Field Trials / Variations are in use by visiting the following:
chrome://version/?show-variations-cmd
It is not incredibly organized and can be a chore to look through, but it gives some ideas anyway. Keep in mind that Field Trials / Variations can sometimes be different from one machine to the next machine based on percentages and such.
I know about potential Intel AVX2 throttling for "heavy" AVX256 floating-point code, but apparently FMA (even at AVX128?!) qualifies as "heavy" as well. Probably explains some minor, yet measurable regressions in my AVX2 build. I intend to disable FMA in my next AVX2 build to test.
I found this web site
https://www.cloudflare.com/ssl/encrypted-sni/
and chromium 80.0.3978.0 (718590) failed in Secure DNS & Encrypted SNI
Encrypted SNI
Your browser did not encrypt the SNI when visiting this page.
Anybody listening on the wire can see the exact website you made a TLS connection to.
Secure DNS
You may not be using secure DNS.
We weren’t able to detect whether you were using a DNS resolver over secure transport. Contact your DNS provider or try using 1.1.1.1 for fast & secure DNS.
in chrome://flags/ Secure DNS lookups is enabled and DNScrypt is installed and running Chromium seems to override and ignore what system and DNScrypt uses for DNS and settings and configuration
not sure where to write about defects within chromium and chrome but I use web browsers from this page
"When Chrome makes a web request, it will check to see if that provider is on a list of DoH-friendly DNS services which Google says it has vetted for strong security and privacy. Only if it is on that list will it switch to DoH."
Source: https://nakedsecurity.sophos.com/2019/09/12/google-experiments-with-dns-over-http-in-chrome/
Not in Your builds but as external link.
Did a quick search through chromium sources - there's a policy rule to activate DOH
Made a quick registry hack "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Chromium\DnsOverHttpsMode"="automatic", checked https://www.cloudflare.com/ssl/encrypted-sni/ - DOH is on now (Yes, I have cloudflare's dns configured on adapter settings)
About ESNI - https://bugs.chromium.org/p/chromium/issues/detail?id=908132
@Anon5257: Don't know exactly, what DNScrypt is, but wild guess - it acts as local proxy for dns lookups, so dns server in your adapter settings is actually 127.0.0.1, thats why DOH doesn't work for you
In your Chromium user directory under WidevineCdm directory. The module is not included because it's not open source and it's fetched from Google servers on first-run.
@Anon5260, @Anon5257
DNScrypt has nothing to do with DoH or DoT, I assume @Anon5258 is simply confusing these three.
DNS traffic encryption and authentication. Supports DNS-over-HTTPS (DoH) using TLS 1.3, DNSCrypt and Anonymized DNS
I have DoH for the whole pc via DNSCrypt?
https://github.com/DNSCrypt/dnscrypt-proxy
i wanted to run my own server but it doesn't sound like windows is supported or windows server don't know
https://github.com/jedisct1/encrypted-dns-server
Pioneered by the OpenBSD operating system circa 2008, systems to tunnel DNS over a secure channel greatly improve DNS security.
The DNSCrypt protocol was then specifically designed for that purpose. DNSCrypt version 2 was specified and implemented in 2013, and is probably the most deployed encrypted DNS protocol to date.
https://dnscrypt.info/
"As part of future milestones, Windows 10 users and admins will also be able to set up DoH servers explicitly using a dedicated interface within the Windows DNS settings."
Source: https://www.bleepingcomputer.com/news/microsoft/microsoft-is-adding-dns-over-https-doh-to-windows-10/
----------------
Updated Win64 AVX and Win32 builds in the listings above. Updated Win64 SSE2 build below.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v80.0.3982.0-r720336-win64-sse2
----------------
The recent issues with Polly are resolved, at least as tested with my current streamlined Polly config.
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-position=early",
As noted before, DeLICM is more for when running Polly later in the pass manager. We run early, so disable it to save build time.
I am not running the Polly early inliner pass, either, to speed build times. It pulls in lots of repetitive libc++ code that either outright does not optimize or does not really benefit much, if any, from optimization. No use spending expensive build time in Polly trying to deal with such code.
The 64bit build 80.0.3982.0 Archive version points to v80.0.3977.0-r718491-win64.
@z999 It is largely to each his/her own IMHO. Some people feel Google features can be intrusive in Chromium, while some here actually want those features. Yet like others like me probably do not care too much either way.
For example, I do not provide API keys with my builds as I have no use for Google Sync, but I am not going to the effort to actually modify the related underlying code to outright break Sync, either. That way for those few that do want Sync with my builds, they can setup and supply their own API keys.
I (attempt to) modify build parameters for better performance, which is my particular ongoing interest in the Chromium project. I often have one of the "fastest" modern browser builds available - huge YMMV, of course. However, many the actual browser features are secondary to my concerns, especially if I can simply enable and/or disable them through the usual browser settings anyway.
I use macOs mojave....
https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
been waiting since the announcement Thursday, October 3, 2019
not sure but think that was the only update i was waiting for?
do I still need HTTPS Everywhere extension with chromium 81 for auto upgrading http to https and blocking none https web sites?
https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp
https://addons.mozilla.org/en-US/firefox/addon/https-everywhere/
https://www.eff.org/https-everywhere
There also is some questioning if maybe a build flag should be created specifically for SwiftShader Vulkan support.
I'll presume that you are using Windows 10 64-bit and Chromium (ungoogled) v78.0.3904.108.
I test HEVC functionality by using the samples at https://tools.woolyss.com/html5-audio-video-tester/ ; HEVC functions correctly. If you drag and drop an HEVC sanmple then the file extension must be .mp4
Try this:
Chromium 79.0.3945.74 (Official Build) (64-bit)
Revision 99b6d241cf84f7fa7434ae8a59f9e74eb1464280-refs/branch-heads/3945@{#888}
No Sync - WebRTC - No Widevine - All Codecs - ThinLTO
- Linux cross-compiled (default compiler)
- No Vulkan
Chromium-79.0.3945.74-x64.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.74-r706915-Win64/Chromium-79.0.3945.74-x64.7z
SHA1 2BFEA80C7D70BD885A75761E154668D5BE9476BB
I've tested https://woolyss.com/f/caminandes-3-llamigos-x265-aac.mp4 and it functions correctly.
Hi. Could you foresee an update of Ungoogled for Android.
Thank you.
I was able to trade optimization levels for some paths to get Polly with early inlining back enabled for other paths without appreciable code bloat and build time increases. Results have met or exceeded my expectations so far in benchmark testing on my Intel Kaby Lake system.
-----------------------
Updated Win64 SSE2 build available for systems with low-power and/or older processors.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.3990.0-r722786-win64-sse2
https://github.com/macchrome/chromium/releases/tag/v79.0.3917.0-r697525-Win64
performance is good but not sure if bug or not but hover text is blacked out and green screens of death while video playback and media player is used on twitter only thus far entire media player screen goes green similar to that of a blue screen of death first browser did not get the green screens only change was browser
https://github.com/macchrome/chromium/releases/tag/v80.0.3978.0.0-r718590-Win64
Windows does not allow Chromium to change the DNS settings, so the test on Cloudflare page link https://www.cloudflare.com/ssl/encrypted-sni/ does not recognize Secure DNS.
To overcome this you need to change the DNS parameters within Windows and then execute test again on Cloudflare.
You have two options:
1. Follow the tutorial on Windowscentral.com at this link: https://www.windowscentral.com/how-configure-cloudflare-dns-1111-service-windows-10-and-router
the process works for Windows 10 (but also 7/8 / 8.1) and also affects your router
2. Use the portable program of Nirsoft.net 'Quick Set DNS' at this link: https://www.nirsoft.net/utils/quick_set_dns.html
For me it works.
However, if you use Tor with Chromium look on the Cloudflare site at this link: https://developers.cloudflare.com/1.1.1.1/setting-up-1.1.1.1/
So Marmaduke's build works perfectly.
oops... I use also SimpleDNS Crypt with select Cloudflare as Resolver.
This service is not running but it works with Cloudflare.
I am building at O2 across the board for clang and LTO codegen of all optimized code paths. Some LLVM-related tweaks, Polly with a few features enabled, Polly early inlining on hot code paths, increased LLVM inlining thresholds, increased LTO import limit, etc.
The build in particular produced one of the highest Web Basemark 3.0 scores in recent times on my test system. YMMV, of course.
v81.0.3990.0-r722786-win64
Reset flags, clear cache, etc. if not done already as well.
----------------
BTW, currently I only run two flags, and those are just to make sure the features are enabled locally.
chrome://flags/#turn-off-streaming-media-caching
chrome://flags/#enable-heavy-ad-intervention
Updated Win64 SSE build available.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.3991.0-r723152-win64-sse2
chrome://flags/
Native File System API: Disable
Cookies without SameSite must be secure: Enabled
Secure DNS lookups: Enabled
any suggestions for other flags to disable or enable
and I just added Heavy Ad Intervention: Enabled recommended by RobRich
Current version for Win 64 bit is 4.10.1582.2 of 2019-11-08.
https://github.com/macchrome/winchrome/releases/tag/v78.0.3904.108-r693954-Win64
Ungoogled Chromium is based on Beta version 79.0.3945.74 because I preempted the build!
The standard way to install extensions is to sideload. Furthermore, it is not now possible to include safe-browser in the windows version of ungoogled, so the SB patch breaks: the ability to pre-install extensions via the registry; and the ability to configure (under /settings/content) - Unsandboxed plugin access, MIDI devices, USB devices, File editing, Clipboard, Payment Handlers. Ungoogled is a work in process, and perhaps not suitable for the average user.
----------------
Updated Win32 build now available.
Sorry, I found it. https://www.bromite.org/
I recall some weeks back there was mention of no H.265 codec with Hibbiki's. I don't understand a whole lot when it comes to the media codecs and, specifically, the differences between the "all-codecs" tag and the "all-codecs+" tag. Of course, Jerry has done a fantastic job with details when hovering over those tags. But I don't necessarily understand if one codec is specific to, say, Netflix for example.
Many users are accustomed to Nik's builds (Stable branch) which he did a great job building and sharing with the community for several years. Now that Nik has stepped back and Hibbiki has stepped forward for the community, some users, myself included, may be wondered what the differences are between Nik's previous Stable branch builds and Hibbiki's Stable branch builds specifically when it comes to media codecs included (or not included) and what those differences may mean for overall web experience.
Is there someone in the community that can explain the media codecs differences between "all-codecs" and "all-codecs+" tags and what differences that can make for web experiences? (What sites and services may or may not be impacted?, etc.)
Thank you, as always, for this fantastic community of Chromium enthusiasts and developers. Also, thank you Hibbiki for stepping up to fill in Nik's shoes by compiling latest Stable branch builds. Cheers!
ungoogled 79.0.3945.79 is solid mate. it does what it says on the tin. Ripper!
Marmaduke is a spiffing chap and obviously an ardent Jeremy Corbyn fan and true socialist: unlike Alexandria Ocasio-Cortez who in Europe would be called a right-wing conservative and a buffoon ala Boris Johnson.
Big ups to Jeremy Corbyn, Marmaduke and the heroric workers of France in their fight against the neo-liberal shill man-child Macron.
@Anon5306
Ah! Didums
Check https://chromium.woolyss.com/?all=1#comment-5242 and https://chromium.woolyss.com/?all=1#comment-5237 for details on differences between these tags and codecs they involve.
Thanks as always for ungoogled-chromium updates. Can I ask the significance of no Vulkan support? Was this used before for hardware-acceleration of any type? And why was it built without?
Thanks again! :D
I have a little proble as when I try to download an extention, it downloads for ever... never end.
Do you know where it comes from as it was working perfectly before
thanks
Jeremy Corbyn, love or loathe him, is a traditional old school humantarian British left-winger: we don't do filthy atheistic degenerate bollocks contintental communistic Marxism in Britain.
@Anon5313
Vulkan is a 3-D library which really has no place in a web browser and is probably only used by spotty faced anti-social onnonists who aspire to be nonces. Alternatively, in a Windows environment Direct3D is the default graphics language, by eliminating Vulkan (and polly), and Linux cross-compiling the Chromium build is approximately 30% faster: this is to mitigate the removal of jumbo, which makes build times approximately 3 times longer. Having said that, the AMD Ryzen 9 3900X would form the basis of a nice Chromium development environment: single thread linking appreciates a high basic clock speed. v79 is still jumbo. So basically, I've been experimenting in preparation for non-jumbo builds.
Does any one actually use Vulkan?
Is that a local problem or someone else got the bug?
Anyway, thanks @marmaduke for the job!
https://en.wikipedia.org/wiki/Vulkan_(API)
https://en.wikipedia.org/wiki/Vulkan_(API)#Vulkan_1.1_2
buggy
https://github.com/macchrome/chromium/releases/tag/v80.0.3978.0.0-r718590-Win64
perfect
https://github.com/macchrome/chromium/releases/tag/v79.0.3917.0-r697525-Win64
I would not use the v79 version you linked because it is from September and has many security vulnerabilities (at least 1 that is being used in the wild), just a word of advice.
Engage development mode and side load, oitherwise just use Chrome or compile Chromium to your liking. Use your initiative, stop moaning and appreciate the effort that goes into building Chromium ungoogled. I honestly don.t know why marmaduke bothers casting his perls before swine.
Tutorial: https://www.cnet.com/how-to/how-to-install-chrome-extensions-manually/
Your anger makes you lose your mind bro.
Before you moan, read the message : "It was working" means I know how to install and use. I'm using ungoogled for years... I just report a bug that happened to me and require help from the community as sometimes it's a local problem that someone knows, and sometimes it's just a bug to the version which only needs to be reported and wait...
@Jerry
Damn, I confirm it's a local problem then because the same problem happens to my when trying your solution : the extension screen goes darker and shows the "drag to install" message, but now it is blocked on that screen when I release the extension file.
Don't know how to fix that :/
- get the crx file
- extract the crx file on crxextractor.com
- unzip (!) the downloaded zip file
- move the unzipped folder to \AppData\Local\Chromium\User Data\Default\Extensions
- start chromium - open about:extensions (not in incognito mode)
- click on load unpacked extension (or whatever it says in english)
- chose the location of the folder (see above)
- you're done
Thrust me, I know how to install and extension with ungoogled as I did a lot before
AND
if I revert to V78, it works again
I guess it's the same bug as @Anon5306 and @olle
If I load un extension with the unpacked method, indeed it works, but the extension behave very strange (tried from a brand new chromium).
I noticed that with V79, the extension will load in \%local user%\
Instead of the directory where chromium is (portable version)
So I guess it's a problem with portable transformation.
Thanks to those who help
Regarding unpacked extensions, you have to put the unpacked extensions folder somewhere permanent. It will always load the extension from there (it wont install/move it elsewhere on adding).
I've just figured that out right now :) Thanks
And don't put the extension in chrome profile\Default\Extensions directories as it will delete it...
And it's not portable
The thing is, why this change in V79 as it was working perfectly in V78... Chrome or ungoogled evolution ?
I use chromium web store to update my extensions and it looks like this evolution broke it. I hope it can be fixed as it's very useful.
Sorry I cannot help with the new change...though it looks like ungoogled-chromium never intended for extensions to auto-update (see https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq#will-extensions-auto-update), makes sense as you want google to have less control over what the software does.
I recommend putting unpacked extensions in the chromium program files folder in a folder called 'extensions' which may already exist. Extension folders/contents do not change so no problems if low-privilege users cannot write to the folder or permissions problems.
I know it was not intended for extension auto-update, but "chromium web store" is an extension made for that. check it and you'll love it.
https://github.com/NeverDecaf/chromium-web-store
That's what I was talking about
I notice the disappearance of "Handling of extension MIME type requests" flag.
I guess it comes from there :/
I cross fingers to have a work around as verifying and updating manually extensions is really a pain.
But still a big thanks to @Marmaduke !!
Hi
I noticed that chrlauncher 2.5.6 is present in the portable version of Hibbiki for Win 64.
Chrlauncher 2.5.7 has been released: https://github.com/henrypp/chrlauncher/releases/tag/v.2.5.7
Marmadukes ungoogled build, is also on 2.5.6
Can you update Ungoogled for Android to 79. Plz.
Thanks.
Can you update Chromium v81? (Sync - WebRTC - Widevine - All Codecs+) and installer?
Thanks.
Not happening here and I'm using the same build personally :>
Haha that ended well didn't it loser?
Corbyn's preparing his speech for Monday . .
"would you likr fries with that?"
'uck him.
2038
https://www.youtube.com/watch?v=zZwzrlLc_oc
https://www.youtube.com/results?search_query=windows+2038+problem
NVIDIA Officially Drops Driver Support for 32-bit Operating Systems
https://www.techpowerup.com/243320/nvidia-officially-drops-driver-support-for-32-bit-operating-systems
AMD Confirms Drop of 32-bit Executable Driver Support
https://www.techpowerup.com/248893/amd-confirms-drop-of-32-bit-executable-driver-support
AMD, via a statement provided to the 4Gamer publication, has confirmed they're dropping support for 32-bit executables in their driver releases. This move from AMD comes after mainstream adoption of 64-bit Operating Systems, which has rendered the market for 32-bit executables as apparently not worth the additional coding and certification effort.
Thanks so much and Merry Christmas,
Lorenz
Cross compiler is now capable of building a full mini_installer! I will still only upload the the archive.
==========
Chromium for 64-bit Windows - All Codecs - Sunday, 15 December 2019
Chromium 81.0.3998.0 (Official Build) (64-bit)
Revision f66e705bf3ae04e5ec568645ba9064672fb8e02f-refs/heads/master@{#724962}
OS Windows
- SDK 10.0.18362.1 (Visual Studio 2019 16.4.0)
- clang/llvm default (GNU/Linux cross-compile)
- ThinLTO
- WebRTC
Sync - Widevine
mini_installer.exe
https://github.com/macchrome/chromium/releases/download/v81.0.3998.0-r724962-Win64/mini_installer.exe
SHA1 0A62F64D1F04E4B438F9937B45F2F16224000BDE
Some video on YouTube can't reproduced.
There is a problem on source code of Chromium.
Solution?
Go to Settings -> System -> Use hardware acceleration when available: disable this flag and relaunch.
It works.
----------------
Hibbiki build works very well: it's fast and stable.
Not recommended.
https://bugs.chromium.org/p/chromium/issues/detail?id=1033655&q=component:Mobile>WebView&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified
@marmaduke
Do you know where it comes from and do you plan to reactivate this fonction, as it looks like a problem for many ppl?
Thanks for your work bro
Thanks for your explanation.
I'm usinf no-sync (ungoogled) since day one, but as CRX drog and drop stoped working in v79, I tested sync with a copy paste of user data (profile actually to me) and everything is working. But indeed, I don"t intend to copy profile back to no-sync, I keep using V78 ungoogled and wait.
Safe browser (and related) patch not applied:
ungoogled-chromium-79.0.3945.79-1_SB_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.79-r706915-Win64/ungoogled-chromium-79.0.3945.79-1_SB_windows.7z
SHA1 55552B22862E6E55FDFCC99416BC04DDBE647475
=======
No more releases until the New Year!
Merry Christmas and a happy New Year to all.
Boy you rock... It's Merry Christmas day already :)
Merry Christmas and a happy New Year to you !
Does ppl here recommand me :
- to switch to a Safe browser (and related) patch applied. It's the futur and https://github.com/NeverDecaf/chromium-web-store or equivalent will adapt
- Keep a Safe browser (and related) patch NOT applied. It's useless and build like this will live
I've read that it's only a hash, not the passord itself that is send.
Avoid sending those informations are more important that verifying passord leak in you opinion?
@marmaduke
Thank you so much.
Since upgrading to 79.0.3945.79 (706915), I can no longer use the translation function normally, am I just experiencing this problem?
No issues here. Make sure you are not trying to translate page to a language that most of the text on page is already in (this doesn't work and indeed shows failure) and that your extensions like uMatrix are not blocking domain 'translate.googleapis.com'.
i tries testing the latest stable and dev all-codecs+ options, but on the test page (https://tools.woolyss.com/html5-audio-video-tester/) only the caminandes-3-llamigos-x265-aac.mp4 video plays. The Tractor_500kbps_x265.mp4 video does not play. is that a limitation or did something go wrong?
Peter
Thank you for confirming :)
Pete
I think he may use the "storage only" packaging method, which may save some compression time, but is not friendly to network transmission.
@marmaduke: Did you see that your stable releases on macOS point to a "not found" Github URL.
--------
Note:
- I updated all "Portable" archives with chrlauncher 2.5.7
- In January, I will remove ThumbApps releases because they are outdated. However I will put a link to his portable (PortableApps) releases.
- In January, I will add the Hibbiki's "no-sync" releases.
- In January, I will add the RobRich's "sse2" releases.
Thanks
Chromium for 64-bit Android - Friday, 20 December 2019
Chromium 79.0.3945.94 (Official Build) (64-bit)
Revision 36534724d0d761d68b9150507df9c8e88c98f5d0-refs/branch-heads/3945@{#967}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9
- official build
- All Bromite patches applied (AV1 works - 32-bit webview)
- HEVC
- "No Search" option
- Domain substitution, tracking and blocking
- CFI & LTO
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
arm64_MonochromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v79.0.3945.94-r706915-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
SHA1 621512BBB2914203F7CB00073AFA73DD25A6247D
"Supported browser:
as launcher - Chromium based (like Google Chrome, Opera, Yandex Browser, Vivaldi, etc.) and Firefox based (Mozilla Firefox, Basilisk, Pale Moon, Waterfox, etc.)"
but i cannot find any information about setting it up for Firefox
Thank you very much for the update of Android;
If you can ad for your next build the "new" feature of Bromite ; DNS over HTTPS.
It would be great.
Thanks...
@All compiler , and you of course.
Thank you so much for all your work. :)
Settings -----> Privacy -----> Secure DNS
Hi.
Oups ; OK , thank you.
Sorry for disturbing you :) .
https://github.com/macchrome/chromium/releases/tag/v81.0.3998.0-r724962-Win64
(clang/llvm eadb65f273c076c4997b28a51f086eea505c3e78)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.88-r706915-Win64/ungoogled-chromium-79.0.3945.88-1_polly_windows.7z
SHA1 D4B2BE9D12267F2CB7448829D84144536C24571F
(clang/llvm 7376d9eb38914ff7b6b5f5901d32743f0ee76b5a)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.88-r706915-Win64/Ungoogled-Chromium-79.0.3945.88_polly-Win32.7z
SHA1 Ungoogled-Chromium-79.0.3945.88_polly-Win32.7z
(32-bit AV1 codec not link-time or polly optimized, program would not link otherwise!)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4007.0-r727374-win64-sse2
Updated Win32 currently building.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4007.0-r727374-win64-avx2
I have a Kaby Lake i7-7700. Can I easily compile on Windows my own chromium with google sync and SSE4.2 & AVX2 (I have a Kaby Lake i7-7500U)?
Is the performance difference noticeable?
Many thanks in advance!
I changed my audio driver too so I'm wondering which one is the culpit.
Thanks
No audio problems here with latest ungoogled-chromium...last audio problem was a few months back due to no hw acceleration...checking chrome://gpu shows what is used (swiftshader is used if no gpu acceleration available)
The default build targets a baseline of SSE2. However, to convolute the matter a little, some components can detect and run code for later SIMD revisions if a processor with support for those later SIMD revisions is available. For most code, though, the default is SSE2.
----------------
I change the baseline for my primary Win64 build from SSE2 to AVX. Beyond just new instructions, AVX offers more and wider SIMD registers. AVX also does VEX coding, plus VEX prefixing of SSE(n) code.
For example, VEX prefixing can be quite useful. It allows running mixed SSE(n) and AVX code without having to zero out the SIMD registers when switching code revisions. Using the default SSE2 build means that when one of those earlier mentioned components can and does use AVX, there is a decent chance the SIMD registers have to be zero'd as the processor switches between SSE2 and AVX code, such as running AVX code internally from that component mixed with SSE2 from another component.
By setting AVX as the baseline, the compiler can VEX prefix the SSE2 code even if no further optimization occurs. The VEX prefixing basically tells the processor to simply run the SSE2 code in the lower half of the SIMD register space, thus allowing mixed SSE2 and AVX code to run without potentially having a wait state to zero SIMD registers.
It is important to realize we are setting a baseline here, so still be sure to remember "some components can detect and run code for later SIMD revisions if a processor with support for those later SIMD revisions is available." So regardless of the base, say some component has AVX2 code, that AVX2 code will run on a detected compatible processor.
----------------
AVX2 and above is where we can run into possibly more significant performance minefields. For simplicity's sake, we can say AVX2 has "light" and "heavy" instructions. Light instructions generally are okay and potentially beneficial from a performance standpoint. The results of heavy instructions can be rather mixed depending upon particular instructions and what data is being processed. Heavy instructions usually are the ones responsible for changing frequency scaling, thermal throttling, etc. when processors encounter certain AVX2, AVX512, FMA, etc. code.
The general idea is whether AVX2 heavy instructions still are faster to process the target data even at a possibly slower processor clock. Therein I can build Chromium with an AVX2 baseline, but as to any performance benefit, it could change highly depending upon a system's specific hardware and what exactly is being done with the browser. Even then I am not inclined to measure the performance difference at the fine granularity needed to assess just how AVX2 coding affects each of the project's numerous components.
Some Chromium components do use AVX2 if available, but the devs of those components likely also either know about the specific instructions and/or profiled the performance differences for their code. Given I am not a project developer, I will leave those concerns to them.
I occasionally push an AVX2 public build, but like so many compiler-side things I do with Chromium, it is a huge YMMV and experimental for a reason. I suggest those using my Win64 builds to use the AVX build instead.
----------------
AVX512 is a "whole other bag of chips." Take what I said about AVX2, now make most every instruction "heavy," plus take note AVX512 is seriously fragmented in its instruction implementations. Just because a processor indicates "AVX512" support, it does not mean it supports the same instructions as a different model processor with "AVX512" support. Have fun! BTW, I do not even have a system with AVX512 support at this time, and probably will not for quite some time.
----------------
@debofsky Long story short, I would suggest to you and others with modern processors having AVX support to opt for the *AVX builds* if running my Win64 builds.
Are you going to notice a huge performance difference? Again, YMMV depending upon what you are doing with the browser. There are numerous other factors at play with my builds, too. For example, my Win64 builds in particular have differences in component optimization levels, LLVM-specific options, LTO instruction import limits, etc. compared to standard builds. Toss in Polly (https://polly.llvm.org/) optimizations as well, though right now I keep them somewhat constrained due to excessive build times.
----------------
@Dustyn Thanks for the positive thoughts!
Thank you for providing the updated polly version of 79.0.3945.88.
In this release you have additional file called "bollocks.txt" and the file "chromedriver.exe" which is part from your portables is missing.
I used the android version 73.0.3683.75 for some time and now I tried to use the 79.0.3945.94 because of the AV1.
In this release 79.0.3945.94 if Google is selected for search engine, we don't have any results, because the connection is blocked. The rest of the search engines are working.
I tried to use the Bromite 79.0.3945.94 and Google is working, like search engine.
Thanks.
Chromedriver.exe is a standalone program and can be obtained from the my respective non-polly version of Chromium. Bollocks.txt was included by mistake and if desired may be removed.
The Google search engine is blocked because of domain substitution, tracking and blocking. I'll make sure that Google is not blocked in the next release.
https://pastebin.com/UF4F8fhQ
Translation? I now have LTO interprocedural Polly optimizations available.
I will post the source changes later, as I need to find a recent regression hanging LLVM when invoking Polly. In the meantime, I am using the same LLVM revision as the Chromium project currently bundles with its repo checkout.
----------------
Found the Polly breaker in LLVM. I have posted a note in the Polly discussion group. In the meantime:
git revert --no-commit 9f6b13e5cce96066d7262d224c971d93c2724795
----------------
A few quick-and-dirty edits got Polly working during ThinLTO codegen via lld-link.exe on Windows.
----------------
D:\src_builds\llvm-monorepo\llvm\lld\COFF\CMakeLists.txt
Add IPO to LINK_COMPONENTS and add Polly to LINK_LIBS as shown in the source link below:
https://pastebin.com/NBiBPW67
----------------
D:\src_builds\llvm-monorepo\llvm\lld\COFF\Driver.cpp
Add namespace for Polly. Line 57 in source link below.
Initialize Polly for LTO. Line 1113 in source link below.
https://pastebin.com/vexW0fBp
----------------
lld-link.exe will now accept, initialize, and pass arguments for Polly. For a basic example:
-mllvm:-polly -mllvm:-pass-remarks-analysis=polly
----------------
Example of analysis remarks generated by lld-link.exe for some code I compiled with both Polly and ThinLTO enabled.
....
<unknown>:0:0: SCoP begins here.
<unknown>:0:0: Inbounds assumption: [p_0, p_1, p_2, p_3] -> { : p_3 >= p_0 }
<unknown>:0:0: Inbounds assumption: [p_0, p_1, p_2, p_3] -> { : p_2 >= 2p_0 }
<unknown>:0:0: Inbounds assumption: [p_0, p_1, p_2, p_3] -> { : p_2 >= 2p_0 }
<unknown>:0:0: Inbounds assumption: [p_0, p_1, p_2, p_3] -> { : p_2 >= -1 + 2p_0 }
<unknown>:0:0: Inbounds assumption: [p_0, p_1, p_2, p_3] -> { : p_2 >= -1 + 2p_0 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 >= 4611686018427387905 and p_1 > 0 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 >= 4611686018427387905 and p_1 > 0 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 >= 4611686018427387905 and p_1 > 0 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 > 0 and p_1 >= 4611686018427387905 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 > 0 and p_1 >= 4611686018427387905 }
<unknown>:0:0: No-overflows restriction: [p_0, p_1, p_2, p_3] -> { : p_0 > 0 and p_1 >= 4611686018427387905 }
<unknown>:0:0: Finite loop restriction: [p_0, p_1, p_2, p_3] -> { : p_0 < 0 and p_1 > 0 }
<unknown>:0:0: Finite loop restriction: [p_0, p_1, p_2, p_3] -> { : p_1 < 0 and (p_0 < 0 or p_0 > 0) }
<unknown>:0:0: Possibly aliasing pointer, use restrict keyword.
<unknown>:0:0: Possibly aliasing pointer, use restrict keyword.
<unknown>:0:0: Possibly aliasing pointer, use restrict keyword.
<unknown>:0:0: Possibly aliasing pointer, use restrict keyword.
<unknown>:0:0: Possibly aliasing pointer, use restrict keyword.
<unknown>:0:0: SCoP ends here.
....
----------------
For Chromium, it can be added to the compiler build optimization configuration.
D:\depot_tools\chromium\src\build\config\compiler\BUILD.gn
For example, below the common_optimize_on_ldflags initialization around line 1895, add:
common_optimize_on_ldflags += [ "-mllvm:-polly", "-mllvm:-pass-remarks-analysis=polly", ]
----------------
Note I did not condition the LLVM source changes, so remember to enable the Polly project when building LLVM. For example:
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang;lld;polly;compiler-rt -G "Ninja" ..\llvm\llvm
----------------
My build box is working on such a build right now. Basically it is a slammed -O3 build for both clang and LTO codegen as a test. I will try to push an experimental build if/when it works.
----------------
Polly breaker hopefully should be resolved with a LLVM commit that just landed.
Should know shortly. I need to rebuild LLVM anyway.
Archive only due to PoC status. For those interested....
Chromium 81.0.4015.0-r727929 (Win64, AVX, Polly, ThinLTO)
https://drive.google.com/open?id=1YhvDNvOefyewVNmtJyc8BV0ix3d9ph7f
SHA-1: 1C83B84AB29A3ED998C512A0471CF0B513526BC1
Anyway, it still churned out a decent BaseMark Web 3.0 score on my test system, so hopefully some further tweaking will yield further performance benefits. Now to start enabling more LLVM and Polly options, plus probably bump the LTO import limit.
----------------
Looking towards the next few build cycles, I am hoping to find and stabilize an updated Polly+ThinLTO optimization game plan.
I have been thinking about maybe generating my own Windows .order files for symbol layout during linking instead of using the project's provided files, but I get the feeling any returns will be very little compared to the build times involved, profiling annoyances, etc.
While not (anywhere) near the top of my list, I would not mind eventually trying to get PGO back working as intended. Last time I tried it via a modification of Chromium's code coverage configuration, the instrumentation phase was complaining about various missing symbols. IIRC, they were related to what the compiler-rt PGO library was wanting. Might just need another library added during linking.
----------------
@Anon5397: Polly works for Windows 32-bit builds, too. :)
However there still is the issue of trying to easily measure specific performance change using readily available benchmarks. Polly is for optimizing loops, and particularly suited for loops doing heavy data lifting. Some of the better examples in Chromium would be media codecs, SSL encryption, and similar components that most browser benchmarks rarely target. Being realistic, one might find Polly in more typical usage for HPC-class workloads where its benefits can be dramatically more apparent and viably measured.
The reality is Polly often helps a percent or few on various browser benchmarks. It is rarely a dramatic difference, though, but remember we are dealing with trying to find and eek out extra performance on a codebase that already is subjected to routine internal performance testing by the project's own automated infrastructure and experienced developers.
Cheers!
Currently I am running Polly both early for Clang codegen and late for LLD ThinLTO codegen. The technique seems to be working okay for my purposes. Benchmarks tried so far look okay on my test system as well.
----------------
Polly is wanting to see about me submitting the LTO patch(es) for LLD. I have not any actual code development since college, and my typical idea of ide, versioning, and build systems largely was a terminal text editor and CLI commands to toss together math-oriented Fortran code on a DEC Alpha server running VMS. o.0
Anyway, I might try to take a poke at it over the upcoming days if I feel up to it.
----------------
@debofsky I have never bothered to register Google API keys to enable sync. However, the sync components actually are in my builds. It is just the code is dormant without keys being supplied. The upside is you can generate your own personal keys and supply them locally using system environment variables to enable sync for my builds. Jerry has instructions here:
#google-api-keys
1. Add ENABLE_PLUGINS to lld\COFF\CMakeLists.txt
See: https://pastebin.com/up1P5WB3
2. Add
#define HANDLE_EXTENSION(Ext) \
llvm::PassPluginLibraryInfo get##Ext##PluginInfo();
#include "llvm/Support/Extension.def"
to lld\COFF\Driver.cpp
See: https://pastebin.com/wd1YQRNk
3. Build LLVM with Polly and Polly linked into tools. Example:
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang;lld;polly;compiler-rt -DLLVM_POLLY_LINK_INTO_TOOLS=ON -G "Ninja" ..\llvm\llvm
4. Be sure to pass Polly into lld-link.exe using the -mllvm:-polly argument. See my previous recent post about adding Polly during ThinLTO codegen to the Chromium compiler build configuration.
Works perfect with firefox
However, I have to report an issue : after version 81.0.3991.0, your recent builds don't seem to understand the FTP protocol.
For instance, try to download a file from here: https://www.doomworld.com/idgames/levels/doom/Ports/s-u/standrd2 (good old Doom levels frontend site) trying the "Download mirrors" links: Well, nothing happens on builds more recent than 81.0.3991.0, while the save dialog opens and works with 81.0.3991.0.
In regards to your question about the FTP protocol... That has nothing to do with RobRich but rather Google.
That is expected behavior as Google is slowly deprecating the FTP protocol altogether.
https://www.ghacks.net/2019/11/03/google-adds-temporary-flag-to-chrome-to-allow-ftp-protocol/
https://www.bleepingcomputer.com/news/google/google-has-started-removing-ftp-support-from-chrome/
Still happens:
https://chromium.woolyss.com/?all=1#comment-5205
Tested on your AVX 81.0.4015.0 (727929) • Friday, 3 Jan 2020 - ctrl+v in Discord or IMGUR pastes empty image.
Absolutely fine on official builds.
In addition to "-mllvm:-polly", which other polly parameters do you recommend to pass to "common_optimize_on_ldflags"?
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4017.0-r728360-win64-sse2
----------------
@KZ See if this changes anything:
chrome://flags/#raw-clipboard
----------------
@marmaduke Here is what I am currently passing through Clang and LLD for Polly:
common_optimize_on_cflags += [
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
]
common_optimize_on_ldflags += [
"-mllvm:-enable-local-reassign",
"-mllvm:-regbankselect-greedy",
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-register-tiling",
]
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
I tried to enable Polly via LLD for LTO codegen in a Linux environment for ELF and COFF, but when trying to build clang/llvm get the following error:
"include/llvm/Support/Extension.def:2:1: error: no type named 'PassPluginLibraryInfo' in namespace 'llvm'"
So, I thought might as well cross-compile Chromium 64-bit (Linux/Windows) with "-mllvm", "-polly-position=before-vectorizer"
Polly parameters used:
common_optimize_on_cflags += [
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=before-vectorizer",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
]
Used Xclang parameter in the hope of getting some feedback (there was none), equivalent to when -"polly-position=early" is used.
The build completed successfully, and there is a difference in file sizes with respect to the non-polly build.
The Linux command "ps ax" confirmed that the polly parameters are being passed to clang-cl. So, in a Linux/Windows cross-compile environment is it sufficient just to pass polly parameters to common_optimize_on_cflags and to assume that "-polly-position=before-vectorizer" functions correctly?
Chromium x64 for Windows - Linux cross-compiled
Basemark Web 3.0
-polly-position=early 8% faster than non-polly
-polly-position=before-vectorizer 3.42% faster than non-polly
R U on drugs? G.O.O.G.L.E Chromium! If you download Chrome/Chromium, don't connect to the the net and put on your tinfoil hat you should be OK.
I know on a native build, clang-cl will accept Polly before the vectorizer, but it does not do anything (thus no remarks) because the legacy pass manager skips the vectorizer passes until ThinLTO codegen via LLD.
BTW, about the error, are you building LLVM from trunk? The updated set of edits I posted needs a recent commit to work, at least as I tested for COFF.
Yes, I'm building from trunk: f3f7dc3d2990151a78b246a7a1485d0c13a9fb36 06-Jan-2020.
I'll try a native build.
=============================
Chromium for 64 and 32-bit Windows - Wednesday, 08 January 2020
Chromium 79.0.3945.117 (Official Build)
Revision 04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019}
OS Windows
- GNU/Linux cross-compiled
- SDK 10.0.18362.1 (Visual Studio 2019 16.4.2)
- clang/llvm - commit: 7376d9eb38914ff7b6b5f5901d32743f0ee76b5a
- Polly optimized
cflags = [ "/O2", "-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-enable-optree=false",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-vectorizer=stripmine", ]
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Ungoogled
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser"
ungoogled-chromium-79.0.3945.117-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/ungoogled-chromium-79.0.3945.117-1_windows.7z
SHA1 4F57E753D069A7AED5445E7BA805B22823FFD5A8
Ungoogled-Chromium-79.0.3945.117-Win32.7z (32-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/Ungoogled-Chromium-79.0.3945.117-Win32.7z
SHA1 0D2A484FCE59B390BF0E59A86B031C608B4230A3
That said, there could be a later commit or update involved, as that was a few days ago. I will try a fresh build it in awhile.
Yes, I set both Polly in the projects to build and -DLLVM_POLLY_LINK_INTO_TOOLS=ON via cmake.
@Anon5420
Thanks. I will repackage and update.
Regarding Anon5420's comment..I notice a dll file missing (maybe) in the 'Swiftshader' folder on the x86 version - 'libEGL.dll'..the file exists in the x64 archive. Just bringing this to your attention in case you are yet to update x86 version. Thanks for providing ungoogled builds.
https://github.com/macchrome/chromium/releases/tag/v81.0.3998.0-r724962-Win64
Portable launcher for 32-bit stable ungoogled build by Marmaduke (chrlauncher-win32-stable-ungoogled.zip) is not working - it has wrong config (chrlauncher.ini): ChromiumType is set to "stable-ungoogled" which results in empty response from API when chrlauncher tries to get latest build.
While similar 64-bit portable launcher keeps correct type "ungoogled-chromium" which works properly.
- If you use the Hibbiki's release, Chrome Web Store works.
- If you use the Marmaduke's release (ungoogled), Chrome Web Store does not work. This is normal.
https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq
@Anon5424: Choose "ChromiumType=dev-codecs-nosync" in your chrlauncher.ini file.
@Anon5425: Ok. Thank you very much for your report. Corrected! ;)
First, thanks for your effort and time investment building this editions of Chromium. I tried install in Program FIles but doesn't happen. How can I specify install directory for Hibbiki's release? I use 64-bit version with --system-level but installs on Program Files (x86).
Chromium 79.0.3945.123 (Official Build) (64-bit)
Revision fae8572a2711b5220fcec059ba824bf62fed054f-refs/branch-heads/3945@{#1026}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9 & 10
- Official build
- All Bromite patches applied
- HEVC and AV1
- "No Search" option (Replaced Google search engine with no search)
- Domain substitution, tracking and blocking (Now standard on Bromite!)
- CFI & LTO
- No menu option to toggle global Javascript (Feature has sadly been removed)
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
arm64_MonochromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v79.0.3945.123-r706915-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
SHA1 0DCD03A801DC29745101857E140EEB5E7AAC93B9
1. Add ENABLE_PLUGINS to lld\COFF\CMakeLists.txt
See: https://pastebin.com/R2A5xsCt
2. Add
#include "llvm/Passes/PassPlugin.h"
and
#define HANDLE_EXTENSION(Ext) \
llvm::PassPluginLibraryInfo get##Ext##PluginInfo();
#include "llvm/Support/Extension.def"
to lld\COFF\Driver.cpp
See: https://pastebin.com/BkGx6zfp
3. Build LLVM with Polly and Polly linked into tools. Example:
cmake -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang;lld;polly;compiler-rt -DLLVM_POLLY_LINK_INTO_TOOLS=ON -G "Ninja" ..\llvm\llvm
4. Be sure to pass Polly into lld-link.exe using the -mllvm:-polly argument.
Current Polly config for both Clang and LTO codegen:
common_optimize_on_cflags += [
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
# "-Xclang", "-Rpass-analysis=polly",
]
common_optimize_on_ldflags += [
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-register-tiling",
# "-mllvm:-pass-remarks-analysis=polly",
]
Patched COFF ELF wasm!
Polly LLD would only work in the position indicated below.
===============
build/config/compiler/BUILD.gn:
~ Line 2011
config("optimize") {
if (is_win) {
# TODO(thakis): Remove is_clang here, https://crbug.com/598772
if (is_official_build && full_wpo_on_official && !is_clang) {
common_optimize_on_cflags += [ "/GL" ] # Whole program optimization.
}
# Favor size over speed, /O1 must be before the common flags. The GYP
# build also specifies /Os and /GF but these are implied by /O1.
cflags = [ "/O2",
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
]
~ Line 603
if (is_win) {
# This is a straight translation of the non-Windows flags below,
# except we do not use the ThinLTO cache, which leaks temporary
# files on Windows (https://crbug.com/871962).
ldflags += [
"/opt:lldlto=" + lto_opt_level,
"/opt:lldltojobs=" + max_jobs_per_link,
# Experimentally determined to yield a reasonable trade-off between
# build time, run-time performance, and binary size.
"/mllvm:-import-instr-limit=10",
### "-mllvm:-pass-remarks-analysis=polly", #### FOR COMMENTS ###
"-mllvm:-enable-local-reassign",
"-mllvm:-regbankselect-greedy",
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-register-tiling",
]
} else {
==========
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Ungoogled - Super Polly Optimized
- GNU/Linux cross-compiled (Host Linux target Windows 64)
- clang/llvm - commit: 6d6a4590c5d4c7fc7445d72fe685f966b0a8cafb (13 Jan 2020)
ungoogled-chromium-79.0.3945.117-1_polly.lld.windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/ungoogled-chromium-79.0.3945.117-1_polly.lld.windows.7z
SHA1 05C5CDFA2591CA297325DCCFD41C541A985E8F0F
chromedriver.polly.lld.7z
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/chromedriver.polly.lld.7z
SHA1 0B561A3CA74D6CD1A3D77A4E2B8018490C7CCEDB
Just make sure to pass Polly into Clang for all four active optimization levels.
I suppose cross compiling could be the reason about where you need to pass the ldflags. Anyway, as long as they get in there.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4027.0-r730470-win64-sse2
Updated Win64 AVX2 experimental build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4027.0-r730479-win64-avx2
I will try to push an updated Win32 legacy build tonight or tomorrow.
I had to move a folder too align the thing.
Hope you find a way too compact this bookmark bar again !
Thanks. Making sure to pass Polly into Clang for all four active optimization levels! Doing a build with the bootstrapped compiler now.
@Anon5442
In present stable cross-compile I manually package (the mini_installer produced is incomplete); deleted the wrong file.
Replace swiftshader/libEGL.dll.lib with:
Ungoogled-Chromium-79.0.3945.117-Win32.libEGL.7z
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/Ungoogled-Chromium-79.0.3945.117-Win32.libEGL.7z
SHA1 F0629BE1F84CF844CA75B59474CD635B004D1F61
ungoogled-chromium-79.0.3945.117-2_polly.lld.windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.117-r706915-Win64/ungoogled-chromium-79.0.3945.117-2_polly.lld.windows.7z
SHA1 377A7BCFD6664B5D2A78548AD388981000A1DA6E
I couldn't use web push notification.
In particular comment: https://github.com/bromite/bromite/issues/464#issuecomment-574037539
Thanks.
Thanks for uploading the missing file. I haven't a chance to test yet but I'm sure it works fine. Swiftshader missing probably doesnt affect many users anyhow but I use it so appreciate the support. And of course thanks for continuing to supply ungoogled-chromium builds!
I wonder if the Chromium daily builds (from Chromium team) were built with proprietary codecs enabled would users be tempted to sway from Chrome? I understand there are probably license reasons for them not building without, but can't help think it is a way to keep casual users away. I do recall Chromium used to be able to use ffmpeg dll to resolve this easily, I see they stopped that though...
Thanks again.
Build box is churning through other build updates to resolve my bookmark bar modification I missed in some recent builds.
----------------
@marmaduke Excellent. Glad to hear the source edits work for ELF and WASM in LLD, too.
Can you share your code’s modification about bookmark’s bar on pastebin ?
In any case, thank you for your responsiveness and the huge density and celerity ( thanks to a Ryzen 9 3970x ? 😉💪 ) to you for release builds!
Am using a Samsung galaxy book 2 with Windows 10 ARM 64
I found a Chromium build (79.0.3943.0) created for Windows ARM64 on GitHub
https://github.com/brion/chromium-win-arm64/releases
Am browsing on it now :)
Please consider listing a Windows ARM64 build on the site.
M
@Anon5450: Here, all "sync" versions support AVX2.
@Mark: Mark, thank you very much for your help but please read my note at #windows-on-arm
============
No Sync - WebRTC - Widevine - All Codecs - ThinLTO - Ungoogled
Polly optimized native/target clang/clang-cl/clang++/lld all levels.
- - GNU/Linux cross-compiled (Linux host, Windows target)
- - clang/llvm 11.0.0-llvm-project-546f8f426463c7c22a3a8731803a501ff044ba20 (18 Jan 2020)
Ungoogled-Chromium-79.0.3945.130-Polly.Win32.7z (32-bit)
https://github.com/macchrome/winchrome/releases/download/v79.0.3945.130-r706915-Win64/Ungoogled-Chromium-79.0.3945.130-Polly.Win32.7z
SHA1 FA30AD3B7CE4855AC9E7E336AA4969BCEC4F907D
===
Faster than the non-polly version! and a bloody pain to build!!!
" ... and a bloody pain to build!!! ... "
And our infinite thanks from all the users here present for continuing to suffer for us.
You are something like the Chromium’s Jesus Chirst for us!
----------------
D:\depot_tools\chromium\src\chrome\browser\ui\views\bookmarks\bookmark_bar_view.cc
static const int kBookmarkBarMaxButtonWidth = 100;
static const int kBookmarkBarHorizontalMargin = 0;
----------------
D:\depot_tools\chromium\src\chrome\browser\ui\views\chrome_layout_provider.cc
case DISTANCE_RELATED_LABEL_HORIZONTAL_LIST:
return kHarmonyLayoutUnit / 4;
----------------
@marmaduke Yeah, the lax vector conversions bit me earlier today. Landed Wednesday, but apparently it dates all the way back to a bug that *Agner* reported back in 2013. o.0
Thank you for new Ungoogled Polly 32bit ; it works really very very well.
:)
@RobRich and Hibbiki
Thank you too ; for keeping old 32 bit always uptated.
:)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4032.0-r733187-win64-sse2
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4032.0-r733187-win64-avx2
-------------------
For those experiencing a bookmark bar issue with my latest Win64 SSE2 build, I have pushed updated files with the needed fix. Same link as before.
im looking for this because ive used --disable-encryption flags before and still it removes my extensions when i run chromium on other pcs.
The stable Builds here from "Hibbiki" and "Marmaduke", Brave, Vivaldi and the new Edge - all these browsers were updated on the same or next day.
Of the renowned companies, only Opera is once again not able to deliver - to the potential harm of the user.I think this is so important for the choice of browser that all the frills Opera offers become unimportant.
While Meghan, aka as Mummy, was eating her drought and murder fuelling advocado on toast this morning, she read this article to me:
What is going on at Opera Software?
https://www.nsaneforums.com/topic/362767-what-is-going-on-at-opera-software/
Mummy would also like to take this opportunity to apologise to Princess Charlotte for nealy killing her with a bouquet of flowers. For not crossing her legs properly; for being the wrong colour; for being a gansta from Compton; and for not appreciating Princess Michael's golly wog themed jewellery.
This stuff is more real than the contents of my nappy: you could not make it up.
My parents are dysfunctional, so I have decided to transition.
Arabella
Look:
https://en.wikipedia.org/wiki/Abandonware
Nothing in options changed, straight outta box Chromium from Installer.
I don't use Windows 10 so "Default App Mode" is not existing in my system. "Light Theme for Google Chrome" You recommended fixed it for me. Better than default skin and without bugs. Interesting fact that I cannot find any way to menage themes, there is only a link to Chrome Web Store inSettings or Defaults option which delete them all. I cannot find any chrome:// shortcut either. Wired.
https://blog.pcrisk.com/general-information/7734-remove-chrome-extension-installed-by-enterprise-policy
Portable Chromium ungoogled for 64-bit Linux - Wednesday, 22 January 2020
- Ungoogled - https://github.com/ungoogled-software/ungoogled-chromium-portablelinux
- Built on Debian (9) Stretch. Custom Kernel 5.3.4
- Default Chromium compiler used
- Bog standard test build - if possible will add HEVC and Polly optimize clang/lld
- Install instructions in README
ungoogled-chromium_79.0.3945.130-2_linux.tar.xz
https://github.com/macchrome/linchrome/releases/download/v79.0.3945.130-r706915-portable-ungoogled-Lin64/ungoogled-chromium_79.0.3945.130-2_linux.tar.xz
SHA1 015C10C31F64C6F490F81BA966B1CBD71B768A31
==
Only built this because I like the ungoogled Linux build process! Plus, the fact that I think that Linux is an excellent development platform, but a poor desktop operating system, and would be mightly surprise if this build actually works outside of my build environment!
Negative feedback greatly appreciated so that I can abandon this build.
ungoogled-chromium_79.0.3945.130-2.codecs_linux.tar.xz
https://github.com/macchrome/linchrome/releases/download/v79.0.3945.130-r706915-portable-ungoogled-Lin64/ungoogled-chromium_79.0.3945.130-2.codecs_linux.tar.xz
SHA1 082B9510B6267DA25CB9B99A8B7FAA4AFDC9BFCB
Surprisingly smooth in operation under a VM.
You're doing it wrong, plop this two flags on ungoogled-chromium:
--disable-machine-id --disable-encryption
Works on my end, this version https://github.com/macchrome/winchrome/releases/download/v79.0.3945.130-r706915-Win64/ungoogled-chromium-79.0.3945.130-1_windows.7z
Just want to say thanks for your ungoogled mac and windows builds with all the codecs and widevine support - exactly what I need in a browser! Any way we can donate?
Appreciate it! An AMD 3950x with 126 Gb of Ram would be nice.
But realistically, It would be nice if Google would pull their finger out and develop a decent (local) distributed build system. V79 is the last of the Jumbo builds.
===========
==========
- Polly Optimized & All CODECS
- Make sure only one locatable instance of Widevine is installed (...next to main binary is the desired location!!!!)
- Custom build of default Chromium compiler. (Chromium Linux is compiler sensitive)
if (!is_debug && use_thin_lto && is_a_target_toolchain) {
assert(use_lld || target_os == "chromeos",
"gold plugin only supported with ChromeOS")
cflags += [ "-flto=thin" ]
if (target_os != "chromeos") {
cflags += [ "-fsplit-lto-unit", "-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
#"-Xclang", "-Rpass-analysis=polly",
#"-flax-vector-conversions=all",
]
ungoogled-chromium_79.0.3945.130-3.polly_linux.tar.xz
https://github.com/macchrome/linchrome/releases/download/v79.0.3945.130-r706915-portable-ungoogled-Lin64/ungoogled-chromium_79.0.3945.130-3.polly_linux.tar.xz
SHA1 E5806653BF5A91D8644E66F19A52C9A7683E64DC
I am also unable to install the chromium web store extension, but I can't tell if this is a browser issue or an extension issue.
The project itself already produces multiple dev builds daily, assuming that is something one really needs for whatever purposes. They are generic stock builds, but they still are quite usable and generally stable in my experience. I used them for a long time before starting to build and modify my own.
----------------
@marmaduke I have been seeing more public work and commits on distributed ThinLTO for LLVM, so maybe there will be something available to help distributed building in the near to intermediate future.
----------------
Speaking of building, there is work to (optionally) integrate rpmalloc into LLVM on Windows. Apparently the MS VS CRT allocator is causing extraneous thread blocking during ThinLTO codegen due to heap locking. The rpmalloc allocator uses a " lock free thread caching" design.
There also is a proposed modification to the thread pooling strategy for Windows due to how the OS assigns "processor groups" on systems supporting more than 64 concurrent threads. Suppose that one might be awhile at least for me, seeing as I am still building on my aging 32-core Opteron box.
yeah i know but im not using ungoogled chrome. its 2 version older than current (79 vs 81).
and that flags are not working. my extensions are always removed on another pc.
Look:
This floating popup loose styling sometimes, after logging in from sleep mode when browser is running. After browser restart it's fine again.
I really think the Chromium Authors are trying to dissuade the average person from building Chromium and seeing the fundamental inadequacies in the the code base: a 32-bit clang 11.0.0 lto/polly clang/lld build exposes at least 4 possible vectors of attack!
@Anon5484
I just engage developer mode and sideload; works wonders in Linux drag and drop and sideload. I don't use webstore at all.
@Anon5489
Go to https://github.com/macchrome/winchrome/releases/tag/v79.0.3945.130-r706915-Win64 and compare the 32-bit builds, different compilers but I think the polly build is state of the art: I enjoyed the challenge of building it.
Thanks. Your previous comment pointed out non polly being 'faster', not sure if you meant faster to build or usage benchmarks. Either way I will give them a try. Also, any idea why polly builds are noticeable larger in size?
I found this official portable version of opera
https://www.opera.com/computer/portable
haven't found anything for google chrome or firefox yet
i checked that url web site and it was reported to have malware and ransomware in all the downloads on
https://www.virustotal.com/gui/home/
on portables web site you can click antivirus scan and it goes to virustotal's web site all of the portable browsers there are infected for chrome and chrome dev and firefox etc so i didn't risk downloading or opening
I wanted
https://portableapps.com/apps/internet/google-chrome-portable-dev
https://www.virustotal.com/gui/file/f73ba0d3783972db79663163e512ef483360279cd6e2ec27fbccf930dc44410d/detection
kinda of why i was looking for official versions not sure why no one but opera has a official portable version
Also: https://virusscan.jotti.org/en-US/filescanjob/1d97v1ftql
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4039.0-r735249-win64-sse2
I went with this one as it had zero false positives on chrome firefox edge all versions
https : // www . g hacks . net /2019/03/13/chrome-portable-updater-for-windows/
i like how user friendly it is and how accessible it is the tiny app and everything you would ever need for installer and updater
and jotti only claims it is clean because only 15 company's scanned the files there vs the 68 plus company's at totalvirus scanning files and the company's that claimed it is infected are not at jotti
and it was portableapps . com that recommended totalvirus i didn't even know totalvirus existed prior #malware
i don't know these company's so how do i know they are reliable sources? hence the second opinion at anti virus providers
https://en.wikipedia.org/wiki/VirusTotal
Hi. Can you update Ungoogled for Android ?
Thanks.
Hi. Can you update Dev for Windows ?
Thanks.
Updated Windows Dev version will be released when v82 is.
=======
Chromium 79.0.3945.139 (Official Build) (64-bit)
Revision cd3a886c28f57603dea2a9050d2aadef3e8c30a4-refs/branch-heads/3945@{#1070}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9 & 10
- Official build
- All Bromite patches applied
- HEVC and AV1
- "No Search" option (Replaced Google search engine with no search)
- Domain substitution, tracking and blocking (Now standard on Bromite!)
- CFI & LTO
- No menu option to toggle global Javascript (Feature has sadly been removed)
No Sync • No Widevine • ThinLTO • CFI • Bromite • HEVC
arm64_MonochromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v79.0.3945.139-r706915-Ungoogled-And64/arm64_MonochromePublic_HEVC.apk
SHA1 9F008B5869E5ACA4EDCC8BFA88132866B2240377
Thanks a lot for the update of Ungoogled for Android. :)
Regards.
8 out of 12 months scheduled for 2020
https://www.chromium.org/developers/calendar
so 7 builds left will be posted here for 2020
https://support.google.com/chrome/a/answer/9027636
this says 9–12 week preview but is actually that far behind here
new to web site only been around for maybe three builds future here looks bleak
The 82 dev branch point will be around Feb 4, 2020. the bias has to be towards the ungoogled stable branch. RobRich releases regular updates to the dev branch.
You know, some developers aren't mongs who spend 24/7 at the computer; we like to drink malt whisky, catch-up with friends and fix the garage roof. All while raising our little sprogs to be good, decent, fair minded and understanding future adults.
We have a life!
Batwoman
stable is on the google stable channel
Version 81.0.4033.2 (Official Build) dev (64-bit)
is dev?
https://chromium.googlesource.com/chromium/src/+/refs/tags/81.0.4033.2
this is canary? like the other one as well
https://github.com/RobRich999/Chromium_Clang/releases/tag/v81.0.4039.0-r735249-win64
I have tried RobRich's builds before they do not run properly on my pc
official four google builds run fine on my pc though
if the browser developers were upfront and forthcoming and provided information about when updates would be provided i and others would not be posting here all the time about updates this seems handled as well as the early access crapware on steam
https://it.wikipedia.org/wiki/Crapware
https://translate.google.com/
https://en.wikipedia.org/wiki/Early_access
the browser has not been updated in over 7 weeks and still counting and your giving me lip go f u c k y ou r se l f
Cheers! :)
Auto-update, add this F-Droid repo: https://www.droidware.info/fdroid/repo
Thanks for the great chromium build. I'm really enjoying having hevc/h265. One thing that bothers me is that while the browser can play a lot of formats, they're not reported as supported by MediaSource.isTypeSupported or canPlayType. This means that sites won't know that the browser can actually support these formats. Do you know how this could be added? If you share your build scripts I will see if I can maintain a fork of Chromium that correctly reports all-codecs+.
"The browser in question "knows best" what formats it can use."
https://en.wikipedia.org/wiki/HTML5_video
Ciao.
I have found an issue with the Mac versions of Chromium ( I tested v73,74,76,79,81 ) that makes the page crash when attempting to play normal videos (videos already supported by Default Chromium). sync, no-sync, wildvine, all have the same issue ( all-encode versions ).
This is not an issue with default Chromium as it can play them fine -- where should I post the issue?
Version 69 and 70 (all-encoded versions, no-sync) seem to be un-affected by this issue and can play normal videos fine.
I spent a few days debugging the issue but didn't get much headway. It may have something to do with Very Simple Backend (ref: https://www.chromium.org/developers/design-documents/network-stack/disk-cache/very-simple-backend) but not entirely sure.
Here is an example video that will make the page crash every time when trying to play on a Mac (10.13.6) with all-encode Chromium v74+ (https://www.youtube.com/watch?v=Gu2pVPWGYMQ).
Windows versions does not have this issue. Didn't test linux.
Checked: macOS 10.13.6 (17G65)
81.0.4043.0 (SDK 10.15)
80.0.3962.0
78.0.3904.108
79.0.3945.130
No issue, video/soundtrack plays OK.
https://en.wikipedia.org/wiki/Trunk_(software)
My builds should work about the same as any other trunk builds, with two potential caveats:
1. Systems without AVX instruction support will not run my Win64 build posted in the listings above. I offer an SSE2 build at Github as a legacy support alternative for such systems.
2. My Win64 builds might not play too nice with low-memory systems and/or low-power processors with small caches. I build at much higher optimization, instruction import, and inlining levels than the default project, thus the code size can be considerably larger.
----------------
If unsatisfied with available options, one could always just do their own builds. Chromium actually is one of the easier large software projects to build assuming no source modifications. The project even bundles the compiler, linker, build tools, etc.
It is not my idea of fun, but Chromium even should build without LTO on a somewhat modern quad-core processor system with just 8GB of memory. Figure more like 16GB for a LTO build.
Admittedly I do most of my builds on a 32-core Opteron box with 64GB memory, enterprise-class SSDs, etc., but I do my Win64 AVX2 builds on a Kaby Lake quad-core notebook with 16GB of memory.
----------------
Straightforward, and I suspect I can say the same for Marmaduke and other builders here: I do not work for Google. I do not actively participate in Chromium development for any company, organization, etc. I do not even have an @chromium email. Other than the newly listed Windows ARM build, this is a hobby for most (all?) of us here.
----------------
Speaking of Windows ARM, I would not mind trying it, but frankly where are the usable systems? I do not need yet another tablet, and I can about imagine how "well" it likely runs on a Raspberry Pi. o.0
Otherwise, outside of Windows land, I have thought about maybe a PPC64LE box. Raptor is porting Chromium to the architecture. :)
logs collected just before crash:
dtruss (dtrace): https://pastebin.com/5tKyQy8Y
--enable-logging gist: https://gist.github.com/talmobi/667af5c386383b59cff8da3c285b1ed3
without flags stderr just prints this before crashing/exiting:
[0130/221650.848772:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffeea44c000, 0x2000): (os/kern) invalid address (1)
(If you see a post from me saying it was fixed after updating OS then that's wrong: I thought it was fixed after OS update but I was testing with default Chromium version instead of an all-codecs Chromium.)
Not sure how to help debugging this issue further? Thank you for your time hopefully I can be of help. I'm surprised it can't be reproduced as it's consistent on both of these laptops.
No-sync Chromium 79.0.3945.130 was built under macOS 10.15.3, using xcode 11.3.1, the respective SDK 10.15, and the default Chromium clang/llvm: an advanced build environment (soft links were used to make sure that SDK 10.15 was actually being used). I would say my builds are more orientated towards the Hackintosh community.
Download the video clip in question - using youtube-dl - and analyse it. As stated previously, I have no issue with the video still and soundtrack in question. If you feel that my all-codecs version of Chromium for macOS is sub-par, let me know: I will delete the github Mac archive and cease to release any public Mac builds.
-------------------------
Substitute 79.0.3945.130 for 81.0.4043.0.
To be blunt, provide more samples of mal-functioning video a 240p video still/audio of Creedence Clearwater Revival does not really move me.
Try disabling hardware video decoding as a starting point for diagnosis:
chrome://flags/#disable-accelerated-video-decode
Also, do you have any anti-malware utilities installed? Something that might interfere with memory accesses, like running with an extra layer of sandboxing, a VM environment, or similar.
Hello,
Sorry I did not mean to come off as disrespectful.
Debugging this issue is a bit over my head and I'm not sure what to do next really. What tools to use to debug etc.
However, I tried the all-codecs no-sync version 81.0.4043.0 and it works perfectly fine! I double checked and version 79.0.3945.130 still does not work -- even in the beginning it prints some errors:
[20877:51971:0131/040940.824326:ERROR:database.cc(1584)] Web sqlite error 1, errno 0: no such column: type, sql: SELECT card_number_encrypted,
last_four,masked.id,metadata.use_count,metadata.use_date,network,type,status,name_on_card,exp_month,exp_year,metadata.billing_address_id,bank_name FROM masked_credit_cards masked LEFT OUTER JOIN unmasked_credit_cards USING (id) LEFT OUTER JOIN server_card_metadata metadata USING (id)
and page crashes on the video with the same:
[0131/040946.171549:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffeee9d4000, 0x2000): (os/kern) invalid address (1)
But starting 81.0.4043.0 prints nothing to stderr and works perfectly fine.
I did actually use ytdl to download the video and try it out -- the actual video/audio playback works fine in the all-codec Chromium versions (e.g. dragging the video over to the browser or local url to the address box) -- this is what lead me to think there were some caching/state issues that was going a bit haywire. In other words it doesn't seem to be a codec issue.
I'm surprised 81.0.4043.0 works because I don't really have any idea what's going on nor do I know where to learn more about it.
Made a small screen recording demonstrating the success case of version 81.0.4043.0 ( the video audio works but you can't hear it in the recording ) and the failure (page crash) case of version 79.0.3945.130
screen recording: https://www.youtube.com/watch?v=lk1lVkepTlE
To re-iterate on macOS 10.13.6 (17G11023) and no-sync all-codec Chromium 81.0.4043.0 the video plays fine on YouTube. With 79.0.3945.130 it has the same issue as before.
Perhaps there's a better place for these kinds of discussions that you could recommend?
I think what you're doing, and all this, is very cool but it's a bit over my pay-grade at the moment so I don't have much intelligent input. I mean no disrespect. Thanks~
----------------------------
@RobRich
Hello,
Indeed disabling/enabling many features through cli flags was one of the first things I tried to do gpu and hardware acceleration/video encoding among the first I tried. Spent around 1-2 days on that. Nothing worked however, which was surprising. Then later I started going through older versions and 69 and, was it 71, that worked fine. But, the new version 81 works just fine without any errors or page crashing -- which is cool -- but I still have no idea what's going on.
Try this:
No Sync • WebRTC • No Widevine • cfi • thinLTO • Polly
Chromium.81.0.4043.0.nosync.polly.app.zip
https://github.com/macchrome/chromium/releases/download/v81.0.4043.0-r736331-macOS/Chromium.81.0.4043.0.nosync.polly.app.zip
SH1 03505ADB694B7C529F31C41775FE8500E50C1F35
Build details at:
https://github.com/macchrome/chromium/releases/tag/v81.0.4043.0-r736331-macOS
I think, I actually know what the issue is and would be surprised if this build were to work on your system. Basically, Apple's ld64 linker is crap and clang/llvm can't be bothered to cover for Apple's inadequacies.
Hello, and thanks for helping out~
Hmm, interesting.
Firstly the "Chromium.81.0.4043.0.nosync.app" like I said before, it works PERFECTLY. It plays default videos (that doesn't need extra codecs like h264) and it also plays videos that require the extra codecs. I've tried it many times it always works perfectly.
YouTube video that does not need extra codecs : https://www.youtube.com/watch?v=Gu2pVPWGYMQ
YouTube video that REQUIRES extra codecs : https://www.youtube.com/watch?v=pFbkURxNKPE
However, this new version that you just linked "Chromium.81.0.4043.0.nosync.polly.app":
1. It does not start with any output to stderr like version 79 and the rest does
2. It plays videos that does not need codecs (https://www.youtube.com/watch?v=Gu2pVPWGYMQ) ( that default Chromium can also play )
3. However, it >>>USUALLY<<< Page Crashes on videos that requires the all-codecs codecs (https://www.youtube.com/watch?v=pFbkURxNKPE)
4. After it Page Crashes then it starts to crash on normal (non-codec required videos) also.
The >>>USUALLY<<< part is truly confusing. I thought it worked fine at first, but then no after a few more tries.
Error Code: RESULT_CODE_UNINSTALL_USER_CANCEL:
So that's interesting and weird -- hopefully that is useful information.
It did not report any sqlite or any other stderr's on start, it just page crashed with the familiar:
[0131/075757.942220:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffeed3d1000, 0x2000): (os/kern) invalid address (1)
Except this time it does it on videos that requires the codecs, but not the normal videos ( at first ) -- so normal videos play fine on this version, but videos that require the codecs (that default Chromium can't play) will USUALLY make it crash. In fact I'm having a hard time getting it to work at all with those videos ( https://www.youtube.com/watch?v=pFbkURxNKPE ) now after many tries. In the beginning it worked a few times.
https://www.youtube.com/watch?v=pFbkURxNKPE
It even runs incorrectly on Firefox 72.0.2 on Windows 10 1903. It won't be the only one on YouTube.
The Chromium git checkout, as RobRich stated, is bundled with its own tools: the default compiler llvm/clang 11.0.0. I build with 8.0.1 because the bitcode produced is fully compatible with Apple's linker and polly capable.
Chromium.81.0.4043.0.nosync.app is a default build: default compiler, no polly, no cfi. The instability, in Chromium.81.0.4043.0.nosync.polly.app.zip, is related to the use of polly optimization, but specifically to memory allocation: refer to point 2 in RobRich's penultimate post.
My basic Chromium Hackingtosh test system is quite primitive: macOS 10.15.3, Dell Optiplex 780, C2D E8500, 8Gb of RAM, and a 1 Gb Nvidia Geforce 210 (with HDMI audio!).
Chromium.81.0.4043.0.nosync.app is the first default build that I've done for a long time, which I did to assses the impact of the removal of jumbo on build times.
Your feedback has been informative, and in the future I might restrict my all-codecs builds to the default build process. I actually know where the problem is!
Chromium.81.0.4043.0.nosync.polly.app.zip (and the latest stable builds) is a component ffmpeg build. The code has been thinLTO and polly optimized at all levels, the resulting integral ffmpeg failed to link, hence that is why I did a component build. The link-time error message is quite informative. instead of working around the error I should endeavour to solve it.
=================
src/third_party/ffmpeg/BUILD.gn
=================
if (is_win) {
# Setting the optimizations to 'speed' or to 'max' on Windows results in
# a lot of unresolved symbols. The only supported mode is 'size' (see
# crbug.com/264459).
#
# FFMmpeg require dead code elimination to be available in all build modes
# and thus doesn't support wpo.
configs += [ "//build/config/compiler:optimize_no_wpo" ]
} else {
configs += [ "//build/config/compiler:optimize_max" ]
}
==================
This Greta-esque nonsense accounts for the problems that I had when optimizing ffmpeg! (In Windows builds, I solve the unresolved (lto) symbols and polly optimise at /O2.)
Anyway, I've edited ffmpeg_internal.ninja so that polly and thinlto is not applied to ffmpeg, which results in a successful integral ffmpeg build:
Chromium.81.0.4043.0.nosync.polly.FIXED.app.zip (internal ffmpeg)
https://github.com/macchrome/chromium/releases/download/v81.0.4043.0-r736331-macOS/Chromium.81.0.4043.0.nosync.polly.FIXED.app.zip
SHA1 C9EDA0B84E8A4BB76CB600008E4BFDC1BF9A8877
I doubt if this version will run on your Mac Book: I think your problem might be due to a lack of memory.
As long as feasibly possible, I will build Chromium Mac stable with clang 8.0.1, polly and thinLTO.
if (is_mac) {
if (is_component_ffmpeg) {
# Export all symbols when building as component.
configs -= [ "//build/config/gcc:symbol_visibility_hidden" ]
configs += [ "//build/config/gcc:symbol_visibility_default" ]
}
Explains why the component build builds. I prefer to use thinlto, which ordinarily implies cfi https://clang.llvm.org/docs/ControlFlowIntegrity.html , which requires fvisibility=hidden; therefore (given the build tools at my disposal) it is not possible to thinLTO the internal build of ffmpeg: instead I've settled for -O3 and polly optimization.
Chromium.81.0.4043.0.nosync.codecs.polly.FINAL.app.zip (internal ffmpeg: -O3 polly optimized)
https://github.com/macchrome/chromium/releases/download/v81.0.4043.0-r736331-macOS/Chromium.81.0.4043.0.nosync.codecs.polly.FINAL.app.zip
SHA1 6CC5D73B6EFE4D7E840B1761865B930BC9846C8B
The component ffmpeg builds are perfectly acceptable: -O2, thinLTO, cfi and polly.
Hello, with testing this new version I discovered some FALSE INFORMATION in my previous comment.
Thanks for such detailed information! This is kind of exciting, I'm going to try and mess around with a build myself with the help of your previous guidelines after/during this.
But firstly, to re-iterate, the "Chromium.81.0.4043.0.nosync.app" has none of these issues and they work perfectly fine on all cases including the one's I'm detailing out below.
Now, this new version "Chromium.81.0.4043.0.nosync.polly.FIXED.app" ( >>>BUT ALSO<<< the previous "Chromium.81.0.4043.0.nosync.polly.app" ) they both actually play the normal ( https://www.youtube.com/watch?v=Gu2pVPWGYMQ ) and all-codec required ( https://www.youtube.com/watch?v=pFbkURxNKPE ) videos PERFECTLY!
HOWEVER, they crash when attempting to play SOME of the >>ADS<< that appear before the video is loaded. Certain ADS don't make it crash and if I refresh the page and no ads show up -> the video plays fine.
I'm not sure how YouTube decides to show ads but sometimes the same ad keeps showing up every refresh which causes the page to crash every time.
I'm having a difficult time creating a consistently reproducible setup. The best I've got at the moment is keep refreshing the page until the ads show up. Most of the time before the page crashes, I can see the first image/thumbnail of the ad before the page crashes -- this is how I can identify which ads causes the crash.
I will then use the working version "Chromium.81.0.4043.0.nosync.app" to find the same ad ( basically I keep refreshing the page until it shows up ) and then inspect the DOM to see if I can find a way to reproduce that ad, or what the issue with it is, so that we can reproduce it consistently.
Using incognito and a VPN to change ip addresses just re-rolls the ads I get and most of them seem to work and load fine.
Also >>IMPORTANT SIDE NOTE<<: This is only for these two versions -- the other versions e.g. "79.0.3945.130.nosync.app" crash on actual normal video playback ( https://www.youtube.com/watch?v=Gu2pVPWGYMQ ).
When I run these last two Chromium versions ( "Chromium.81.0.4043.0.nosync.polly.FIXED.app" and "Chromium.81.0.4043.0.nosync.polly.app" ) with a custom request interceptor ( https://chromedevtools.github.io/devtools-protocol/tot/Fetch#method-enable ) to BLOCK ALL ADS from loading ( aborting request urls matching against easylist.txt ) then basically everything works perfectly because none of the ads are loaded that might make it crash -- but blocking ads in version "79.0.3945.130.nosync.app" has no effect since the normal video ( https://www.youtube.com/watch?v=Gu2pVPWGYMQ ) is causing the crash (ads ALSO cause crashes on these versions &[1]).
I'm using puppeteer to attach the custom request interceptor through the DevTools Protocol ( it's not an extension or anything ).
Interestingly "79.0.3945.130.nosync.app" is able to play codec required videos ( https://www.youtube.com/watch?v=pFbkURxNKPE ) but it ALSO CRASHES on certain ADS [1] ( in addition to crashing when trying to play normal videos like https://www.youtube.com/watch?v=Gu2pVPWGYMQ )
This should mean that these latest two versions ( "Chromium.81.0.4043.0.nosync.polly.FIXED.app" and "Chromium.81.0.4043.0.nosync.polly.app" ) have fixed the issue of crashing when playing normal videos (on YouTube that is, playback seems to work fine on pure/local videos in all versions) -- but they still crash when certain ADS show up.
Why? I don't know -- Is it a codec thing? Are ads encoded in some funky arbitrary way/format? Or is it some funky way that ads are loaded into memory/cache on YouTube? It doesn't seem to happen on every ad, but on some of them. Trying to find out at the moment ( have been gathering info into this post the whole day so far ).
To begin with here's a cursory list of the ads and their thumbnails that cause page crashes:
Oreo Ad
Grammarly Ad:
Another Grammarly Ad:
Not all Grammarly ads crash, though, but those two seem to always crash.
These make the page crash almost immediately when they are loaded (not even playing yet) -- Sometimes you can see the thumbnail of the ad before the page crashes, but not always.
Then there are other ads that seem to work FINE without any issues like the HBO Nordic Chernobyl ad (https://i.imgur.com/fPTeRCP.png) and many other ads.
I'm having a tricky time figuring out how to get access to/download those ad videos to see if it's a codec thing or not. But my suspicion is that it's not a codec thing, but rather something to do with how the browser handles caching/memory (because pure videos seem to play fine on all versions, it's only when they are played in YouTube that seems to be an issue).
I'm not finished debugging yet but I'm going to post this what I have so far and grab some coffee and stretch my old bones.
Happy to discuss in other places also ( irc/slack/discord/email/twitter/etc ) if this format is insufficient. My username on github/twitter is talmobi and my email is visible on github.
I use DNSKong (HOSTS blocker, old but fuctions under 10.13.6), Pi Hole (at a network level), Hands Off! firewall, uMatrix and uBlock Origin to block adverts, scripts and general securiy.
Also, if you have not done so already try: https://tools.woolyss.com/html5-audio-video-tester/ Scripting and cookies not required. And try the FreeSmug version of Chromium.
Just raise an issue on my github. I'll reply eventually! This board is more immediate, but I realise probably not the appropriate place to discuss this type of issue.
Hello, thanks again for helping~
For daily use I indeed block ads and use a few tools, not as many as you pointed out however -- I'll have to copy some of that over for myself. Editing the hosts files is a pretty neat trick -- I wonder if the websites can detect such ad-locking ( as sometimes they detect uBlock and prevent you from seeing the page )
That said my main interest here is just the bug itself, not necessarily how to prevent the bug from happening for myself. Although for my intended use-case I would be able to pre-install my desired version of Chromium that I could set to block ads etc. I have a completely unnecessary side-project that plays YouTube videos from the terminal using an embedded headless Chromium, which is how I've stumbled upon these issues.
I did check those pages but I didn't actually test every single video on there individually, not sure why I didn't actually, I just looked at the overall capabilitles (green vs gray), these are the results I found:
These two videos make the page crash on "Chromium.81.0.4043.0.nosync.polly.FIXED.app" and "Chromium.81.0.4043.0.nosync.polly.app"
nandes-1-llama-drama-av1-opus-480p.webm AV1 Main@L3.0 Opus wikipedia.org webm
( https://tools.woolyss.com/html5-audio-video-tester/?u=https://woolyss.com/f/caminandes-1-llama-drama-av1-opus-480p.webm )
bear-av1.webm AV1 Main@L2.0 (no sound) github.com webm
( https://tools.woolyss.com/html5-audio-video-tester/?u=https://github.com/chromium/chromium/raw/master/media/test/data/bear-av1.webm )
They also cause crashes on "79.0.3945.130.nosync.app"
However, in "Chromium.81.0.4043.0.nosync.app" they also show up as gray (and not green) on the page but THEY BOTH WORK and play fine (and they don't make the page crash).
All the other videos or audio files work fine on any of these verions.
In "Chromium.69.0.3497.81.nosync.app" these two videos load but don't play -- they DON'T MAKE the page crash, though! stderr spits out these:
[36085:27395:0201/060946.817991:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"video decoder initialization failed"}
[36085:775:0201/060946.834905:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
The FreeSMUG version "Chromium_OSX_79.0.3945.130" can play those two files perfectly fine -- but there are a bunch of other videos it can't play at all -- like all h264 videos etc -- however, it does not crash when trying to play those videos, it just doesn't play them, stderr spits out:
[36261:35075:0201/062159.688460:ERROR:batching_media_log.cc(26)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: no supported streams"}
[36261:775:0201/062159.688670:ERROR:batching_media_log.cc(26)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_NO_SUPPORTED_STREAMS
Is the issue as you suspected, or does this tell you something new?
Thanks again~
The polly builds are just not compatibe with your system.
@@@ I would appreciate feedback from other Mac users regarding polly video playback: use Jerry's audio.tester.
=======
Solved the ffmpeg lto issue: use full lto instead of thin.
ldflags += ["-flto=thin", "-fvisibility=hidden", "-fsanitize=cfi", ]
config("optimize")
config("optimize_no_wpo")
config("optimize_speed")
config("optimize_max")
config("optimize_ffmpeg") Same configuration, but "-flto=full" for cflags & ldflags
common_optimize_on_cflags += [
"-flto=thin",
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
#"-Xclang", "-Rpass-analysis=polly",
]
No Sync • WebRTC • No Widevine • cfi • thinLTO • Polly (internal ffmpeg: polly, cfi, full lto)
Chromium.81.0.4043.0.nosync.ULTIMATE.app.zip
https://github.com/macchrome/chromium/releases/download/v81.0.4043.0-r736331-macOS/Chromium.81.0.4043.0.nosync.ULTIMATE.app.zip
SHA1 15B97BC837506A6023995C7D3F013DE4DF29B0CB
Is it plausible that it could be an Intel HD 5000/6000 related issue? Since the issue exists on both MacBook Airs that I have access ( Intel HD 5000 and 6000 respectively ).
I tested on a mac mini server at macincloud.com and didn't have playback or crashing issues on the aforementioned two videos.
No lto or polly on dav1d (AV1)
Chromium.81.0.4043.0.nosync.dav1d-no-polly.app.zip
https://github.com/macchrome/chromium/releases/download/v81.0.4043.0-r736331-macOS/Chromium.81.0.4043.0.nosync.dav1d-no-polly.app.zip
SHA1 D1C62874971CFA843570A7BA12BDE122EC1D95C1
Would it be possible to incorporate a fix you mentioned a year ago into your builds:
"You can change the AccountConsistencyVariations field trial configuration when building Chromium to get Gmail working in a no-sync build.
https://www.pastiebin.com/5c2e43c24ff32
It defaults the setting to "dice_fix_auth_errors", which is apparently is no longer a selectable option in the about:flags options - just checked in a r619562 build.
----------------
Speaking of r619562, my Win64 build slated to go public today includes PGO optimization. Note, I am not profiling the entire browser, but I am instead profiling the code paths explicitly optimized for performance instead of size. YMMV, as fine tuning likely will be ongoing.
I also enabled AVX across all optimized code paths, so naturally, a processor with AVX support is now required."
That version works for the two videos on the tools page as well as for the ads on youtube and also both of the youtube videos!
Basically it's perfect. Just as perfect as the "Chromium.81.0.4043.0.nosync.app" version is.
I tried marmaduke's ungoogled yesterday. It runs really well! First of all thanks a lot for the effort!
Using the addon Chrome Web Store I can install and update addons quite well.
But I would be interested to know which ungoogled chromium has e.g. opposite brave? Brave has supposedly also degoogled everything and an updater for the browser is already included. Also the Chrome Web Store works out of the box.
So the question why do you use the ungoogled?
chrome://settings/syncSetup
Disable the "Allow Chromium sign-in" setting, then you should be able to sign into Gmail and other Google services with a no-sync build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4049.0-r738416-win64-sse2
Brave has google spyware removed, but has it's own spyware implemented. Do not use Brave, use Ungoogled Chromium.
No compression applied on archive. Marmaduke's archives are created manually, not via official build target.
Rest assured however they are both similar in size after decompression.
Because Marmaduke's build (Archive .7z) is more compressed than that by Hibikki (Archive .7z). Unpacked is the size of M. 218 MB (77 files), that from H. only 186 MB (80 files).
Thanks for answer. It's hard to download 3x more on 512 kbps unreliable internet connection. I will stay with smaller builds.
chrome.dll and chrome_child.dll merged, are there any caching/prefetching nuances now that it's larger than 128MB in some builds?
>Is it expected or 7-zip was just lucky?
It is expected, it's how the installer is built.
Prefetching has not been an issue here, but admittedly, most of my Windows systems have SSDs. Otherwise, in theory it could cause a slight delay upon launching Chromium, but the project uses binary symbol layout optimization to help with load times anyway.
Since Chromium 79.0.3945.130 and now with Chromium 80.0.3987.87 on specific machines are present scrolling performance issues with a few seconds freezing, when links are opened in new tabs. I perform the test with clean profiles and no installed extensions with and without hardware acceleration.
I start to think that's probably related to polly parameters and the issue is CPU related, because the same branches on other machines are just fine.
I test the branches Chromium 79.0.3945.117 and Chromium 79.0.3945.88 which are the polly and non-polly win 64 versions and the issue is still there, which make me think probably is nothing to do with the polly parameters.
The branch Chromium 78.0.3904.108 polly win 64 is working properly on the affected machines.
I am not sure if that is related to your building process. I would like to do more tests.
How do you find building the Chromium 80.0.3987.87 branch?
https://github.com/henrypp/chrlauncher/issues/166
Your are looking for Chromium 80.0.3987.87 branch on Windows by Marmaduke ?
If so try ➜ https://github.com/macchrome/winchrome/releases/tag/v80.0.3987.87-r722274-Win64
https://github.com/w3ctag/design-reviews/issues/467#issuecomment-581944600
Hi. If possible can you update Ungoogled for Android to 80.
Thanks
Without looking into it...probably not applicable with field trials disabled
Polly and lto tend to bloat the code: on machines with low memory there might be problems. The respective build parameters are on my github and I must admit, that I'm more interested in the build process than the benefits, if any, of the various techniques of optimization. Occaisonally, I do produce standard and optimized vesions of the same build. So, if people want to contrast and compare they are welcome.
Recently, on the Windows stable builds, I've been polly optimising both the compile and link stages. The removal of jumbo in the build process has resulted in a substantial increase in the build time, so in terms of optimization, I might just stick to thinLTO and just polly optimise the link stage.
,
https://github.com/macchrome/winchrome/releases/download/v80.0.3987.87-r722274-Win64/Ungoogled-Chromium-80.0.3987.87-polly-Win32.7z
https://github.com/macchrome/winchrome/releases/download/v80.0.3987.87-r722274-Win64/Ungoogled-Chromium-80.0.3987.87-Win32.7z
https://browserbench.org/JetStream/
common_optimize_on_cflags += [
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
# "-Xclang", "-Rpass-analysis=polly",
]
common_optimize_on_ldflags = [
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-register-tiling",
# "-mllvm:-pass-remarks-analysis=polly",
"/defaultlib:C:/clang-9.0.0a/lib/clang/9.0.0/lib/windows/clang_rt.builtins-i386.lib", ### Don't forget this nasty little shit!!
]
The performance issue with a few seconds freezing of the mouse scroll, when links are opened in new tabs is specific to some affected machines and not to all. I personally thing is something to do with video cards performance or with the drivers for them.
Today I can confirm the issue is specific to Chrome since branch 79 and now with the latest version 80.0.3987.87 including, so is nothing to do with your building process. Sometimes I am surprise to see, how many new things the Chrome team is bringing and how many things are usually broken :)
How do you find the building process of 80.0.3987.87? Do you see anything specific, which can be connected to Manifest v3?
Check chrome://gpu, specially 'GPU0' and 'GPU1' under 'Driver Information. Swiftshader being there means software acceleration (better than none at all).
Also check the bottom of the page for errors such as 'EGL Driver message (Critical) eglInitialize: No available renderers.'
I notice with previous builds that acceleration wasn't being used, swiftshader in my case (marmaduke fixed it, big thanks to him), it has a big impact in browsing performance if no acceleration is used (software or hardware), such as audio stutters switching/loading new tabs.
Effectively polly is faster.
Thanx...
@Anon5565
Thanks for the TIP.
Personaly, l think that Chromium 79.0.3945.130 has achieved Firefox 56 status: a perfectly functioning wood toilet seat is about to be replaced with a vulgar gold plated one - literally dictator style. As in the inane decision to remove jumbo from the build process and replace it with absoultely nothing - excluding the substantial increase in build time, the increase in electricity consumption and the associated environmental emissions.
As for manifest v3: v80 contains elements.
https://www.ghacks.net/2019/11/13/google-implements-controversial-manifest-v3-in-chrome-canary-80/
https://developer.chrome.com/extensions/migrating_to_manifest_v3
Web browsers are standards based. Chromium v79/v80 could be used for the next 5 years without an issue.
------------------------
LLVM/clang COFF/ELF Polly Patch
Enables link-time polly optimisation.
Patch derived from: 11.0.0-llvm-project-546f8f426463c7c22a3a8731803a501ff044ba20
-DLLVM_POLLY_LINK_INTO_TOOLS=ON
-DCMAKE_POSITION_INDEPENDENT_CODE=ON
llvm.lld.polly.patch
https://github.com/macchrome/compilers/releases/download/v.002-polly/llvm.lld.polly.patch
SHA1 74837E70E6F94D8EED67CFB824DC4463D9F2AD02
Acknowledgement to RobRich.
Needless to say, this patch has been thoroughly tested in - the brutal and inhospitable - native and cross-compile environments in the production of compile and link-time polly optimise Chromium.
@marmaduke: Chrome has the vision to win the peoples and they did that :) Slowly then Google start to remove different functionality of the browser hiding behind security concern and manipulating the peoples.
I personally think with Manifest V3, Google finally will remove the peoples, which care for privacy. Of course, there are a lot other peoples, actually much much more, which they don't mind to be tracked and they like to be brain washed.
In our nature everything is about evolution and finding the way if is still there any. Google will apply the Manifest V3, doesn't matter what the peoples are thinking, maybe on few portions but they will achieve what they want, because in the end of the day, they are selling your information. This is what they do like a final product.
Talking about evolution maybe there will be other separate applications, which will work together with Chrome but they will have the vision to bring privacy in that browser. It's a bit messy in my vision :)
Personally I would like to see in what direction Firefox will go.
Marmaduke, do you thing the building process of Firefox is much different than Chrome?
What is your future plan if extensions like uBlock Origin are no more usable in Chrome? Do you thik you'll still spend your time in building Chrome?
llc --version will give a list of all architectures
Registered Targets:
x86 - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
llc -march=ARCH -mattr=help will list "available CPUs" and "available features"
eg. ./llc -march=x86-64 -mattr=help
if (is_win) { cflags = [ "/arch:AVX2" ]}
Place in approriate place
build/config/compiler/BUILD.gn
OR
build/config/win/BUILD.gn
https://clang.llvm.org/docs/ClangCommandLineReference.html
https://clang.llvm.org/docs/UsersManual.html
SuperRey - resistance is futile.
You're not the Messiah, you're a very naughty boy!
I think Google is an absolutely useless company: they are shit, they will never attain the exalted status of Linux, Adobe, VMware, Microsoft, Apple or LLVM/clang. Google is a bottom feeder, second only to Amazon. Google are so crap that no one would be bother to pirate its software.
In honour of Google's utter uselessness, I pledge to update my build system to be Ryzen 9 based. Regardless, I will always build Chromium on all the platforms that I use. I really don't think Google realise the contempt that developers hold them in.
Really, I would rather spend my money on whisky and cars.
Anything of particular interest or change in the v82 release? I think that even the nightly version of Brave is only built on v80.
Thanks for taking the time to keep doing what you do!
https://github.com/RobRich999/Chromium_Clang
Baseline target is the default LLVM x86-64 options modified with AVX2 and FMA added. I modify the processor modeling to Skylake, since it is the closest to the Kaby Lake in my primary system. Anyway, it should be "okay" on Intel Haswell or later.
The bigger issue is AVX2 and even FMA being potential optimization minefields if getting into the "heavy" instructions, which can lead to core throttling, pipeline blocking, instruction splitting, and similar issues depending upon the processor architecture.
------------------------------
@marmaduke Not sure if this applicable to you since it might have been specifically optimization related, but I recently migrated to clang_rt.builtins-i386.lib shipped with LLVM 10rc1 for Win32 builds to resolve a build issue.
http://prereleases.llvm.org/10.0.0/
------------------------------
@Anon5574 Chromium v82 should feature freeze near the end of the month, branch from the trunk next month, and probably go stable somewhere around late April or May.
https://chromiumdash.appspot.com/schedule
Beyond the typical "everyday" stuff, there are four milestone features slated or the v82 release.
https://chromestatus.com/features#milestone=82
The main issue that I have with clang_rt.builtins-i386.lib and clang_rt.builtins-x86_64.lib (in a cross-compile environment) is that I sometimes forget to include them in a build.
The latest 32-bit Windows snapshot build also includes clang_rt.builtins-i386.lib: https://llvm.org/builds/
https://cs.chromium.org/chromium/src/v8/src/base/ubsan.cc?q=mulodi4&sq=package:chromium&dr=CSs explains the need for the inclision of clang_rt.builtins-i386.lib (and clang_rt.builtins-x86_64.lib in a crosscompile environment.)
thanks for all the continued hard work on your builds! I would really love to use them, but I am always (since several months already) having the problem that I cannot log in to YouTube with your builds. I always get:
Something went wrong
Sorry, something went wrong there. Try again.
If using any of the other builders builds, everything works just fine. What could this be?
Thanks so much,
Lorenz
Thank you. I suppose that instruction set is practically the same for Zen 2 as well?
https://chromium.woolyss.com/?all=1#comment-5541
@lgg The baseline instructions I use for my AVX2 builds will work fine for Zen2. Just some various scheduling differences, which could be YMMV. I am on an iPad right now, but I will try to explain it better later when I have an actual keyboard to type.
---------------------------
@marmaduke Just pointing out in case if you are still using the LLVM9 builtins library for Win32 builds. I recently migrated to the LLVM10 builtins library tor resolve a build issue. The snapshot library should work as well. :)
---------------------------
VS2019 now supports (just LTCG?) code generation by using up to a max of 24 threads for VS2019. The previous limits of 4 default and 8 maximum were quite dated. It appears someone at MS actually listened to my feedback on the issue, as my feedback ticket has been under review and recently queued up for prioritization.
https://devblogs.microsoft.com/cppblog/msvc-backend-updates-in-visual-studio-2019-versions-16-3-and-16-4
https://developercommunity.visualstudio.com/idea/825797/increase-linkexe-cgthreads-max-limit.html
Ideally I would have preferred an even higher max limit, but increasing it by 4x should be a good start IMO.
I used to build LLVM with VS2019, and I wanted a higher limit to better suite more modern build systems. I currently use the Chromium project's bundled LLVM revisions to build my updated local LLVM trunk revisions, but I might have to try VS2019 again.
I have a question,
The site can detect copy/paste ?
Thank you !!!
Thanks for all your fast updates ...
:)
https://github.com/Hibbiki/chromium-win64/releases/tag/v80.0.3987.106-r722274 - Thanks for this completeness.
MSVC is now officially unsupported
https://groups.google.com/a/chromium.org/d/topic/chromium-dev/fuVUxe1q6EA
Thanks for the new unG 80.* MacOS build! Also for the great unG Win builds and continuous support!
first of all, great work an resource for everything related to open source Chromium! Actually I'm a Firefox user but for better integration with Android and google I'm considering Chromium, too. On Linux, Chromium updates by the package management system but still I don't really understand how to automatically access the latest stable build on maybe Windows by a script or a small update tool...
For instance, the API (https://chromium.woolyss.com/api/?os=windows&out=revision) regularly updates to a respective snapshot ID, but is this really a stable build? It is not the same as google storage's LAST_CHANGE snapshot. but is it somehow more stable or simply an automatically updated LAST_CHANGE reference, maybe refreshed all three hours or something like that?
If it is not more stable, is there any option to use the API to access the stable reference (i.e. the ID of the current stable reference at top of the page)? At least I didn't find any option to access the stable reference ID...
Thanks in advance!
It is all here : https://chromium.woolyss.com#api
Example : Chromium, stable, windows, 64 bits :
https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=stable-codecs-sync&out=json
https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=stable-codecs-nosync&out=json
With this: you can build you proper update page (like someone did here: https://www.murielfrenchcouture.fr/Chromium.php) or your proper updater script…
Please, check the Chromium #updater part.
@Anon5588: No. This #api is only for "official" Chromium snapshots. It is an alternative to the official download page (https://www.chromium.org/getting-involved/download-chromium). There are other APIs. Contact me if needed.
Would you please consider an SSE4.1 build? SSE2 is comparatively old, and many people still use socket 775/771 CPUs which have SSE4.1 but not AVX. The AVX version installer crashes on these CPUs, but that's to be expected, right?
Thanks
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4061.0-r741948-win64-avx2
----------------
To clarify, I was talking about building LLVM (clang+lld) with MSVC. Good luck building Chromium with MSVC anymore. o.0
----------------
@Plecostomous SSE2 vs SSE4.x is unlikely to offer any significant performance difference for Chromium. IIRC, I did internal testing (last year?) on multiple SIMD instruction sets.
Yes, AVX builds will crash out on processors without AVX support. I currently offer legacy SSE2 builds at GitHub for these older systems.
https://github.com/RobRich999/Chromium_Clang/releases
https://chromium.woolyss.com/api/?os=windows&out=revision
Currently, this returns 742205 while the V3 API call you suggested returns a JSON or a string, but not simply a revision (revision only does not work for some reason). I am looking for a simple call that only return 722274, i.e. the current stable reference ID. Is this possible somehow?
@Jerry: Thanks for pointing to this and I already checked different updaters. Currently I'm a bit unsure if any of these fully satisfies my needs; it was only intended as a motivation why I'm asking for the stable reference ID.
By the way: I also visited this page with a Chromium build on Linux and at least based on my package manager it was a 64 bit build while the info part on this page identified it as 32 bits. Is there maybe something wrong with this architecture detection?
For info, different stable versions have got the same revision/position (ex: 80.0.3987.106 and 80.0.3987.87 use the same 722274 revision).
About CPU architecture detection by this website, yes, it seems to be an issue. I will stop the current way soon because Chromium will change its user-agent too! ;)
https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ
Hi. If you can do an updtade for Android Ungoogled it would be great.
Thanks.
Thanks a lot for the latest ungoogled-chromium build. Also, maybe a coincidence but performance seems to be better than previous builds from you for 32-bit systems. Behaviour got 'janky' after about 6 hours. Has build process changed or...? Saying that, I haven't tried official builds so maybe the change is there. Either way thank you.
Please let me know about significant performance changes with the build. I am experimenting with more fine-grained optimization options depending upon the particular optimization categories. For example, some code for size with a lower LTO import limit, while other code for performance with a higher LTO import limit. I have yet to benchmark the changes on my test system, so YMMV. I do know code bloat is down considerably, which might improve processor code caching, lower memory pressure, etc.
Also FYI, the bookmark bar source has changed, so one of my previous simple edits no longer is applicable. It looks like various conditionals are now handling more complex formatting options. Expect a return wider button width, as there is not much I can do about it right now.
that said, the band Feeder are brilliant, unrelatedly
I am suspecting the issue is relating to your video card/drivers performance, because it occurs after 6 hours.
I suspect the same. But the last ungoogled-chromium does not have the same behaviour. Already I am running 20 hours and feels fresh after no browser restarts. Maybe some obscure memory leak affected my old hardware. Anyway, I am grateful for the builds even if I have to restart each 6 hours :)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4068.0-r743838-win64-sse2
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4068.0-r743838-win64-avx2
----------------
@Daigo Thanks for the FYI. Suspecting I might have to remove my bookmark bar edits altogether for now, as the code has changed and more complex now.
----------------
My latest Win32 build needs to be redone, so it did not get an update for this round. I will try to push its own update today or tommorrow.
----------------
Looks like my Win64 builds took a mild performance hit with my optimization changes. A tweak or few should get me closer to my target expectations for the next round of builds. Thanks for ya'lls patience.
----------------
Looks like I probably can not get the fine-grained control of LTO I want.... yet? Something to poke at later.
----------------
Another round of build time increases, at least for my build box hardware. Fun.
https://reviews.llvm.org/D71775
Windows counts each module as a physical core for AMD Bulldozer and its related families, with each module treated as two logical processors. There were some issues when launched, but these days it generally works okay for the Windows 10 kernel and most apps.
However, to be technical, it is not SMT like Intel HyperThreading. Each Bulldozer module actually has two pipelined cores with certain shared caches, FPU units, etc.
LLVM appears to now count physical cores, plus traditional SMT but not what AMD does, so I just lost 50% of my maximum threads per LLD process when building with ThinLTO. Overriding the LTO job limit does not help, either, as it only sets a upper bound.
TLDNR? I am about to see how far along with performance optimizations I actually can get without LTO building enabled.
----------------
Modified LLVM to work around the threading issue with my AMD Opterons.
Find in llvm/lib/Support/Host.cpp:
#elif defined(_WIN32) && LLVM_ENABLE_THREADS != 0
// Defined in llvm/lib/Support/Windows/Threading.inc
int computeHostNumPhysicalCores();
Change to the following to match your system's available proc thread count (32 here):
#elif defined(_WIN32) && LLVM_ENABLE_THREADS != 0
// Defined in llvm/lib/Support/Windows/Threading.inc
static int computeHostNumPhysicalCores() { return 32; }
@Kein: I had no intention of doing another Chromium release build. Google needs to up its game. Useless!
Still, I would appreciate an update if at all possible because v81 is far off. Thanks!
The peoples ready to arguments should be ready with information, because the branch 80.0.3987.122 have a lot of bugs, which are not present in older versions.
Everybody should have a propriate manner and give some air to @marmaduke.
If peoples want to use the latest security patches, always can get them for free at https://www.google.com/chrome/
@marmaduke The threading issue affects ThinLTO codegen on Windows for all code AFAIK.
CMT straight up does not work unless something has changed since yesterday. LLVM now sets on thread per module instead of logical processor. That affects older AMD processors based upon Bulldozer and similar.
Intel HyperThreading might be a little convoluted. Reading the comments in the code would seem like SMT should work if present, but reading developer comments after my issue was passed to them seems like it is intended to be one thread per core regardless of SMT. ??
To check, turn on ThinLTO optimizations and build a mediums-size file like the libGLESv2.dll library and watch how many peak threads lld-link.exe uses.
I just went ahead and forced a static max thread count in the LLVM source. That works around the issue for now.
The dev working on the recently updated threading model mentioned maybe having something like /opt:lldlto=all to force ThinLTO codegen on up to all available logical processors.
BTW, if building on Linux, I am not sure ThinLTO codegen ever used SMT or CMT. Not sure about cross compiles, either.
-------------------------
The MS C++ CRT allocator with LLVM can incur significant thread blocking due to heap locking. LLVM is working on integrating rpmallcr - "a lock free thread caching 16-byte aligned memory allocator" - for building on Windows. Ideally it should speed up ThinLTO threaded codegen.
Traditionally:
new/delete -> MS VC++ CRT malloc/free -> HeapAlloc -> VirtualAlloc
With rpmalloc:
new/delete -> rpmalloc -> VirtualAlloc
-------------------------
Excellent. There is now a patch in development to enable /opt:lldltojobs=all for using all available hardware SMT/CMT threads during ThinLTO codegen. I suspect it should land as a commit in the near future.
@RobRich: Also thank you very much for your great technical explanation.
@wth: > This is why Google denies access to the store
This is not true at all! 😉
Please read the official tutorial. It is very easy to install Chrome extensions on Microsoft Edge.
https://support.microsoft.com/en-us/help/4538971/microsoft-edge-add-or-remove-extensions
1. Go to edge://extensions
2. On the bottom of the page, check "Allow extensions from other stores"
3. Go to the Chrome Web Store
My screenshot:
Videos from the test page https://tools.woolyss.com/html5-audio-video-tester/
AV1 works very well in the Chromium from Hibbiki but not in the Edge. So which browser is the better choice? No question.
Thanks a lot for the updated ungoogled-chromium build.
(tiny observation: github has release date as 'on 29 Jun 2017' at https://github.com/macchrome/winchrome/releases for a couple of builds)
----------------
Updated Win64 AVX2 build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4071.0-r744852-win64-avx2
I will push other updated Win64 builds shortly. They should perform better than the previous round of builds.
----------------
@marmaduke Something to possibly consider. I am dropping Polly during LTO codegen for now, as it is slowing and even hanging build times. It probably is related to delicm, which ideally is needed for running Polly right before the vectorizer.
I am still running Polly at its early position during clang codegen. Delicm is not really need there, so we can disable it to save time.
---------------------------
Updated Win64 SSE2 build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4071.0-r744783-win64-sse2
Updated Win64 AVX should be in the listings in a few.
Thanks for all your builds!
@rickmv: I'll apply the AV1 patch to Mac ungoogled .122: I have to stop the build and edit the dav1d .ninja files.
Only that the same for the latest Feb 29 unG 80.*.122 for Mac, many youtube videos are still crashing the loading page. On the release ver122 same videos are running OK.
Just to give the feedback. Not a big problem, 79.*.130 is working great. Anyway, this 80 release with so many updates in a month, the G devs need to get their stuff in order, put more work into the browser and give a break on removing options and making compiling more time consuming and cumbersome.
Thanks!
On marmaduke's Great unG builds user Achive distribution for installation. They create the profile in user's home path AppData/Local/Chromium/. You just need to unpack it there into some new directory Application. No need for installer.
Being realistic, here is a decent baseline config for Polly at early during Clang codegen:
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-inliner",
"-Xclang", "-Rpass-analysis=polly",
My current, admittedly way overblown Polly config:
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-analysis-computeout=8000000",
"-mllvm", "-polly-codegen-generate-expressions",
"-mllvm", "-polly-dependences-analysis-level=access-wise",
"-mllvm", "-polly-dependences-analysis-type=memory-based",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-opt-outer-coincidence=yes",
"-mllvm", "-polly-opt-simplify-deps=no",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-precise-fold-accesses",
"-mllvm", "-polly-precise-inbounds",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass-analysis=polly",
As noted previously, I am not running Polly at LTO codegen (via LLD) for now. One dev did some experimental work with FullLTO like 3-4 years ago, but otherwise, the Polly project does not seem to be targeting LTO-centric optimizations at this time. That is why I am running it early during Clang codegen, which is way before LTO codegen occurs. At early in Clang, Polly does its own canonicalization and optional inlining passes before delving into complex LLVM loop optimization, autovectorization, etc.
------------
Updated Win64 SSE2 build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4076.0-r746049-win64-sse2
----------------
Updated Win64 AVX2 build.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v82.0.4076.0-r746179-win64-avx2
How do 81 and 82 look like, for those who have tried them?
Are the issues likely to be fixed in 80, or will 81/82 bring anything worth waiting for?
Thank you all! :-)
(and especially Marmaduke, of course)
AFAIK, Marmaduke and I do pretty much all public builds with at least some form of Polly optimizations.
*Linux is a special case with GCC support still available, but that is somewhat beyond the scope here.
Unfortunately All ungoogled 80.* for Mac are crashing video pages on youtube "something went wrong". Including latest ungoogled 80.*.132. The 79.*.130.AV1-fix build is working perfectly with the same videos. And just before that, 79.*.130 without AV1-fix is crashing.
Some other compile of stock Eloston ungoogled 80.*.132 is not giving any errors. So maybe the extra video codecs included on ungoogled here are the culprit?
Just found out, ungoogled 80.* for win32 are also affected.
This chrome 80 code is doomed. Maybe with the 81, upstream G devs. get back to their sh...enses. Vivaldi is already testing on 81.
https://pastebin.com/EmZUKBwa
If your graphics card is an integrated Intel HD 5000 or 6000, I'm not going to fix the problem.
"We reverse-engineered AMD’s L1D cache way predictor in microarchitectures from 2011 to 2019, resulting in two new attack techniques.
[....]
We also show an entropy-reducing attack on ASLR of the kernel of a fully patched Linux system, the hypervisor, and our own address space from JavaScript.
[....]
We use Collide+Probe to break ASLR from JavaScript within Chrome and Firefox."
Source: https://mlq.me/download/takeaway.pdf
Only that the win32 80.* versions are having the same problem and on different video card.
Got it, thanks. Moving on.
With regard to an installable version of Marmaduke's build: I would appreciate it if the installation program would have an optional feature to remove the user's profile directory when uninstalling the application. In addition, keep in mind that users still have to make a quick launch / desktop icon by hand for the chrome.exe file to launch Chromium comfortably. So if users want to totally remove this version, they need to delete the unpacked directory and the user's profile directory (plus the icon if created).
So @marmaduke, please make an installable version. Thanks for your work!
I've seen you do this before, but I can not remember how many days it is before a version is marked with that tag? Cheers! :)
- If the stable version of Chromium compiled by third-party developers (like Hibbiki, Marmaduke, FreeSMUG and Arm) is similar to Google Chrome, you will see the "up-to-date" tag.
- The "old" tag is automatically added for Major stable version -1. It means if the current stable version is 80. The outdated version is 79.
- A developement version is "old" if its version is under the stable version.
"the academic research team focused on leaking data (an encryption key) from an Intel SGX enclave, a secure area of Intel processors"
Source: https://www.zdnet.com/article/intel-cpus-vulnerable-to-new-lvi-attacks/
"Any vulnerabilities in this process are critical, and easily accessible to remote attackers."
Source: https://github.com/taviso/avscript
Source: https://www.phoronix.com/scan.php?page=article&item=lvi-attack-perf&num=1
----------------------
Apparently it has been decided we all want debug symbols for Windows builds, even if setting symbol generation to zero! :/
I do release builds. I do not care about debug symbols. I do care about increases in build times, plus up to another 2.1GB wasted per build.
Solution, at least for now? Setting debug to none for the linker returns the previous behavior.
D:\depot_tools\chromium\src\build\config\compiler\BUILD.gn
config("no_symbols") {
if (is_win) {
ldflags = [ "/DEBUG:NONE" ]
Long-term solution as more of these wonderful "ideas" emerge? I quit building Chromium.
Change the meaning of symbol_level=0 on Windows
https://chromium.googlesource.com/chromium/src/+/3210c62d6b7d1878890166fe5f3dadf281dc1922
Are you going to make an installable version? See my post above (#comment-5641). Thank you so much for your work again.
-----------------------------
@marmaduke I have finally got around to producing a relatively "sane" Polly config after evaluating numerous options in recent weeks. The following should work fine for building Chromium with limited build time impact IMO.
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-Rpass-analysis=polly",
Eventually I might look into adding register tiling and second-level cache tiling back into the mix, but I am doubting we will find a measurably significant real-world difference in performance. The reality is much of Polly is geared towards HPC and similar workloads, so there is little reason to get too overboard with its options for building a browser, especially compared to further overinflating build times.
-----------------------------
@marmaduke Let's try this again. Stripmining appears to be stalling the build of a component or few; yet again. It seems to come and go depending upon various factors. Anyway.
"-mllvm", "-polly",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-run-inliner",
Note if anything else hangs with Polly enabled, it likely is related to invariant load hoisting. Just remove it from the Polly config instead of trying to work around the issue IMO.
Thank you so much for the updated "83.0.4086.0 all-codecs+ sync win64"
Greatly appreciated! Cheers! :D
don't know if here's the correct place to ask, but I wanted to give it a try to ask here: If I use different Chromium-based Browsers, can I share the profile directory between them?
Particularly interesting for me is the sharing between Edge Chromium (which soon will be rolled out to any Windows 10 machine) and, for instance, "pure" Chromium. On the one hand, both are running Chromium such that I think they might be compatible, on the other hand I don't know how much the individual modifications between the browsers infer or conflict here... It would pretty much interest me if I could sync favorites, history, etc. between Edge Chromium on Windows and Chromium (or alternatively any other browser) on Linux using a shared partition.
Thanks in advance!
In my experience, I suggest running the Polly config rather trim at LTO codegen to limit build time increases.
----------------
*Proof-of-concept* Win64 AVX build with profile-guided optimization (PGO).
Chromium 83.0.4086.0 (Official Build) (64-bit)
Revision 3bdff94dd61ee3fa697a96ff89daff30e9a74b26-refs/heads/master@{#750395}
Compiler clang (+lld_linker +polly +pgo +avx +compiler_optimizations)
https://drive.google.com/open?id=1NUaQCi8qgOAVhpSkjZwfSEGMHRwgwP94
sha1 8E4CF7C22032B887E1151DD74ACB09679686242C
FYI, it is *not* a performance-tuned build, but a PoC experimental build at best. It is not ThinLTO optimized, plus I modified the build config to favor build time at the likely detriment of file sizes, performance, etc. Likewise, I only did very limited profiling.
----------------
If anyone attempts a Chromium PGO build on Windows, pulling zlib into LLVM is going to be a practical requirement anymore. As done for my PoC build configuration and modifications, an instrumented chrome.dll file alone is around *860MB* even with zlib compression of the instrumentation code.
Also note PGO instrumentation needs done at /O2 or higher, so modify the optimization targets in the build config accordingly.
@RobRich: I also added your SSE2 builds with their own portable versions.
I'm sure I speak for other users when I say they are very much appreciated and a good alternative to stable Chrome. I don't know if you do this out of simple kindness or you use the builds yourself (maybe you don't use both architectures)? This is sounding pretty corny now. Anyway...THANK YOU!
https://www.youtube.com/watch?v=RK1K2bCg4J8
What Marmaduke’s build are you using? All ungoogled 80.* running on Intel HD integrated graphics, Mac and Windows, are crashing pages with “ oh snap” on Youtube on most of the videos.
@rickmv: After to see one of his latest #comment-5659, I think @wth uses a Marmaduke's development version. No issue with the 4k video on 64-bit Windows 10 with my basic GeForce GT 1030 fanless graphics card:
https://chromium.woolyss.com/f/video-4k-ungoogled-chromium-80.0.3987.132.mp4 (62 MB).
Maybe disable the hardware acceleration: chrome://flags/#disable-accelerated-video-decode or chrome://settings → [Advanced] → System
https://github.com/macchrome/chromium/releases/tag/v83.0.4086.0-r750130-Win64
SHA1 892F1D0F93FDA6B9821621F2930083FFF8802F82
https://www.zdnet.com/article/google-pauses-chrome-and-chrome-os-releases-due-to-coronavirus-outbreak/
@Jerry: About the SSE build Thx.
Free Tibet
Thanks for trying to help. I’ve been using for a while posted Ungoogled builds. Starting with 80.* Ungoogled builds here have problems with videos on Intel HD graphics, Mac and Windows. On Nvidia it appears they are running ok. Unfortunately this is no fix as from the dev. Looking for alternative. Disabling hardware acceleration makes no difference. Your 4k video is running fine. Other videos from Youtube are crashing even on new profiles. This is an example: https://www.youtube.com/watch?v=a5SxyQ-9YDA
https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_18.html
I need to roll a full build or few to verify. If resolved, I should be able to run Polly during both Clang and LTO codegen again.
----------------
BTW, if anyone runs into issues after upgrading to VS2019 16.5 or 16.6pre1, you probably are going to need to set cflags_cc += [ "/std:c++17" ] in the build config. Also make sure enable_nacl = false is set as a build argument if doing so.
I am going a step further in testing for now. Will let ya'll now if/when I get a build done. YMMV.
cflags += [ "-fms-extensions", "-fms-compatibility", "-fdelayed-template-parsing", ]
cflags_cc += [ "/std:c++17" ]
----------------
A project dev has been working on improving the situation with precompiled headers. I have been disabling the option in recent times due to seemingly no substantial build time improvement, but it appears worthwhile to try again.
enable_precompiled_headers = true
https://chromium.googlesource.com/chromium/src.git/+/10159ac76c62ae3cc3278ad3fe8a2d15571b3175
----------------
Looks like cflags_cc += [ "/std:c++17" ] should suffice without the other MS compatibility options I mentioned above.
So far I have had to edit D:\depot_tools\chromium\src\base\containers\circular_deque.h to replace:
as_const
with:
base::as_const
There are two instances in the file. Both around lines 525 to 530.
Continuing with the build....
Thanks for the update of Ungoogled 32 bit 80.0.3987.149 , download from github
@Jerry
The site should be updated.
Thanks.
Ultimately, the underlying issue is in the Microsoft SDK. MS knows about it, but as to if/when a fix will be available....? The current "solution" is to rollback Visual Studio to a previous 2019 release revision, which is a complicated mess for 2019. It probably would be easier to spin up Windows in a VM and install the older VS revision.
-----------------------
I am likely giving up on the latest Windows SDK until the MS and/or project devs can fix it.
I instead completed a c++14 build under the VS2017 environment with whatever latest SDK it includes. At least that SDK is still working okay.
Updated Win64 AVX in the build listings. More builds to follow.
----------------
Local Win32 building is borked here. Quick look appeared to be something about missing files related to scripting or something. I will poke at it later.
----------------
Updated Win64 AVX2 build now available.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v83.0.4091.0-r751977-win64-avx2
4092 looking good so far for me.
I think Marmaduke don't compile any more 32 bit for Android.
I like it :D The only extension I use is uB0, and I'm fine sideloading it from GitHub, I don't need the Chrome Store for anything really.
I have a Win64 AVX2 build cooking, and I intend to poke at another Win32 attempt sometime today.
For those building Chromium, MS also appears to have a fix in the pipeline for the VS2019 SDK issue.
https://developercommunity.visualstudio.com/content/problem/954683/upgrade-in-c-runtime-from-142428127-to-142528610-b.html
--------------------
Updated Win32 build now available in listings.
It was picking up wrong SDK library code locally. Swapped to a VS2017 32-bit native build environment to resolve.
--------------------
Updated Win64 AVX2 build now available. YMMV as usual.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v83.0.4096.0-r753151-win64-avx2
----------------
I took several hours of build time, but nonetheless, here is a proof-of-concept Win64 AVX build with *profile-guided optimizations*.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v83.0.4096.0-r753154-win64-pgo
It seems to be working okay, but no expectations or promises.
If it works it will be pretty awesome, on the other hand I don't know if there are any platform-specific files in the profile folder. Furthermore, I don't know if all files are fully compatible between different builds; depending on the respective repositories used, the installed versions might not always be exactly the same, but at least more or less the same...
catalina 10.15.4 and xcode 11.4, how did you manage that?
I've read this :"using an hacking method to bypass Secure Preferences". https://www.adlice.com/google-chrome-secure-preferences/ but didn't understand anything. They say they've created a script but there is no link or anything. Is there any way to transfer data without using cloud syncing?
ungoogled-chromium can be configured with command-line switches to disable profile encryption to facilitate portability. Beware that this includes cookies and passwords. I'm not sure if it can strip existing profiles of the encryption -- I haven't tried -- so you may need to create a new profile anyways. I also don't think there are any less-customized Chromium projects that provide this option.
These are back to the current Windows SDK shipped with VS2019. v16.5.2 appears to have resolved the previous SDK issue.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v83.0.4102.0-r755616-win64-avx2
Maybe a percent or few by enabling AVX2 depending upon the specific workload. Media codecs, cryptography, and similar ideally should benefit at least a little. I also enable the compiler to use fused-multiply adds (FMA3) when possible regardless of source programming pragmas.
https://en.wikipedia.org/wiki/FMA_instruction_set
Next up hopefully is getting PGO added to the mix. I already have it working in AVX test builds.
https://en.wikipedia.org/wiki/Profile-guided_optimization
@Jerry My AVX2 builds should be stable enough and routinely updated enough to add to the listings if desired. AVX2 builds require Intel Haswell or later processors.
https://en.wikipedia.org/wiki/Haswell_(microarchitecture)
I use Windows 10 Pro. Since version 83.0.4091.0, the colors of the youtube videos (for example) are not synchronized. Images are "torn".
This problem does not occur with versions of Marmaduke. However, it's perfect on Windows 10 family.
I don't understand.
Thank you for your job.
I suppose you could be a field trial for something breaking locally. Take a look at these flags and try some changes:
chrome://flags/#enable-skia-renderer
chrome://flags/#forced-colors
chrome://flags/#force-color-profile
chrome://flags/#color-provider-redirection
Start with disabling the Skia renderer, which was recently enabled.
Also make sure you have the latest graphics driver for your GPU installed
Thanks for these advices.
I use Windows 10 1909 professional version...
You made me discover the chromium commands, I am confused by Firefox ...
So I changed the parameters indicated one by one, but no improvement on the videos.
As I suspected my Windows 10 pro, I redid an installation starting from scratch.
Regarding the graphics driver, I used the latest version available but not WHQL (2016 driver). I have changed for the most recent WHQL version (2015 driver), but still the same problem.
I still do not understand...
Stop using snap and come bak to standard DEB packages/
PLEASE!
I'm trying to disable autoplay in YouTube and any other sites.
Thanks.
- subresource_filter_tool.exe
- subresource_indexing_tool.exe
- ruleset_converter.exe
subresource_filter_tools.7z
https://github.com/macchrome/winchrome/releases/download/v80.0.3987.163-r722274-Win64/subresource_filter_tools.7z
SHA1 40D264FF5753421979CFDBE70756978A02569690
BTW, with a dated GPU, you might find D3D9 to be more compatible than D3D11 in some situations.
chrome://flags/#use-angle
--------------
Updated Win64 AVX *experimental* build with profile-guided optimizations (PGO).
https://github.com/RobRich999/Chromium_Misc/releases/tag/v83.0.4103.0-r755690-win64-pgo
Thank you for all your work.
And all your Update
:)
No personal endorsement here, but the following extension does seem to work okay for YouTube. Make sure disable autoplay and disable preloading are both checked. It appears to do basically the same thing as "Document User Activation Required" did with the old auto-play browser flag.
https://chrome.google.com/webstore/detail/disable-html5-autoplay-re/cafckninonjkogajnihihlnnimmkndgf
First of all, thank you for your attention and advice.
I tested your 2 versions AVX2 and SSE2 compatible with my AMD Radeon HD 6670 video card.
The DLLs D3D9 and D3D11 being present in Windows and now that I have become a pro of the Chromium settings :-), I chose D3D9 among the possibilities of "# use-angle".
And the miracle happened !!!
Perfect video, you are a great chef ...
However, I wonder why this difference in operation with the versions offered by Marmaduke ...
In any case, a big thank you from France.
https://textslashplain.com/2017/10/18/chrome-field-trials/
----------------
FYI for anyone running older builds:
https://m.slashdot.org/story/369258
https://m.slashdot.org/story/369258
----------------
@Bersyl91 You can grab Chromium from Debian as a deb if desired. I like gdebi for installing single deb packages.
https://packages.debian.org/search?keywords=chromium
https://packages.debian.org/search?keywords=gdebi
Unless something has changed in recent times, Chromium from the Debian repository should run on Debian, Ubuntu, Mint, and similar.
Clang and LTO codegen at -03. LTO instruction import at 100. Profile-guided optimization using project-provided AFDO profile.
Chromium 84.0.4106.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision cba610b17c5d84dbb4b134baf7c654c7804956f3-refs/heads/master@{#756537}
Compiler clang (+lld_linker +thinlto +pgo/afdo +sse2 +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v84.0.4106.0-r756537-linux64-deb
Supporting an extension system will make the browser more complex with more things that can go wrong. When people want a custom experience, there's an app for everything in a single store. Other browsers don't have the incentive to reinforce the app store. They support extensions to build identity and serve the minority of users that must have extensions.
Might be, but even though Chromium might be a bit faster than Firefox (while the difference might be less relevant on mobile), Firefox with uBlock Origin + I don't care about cookies + clear all data on exit (included function) is so much superior to anything other Android browser offer. Additionally, it is somehow interesting that Kiwi integrated extension support as it is also running on Chromium while the latter does not support it directly.
This is not entirely accurate because Chromium depends on the UnRAR which does not carry a FSF- or OSI-approved license.
The UnRAR code is "open", but the license is proprietary. See "third_party/unrar/LICENSE" in the Chromium tarball.
Big thank you for the Android Update :)
@Gibtnix: I corrected your username in your latest post.
@RobRich: I think of you about your 'avx2' build ;)
@Anon5737: Interesting! Thank you. I updated the #features section.
Thanx... for the Windows Update. :)
> i can't control videos on youtube, there is no controls layer.
Remove the --disable-reading-from-canvas switch...and anything (extension, flag at chrome://flags) relative to canvas on Youtube.
(Info about canvas: https://en.wikipedia.org/wiki/Canvas_element)
[EDIT: Jerry. 10 Apr 2020]
You can spoof the canvas fingerprint with an updated extension:
Extension: https://chrome.google.com/webstore/detail/canvas-blocker-fingerprin/nomnklagbgmgghhjidfhnoelnjfndfpd
Test: https://browserleaks.com/canvas
Source code: https://github.com/joue-quroi/canvas-fingerprint-blocker
I would not be surprised if Google took direct instruction from China's President Paddington Bear. (That's 2 years hard labour for you kind sir; thank you very much your excellency, I'll send the Uyghurs your blessings)
I've a clang 8, thin lto, polly optimised version of the present ungoogled for mac: if any one wants, I'll upload it.
(i) Canvas Blocker (Fingerprint protect)
(II) CanvasFingerprintBlock
they do not work!
Chromium ungoogled has 2 flags:
Enable Canvas::measureText() fingerprint deception
Enable Canvas image data fingerprint deception
they work.
-------------
Google has solved the youtube problem: --disable-reading-from-canvas can now be used.
Enable Canvas::measureText() fingerprint deception
Enable Canvas image data fingerprint deception
interfere with uBo and safescript. i suggest that Google carefully test manifest v3!
Looks like I can't access my webcam with Chromium for 64-bit Windows Portable last build.
I've never tryed with previous builds.
Everything look fine, autorisation asked, light next to cam shows it's used, but I got no image.
On firefox, it works.
Any clue?
Thanks
chrome://settings/content/camera
----------------
BTW, thinking of Firefox after the previous poster's mention. A quick FYI:
https://news.slashdot.org/story/20/04/11/1724209/mozilla-installs-scheduled-telemetry-task-on-windows-with-firefox-75
It can be disabled via the Windows Task Scheduler if desired.
It was an extension blocking HTML 5 video autoplay that was blocking the webcam.
Thanks RobRich!
Looks like I dont have the new firefox task...
* Update of Firefox:
If Telemetry was disabled (easily viewable at about:telemetry) via options (https://i.imgur.com/jN6CljD.png) or via the user.js file (https://github.com/beerisgood/Firefox_Anti-Telemetry) before the update, a Firefox task will not be created in the Windows Task Scheduler.
* New install of Firefox:
But if you install Firefox 75+, the Telemetry option is enabled by default. So there will be a Firefox task in the Windows Task Scheduler.
Browser immediately closes when opening any page
----------------
Updated Win64 AVX2 build available.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v84.0.4113.0-r758426-win64-avx2
No flags and only ublock origin
browser opens but as soon as i click on my bookmarks websites it crashes
Hopefully is just a a revision issue. I will take a look at recent commits and roll updated builds. Might take a few hours.
Hello,
Your new version 84.0.4113.0 (758426) • Sunday, 12 Apr 2020 crashes as soon as you add chrome extensions ...
Weird, you said weird, how weird ...
No worries and you don't need to push another build just because of that, only if you want to, of course. I will gladly wait a few more days. I rolled back to previous version for now
Hello
Last update AdGuard 26 march...
AdGuard on 84.0.4114.0 (758483) • Monday, 13 Apr 2020 works fine.
????
Portable Chromium ungoogled for 64-bit Linux - Monday, 13 April 2020
- Ungoogled - https://github.com/ungoogled-software/ungoogled-chromium-portablelinux
- Built on Debian (9) Stretch. Custom Kernel 5.3.4 [libatk1.0-dev 2.30.0-2~bpo9+1]
- Default Chromium (customised) compiler used
- All Codecs
- Hardware Acceleration Video Decode - vaapi patches applied: built against: libva 2.6.1
- Widevine
- thinLTO, AFDO and polly optimised
- Install instructions in README
ungoogled-chromium_81.0.4044.92_1.vaapi_linux.tar.xz
https://github.com/macchrome/linchrome/releases/download/v81.0.4044.92-r737173-portable-ungoogled-Lin64/ungoogled-chromium_81.0.4044.92_1.vaapi_linux.tar.xz
SHA1 044DB3EE1C22EB5FD358F0E7B4A22FBFB153886E
I figure out an issue - Ungoogled-Chromium "eats" too much memory if install HttpsEverywhere - .i.e. I do this browser restarting, one of the "chrome.exe" allocates up to 1GB+ and than (a little bit later) un-allocates memory:
* Ungoogled-Chromium-79.0.3945.130-Win32 - worked FINE (no dumpy allocations); last OK-version
* Ungoogled-Chromium-80.0.3987.87-Win32 - first version with the issue
* Ungoogled-Chromium-81.0.4044.92-Win32 - issue is here
I would like to stay with HttpsEverywhere as it is published by EFF (not from unknown organization). Can you see the issue?
I'll presume that you're referring to my build of ungoogled.
Go to https://github.com/macchrome/winchrome/releases/tag/v79.0.3945.130-r706915-Win64
Compare the performance, with respect to HttpsEverywhere, of the 32-bit polly and non-polly builds.
As you can see from replies above @RochRich released a build (on April 12) that had some problems and he removed it from his Github, BUT the date here on woolyss remained the same instead of also reverting back to previous version which was released on April 2 - 83.0.4102.0 (755245).
Is it possible to make it so if a build is removed the date here also reverts back to when the previous version was released? Don't know if i'm making myself clear
[EDIT by Jerry, 13 Apr 2020: Done! Thanks for report ;)]
@marmaduke I definitely used your build of ungoogled-chromium!
I made an extra research - seems like the issue is not related only to ungoogled-chromium (and optimization options) - but presents in @RobRich (Portable, win32) editions as well:
* chrome-v80.0.3968.0-r715567-win32 - consumes cpu and memory at the start (the issue is present there)
//you may the the issue on the picture
//seems like huge memory leak?
* chrome-v83.0.4102.0-r755245-win32 - !!! no issue !!!
//it still consumes CPU but memory re-use stays within a "usual framework"
I am very limited with hardware, so I can run only win32 builds. And thus I found the nearest available problematic 32-build (mentioned above - v80-based).
@marmaduke - do you plan to prepare ungoogled-chromium based on v83.0.4102.0-r755245-win32 for instance? Memory leak of current ungoogled v81 is too annoying.
I'll continue to update ungoogled v81, and since there will be no v82 update v83 in May.
The problem is proberly with HttpsEverywhere.
Activation context generation failed for "D:\chromium_builds\releases\sse2\chrome.exe". Dependent Assembly 84.0.4115.0,language="*",type="win32",version="84.0.4115.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
A bug report shows project devs are switching yasm to nasm, which I am going to *assume* is the underlying issue. There have been multiple commits related to the issue in the past 24 hours, including an updated dependency roll a few minutes ago.
Now as to why project builds are working versus mine are not, again I am going to *assume* likely differences in the build environments and/or local build tools
TLDNR? It could be a day or few before I have updated builds.
Restore cookies for google.com at startup and prevent youtube.com from seeing those cookies
then delete all cookies for google.com at shutdown
mostly so reCAPTCHA is easier to solve with
" chrome.exe --incognito --save-page-as-mhtml "
Please let me know about any reproducible crashes. I have pushed some build targets even "higher" to -Ofast, which turns on various floating-point optimizations.
----------------
If anyone else is experience assembly-related build issues, I took a couple of potential mitigation steps regarding build tools.
First, I am building the same LLVM revision as the pinned version used by the Chromium devs to help limit "surprises." I probably will continue with the practice for now as that means maybe only two to three LLVM builds per month.
I am building the nasm and yasm assemblers without avx, avx2, fma, polly, etc.
84.0.4116.0 (759268) • Wednesday, 15 Apr 2020
Seems to be working fine so far. Thanks, as always :)
Hello,
The new version 84.0.4116.0 (759268) • Wednesday, 15 Apr 2020 is very fast, opens and closes quickly.
Very fluent navigation.
In short, very good job.
Thank you.
P. S. : collateral effect of automatic update :-)
To add some precision: I compared Canvas Defender and 'Canvas Blocker (no fingerprint)' on Firefox, Waterfox and Chromium 79 (I suppose it would be the same with current version, but needs testing).
- Canvas Defender works on Firefox and Waterfox but not on Chromium 79
- Canvas Blocker works on Firefox and Chromium 79 but not on Waterfox
So maybe you'd rather recommend 'Canvas Blocker (no fingerprint)' as the first choice, instead of Canvas Defender — provided you find the same results. :-)
(I haven't tested the other ones you mention)
84.0.4116.0 (759268) • Wednesday, 15 Apr 2020
After more testing, videos/gifs on Twitter seem to not work. Example: https://twitter.com/PlayVALORANT/status/1250831425378623492
Maybe someone else can confirm this issue
@Anon5783: For me, the video works nicely on the RobRich's 84.0.4116.0 (759268), on 64-bit Windows 10 1909.
For info, videos on Twitter are MPEG-TS stream files (=MP4 files with H.264/AVC + AAC LC codecs).
My tester: https://tools.woolyss.com/html5-audio-video-tester/
Here i have this:
W10 1909 (18363.778)
Maybe a flag, a command-line (switch), a browser setting or an extension blocks your video. Also, you can test with the "Portable" version (=a clean profile).
All good with the build, then :)
btw, a suggestion to you @Jerry
if possible add Github repos when we over mouse into developer name. For example, if i over my mouse into RobRich there's a link there to his Github like we have for the "all-codecs" flag, etc; makes it easier when we want to download previous builds;
ty for your efforts :)
About your suggestion, there is already a link to the developer's Github repository for each release.
Toogle the version/revision number → Click on the link to open the Github page → Choose the "tags" box.
----------------
Win64 and Win32 legacy builds in the listings.
Win64 AVX2 could be awhile. Got a missing symbol issue. Possibly revision related.
Thank you for your releases. I will add your 'AVX2' builds on the site this weekend. 😉
Thanks for updating the dev build all-codecs+, sync, win64 to 84.0.4118.0 (760001) • Friday, 17 Apr 2020.
So far it's running really well!
Cheers!
~Dustyn~
Every year, the tradition with Kiwi ; Chromium based browser for Android is to announce something big for its anniversary:
- 15 April 2018 - First Kiwi Browser release.
- 15 April 2019 - Kiwi Browser gets support for Chrome Extensions.
- Today, Kiwi Browser for Android is going full open-source, like Chromium or Mozilla Firefox.
Everything is released, including extensions code, no strings attached.
You are even allowed to integrate Kiwi in your commercial browser (yep, Microsoft Edge, Brave and Vivaldi are encouraged to use code) or create your own (if you have custom ROMs for example).
This project represents thousands of hours of work.
Pushing such code is absolutely important, it means that new browsers will be able to support extensions and add new functionalities by reusing the work done on Kiwi Browser. In the past weeks, I worked with other browsers to help them integrate Kiwi functionalities. Hope to see good news soon.
If you want to improve Kiwi, your changes will be reviewed actively on GitHub. If you want to create your own fork, feel free to do so.
My goal is to open new possibilities for anyone to mod their browser with absolute freedom.
Give back the power to the user.
The source-code is now available on GitHub and is now the reference for all future developments. It's in Java and C++. As Chromium build system can be sometimes complex to setup, all the dependencies are already included in the repository.
Feel free to share the news with the modding community and Android lovers around you.
If you want to help the project (it's free, as in free beer, and free, as in freedom now), spread the word around you and up-vote Kiwi when you see it on social networks (ex: https://www.reddit.com/r/kiwibrowser/comments/g3kc1n/kiwi_browser_is_now_opensource_including_chromium/ )
Thanks a lot for your support, if you have questions you can reach here as well.
Arnaud.
Link to the repository: https://github.com/kiwibrowser/src
@RobRich: Ok Master! 😉
@Arnaud: Great news! Thank you for your effort and support. Excellent browser. Now, I hope that Chromium and other Chromium-based browsers on Android will support extensions like Kiwi browser currently does. 🤩
In scenarios such as reinstalling the system and extending the settings to a new computer, I realized that each manual configuration from zero is so cumbersome. I also hope to automatically synchronize some settings instead of manually deploying them to different systems every time I modify them.
I tried to find a self-hosted sync server tool. At the beginning, I found https://github.com/valurhrafn/chrome-sync-server, but I found that it seems to have been https://github.com/trexx/chrome-sync-server#chrome-sync-server, and because it is for development and testing purposes, has some https://github.com/ipernet/chromium-sync-server#limitations like only supports one user and does not save data after restart.
I want to know if there is any mature sync server project that supports the latest version of chromium, or any suggestions that might solve tedious problems, have you encountered the same dilemma?
Portable -> Marmaduke | ungoogled | widevine | all-codecs+ | no-sync | win64
For some reason, all my extensions disappear the next day I launch the browser. My bookmarks are intact but the extensions are gone.
What is causing this?
if you are using unpacked extensions make sure the location of said extensions is still the same. In other words Chromium does not 'install' extensions to another folder, it uses the original one you selected.
If this isn't your issue, maybe it is secure preferences related? Read this (#secure-preferences) and then try the flags mentioned to disable secure preferences (click How To Migrate to show them).
Finally had a chance to look at the linker issue. It is a component in the renderer code failing to build at O2 or above. ?!
I just set the baseline target back to Os for now. Other targets are at O3. LTO is O3 across the board.
I will poke some more at the underlying issue and hopefully push updated builds this weekend.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v84.0.4127.0-r762656-win64-avx2
----------------
After tracking down the linker issue, I got LLVM back to ToT. Still building baseline targets at Os on the clang side. Other targets at O3. LTO at O3+100. Performance looks okay so far IMO, so I probably will leave it there for awhile.
----------------
Oh yeah, to clarify, 32-bit LTO is 03+30. I try to limit code size there due to typically older or low-power processors with less system memory. Probably less than a couple percent performance difference versus instruction import at 100 anyway, which is about what Chromium OS devs found in their testing as well.
----------------
For Debian, Mint, Ubuntu, and similar. Built on Lubuntu 20.04 LTS.
Chromium 84.0.4127.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision c2928fb5b97be47758d4b95dc1e7f4cbf414965f-refs/heads/master@{#762672}
Compiler clang (+lld_linker +thinlto +pgo/afdo +polly +avx +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v84.0.4127.0-r762672-linux64-deb
*Please note libc 2.29 or later is required.*
----------------
Before I forget, my latest Linux r762672 build features LLVM's relatively new aggressive whole-program devirtualization - optimization of virtual (indirect) calls to direct calls - during LTO codegen.
https://lists.llvm.org/pipermail/llvm-dev/2019-December/137543.html
https://reviews.llvm.org/D71913
On the clang codegen side, I already have been using -fstrict-vtable-pointers for quite a long time now in both Windows and Linux builds.
http://blog.llvm.org/2017/03/devirtualization-in-llvm-and-clang.html
https://en.wikipedia.org/wiki/Profile-guided_optimization
Feel free to let me know about any notable performance differences.
I don't see the enable-checkbox-external-protocol.patch in the 81.0.4044.129 release. That patch is a new and belongs to the ungoogled-chromium extra patches.
Please, could you apply it in future releases?
I said "future releases" :)
Respect for your time and effort.
Both previous version packages works perfectly. I mean version 81.0.4044.122,
64-bit: https://github.com/Hibbiki/chromium-win64/releases/download/v81.0.4044.129-r737173/mini_installer.sync.exe
32-bit: https://github.com/Hibbiki/chromium-win32/releases/download/v81.0.4044.129-r737173/mini_installer.sync.exe
Like I said, there are no problems with the previous version, but it can only be used if to unzip it manually using 7zip. Hence the conclusion that something is wrong with the installer package. Chromium itself works.
Poking around the project's related python scripts, I am now able to pull those profiles for local usage, meaning I should no longer have to deal with the tedious task of generating additional instrumented builds and subsequent collection of my own profile data.
I do not build Chromium exactly the same as project devs, but LLVM provides enough leeway that I should be okay using the project's collected profile data. So barring no complications, my future builds should include profile-guided optimization as a standard feature. I will post details later assuming it all comes together. I have a Win64 AVX build cooking now.
I have reported the issue and the likely related code commit for when it started. I gave up poking at the issue days ago, so It will be up to the project devs to figure this one out, as they are going to have to fix it anyway if/when turning on PGO+ThinLTO for Chrome release builds.
Chromium for 64-bit macOS - All Codecs - Saturday, 02 May 2020
Chromium 84.0.4134.0 (Official Build) (64-bit)
Revision 013465ba236dc65552565bef4ad83bb71f08e3c2-refs/heads/master@{#764922}
OS macOS Version 10.15.4 (19E287)
- only for macOS 64
- with codecs (h264, h265, flac, xvid, AV1, etc..)
- official build
- clang/LLVM - default
- xcode 11.4
- macOS SDK 10.15
- PGO
Sync • WebRTC • Widevine
Chromium.84.0.4134.0.sync.app.zip
https://github.com/macchrome/chromium/releases/download/v84.0.4134.0-r764922-macOS/Chromium.84.0.4134.0.sync.app.zip
SHA1 CB83AA6615958528A8C8F98D57AE9E697B7DA65B
No Sync • WebRTC • No Widevine
Chromium.84.0.4134.0.nosync.app.zip
https://github.com/macchrome/chromium/releases/download/v84.0.4134.0-r764922-macOS/Chromium.84.0.4134.0.nosync.app.zip
SHA1 43DEE0D5C27569DB0BD626D4EA522B17DA708B06
Yes, macOS and Windows v84+ ungoogled builds will benefit from PGO in the future, presuming that the Chromium Authors persist with PGO. Particularly with macOS given that the latest versions of clang/llvm is producing bitcode that is totally incompatible with the current macOS, and llvm/clang 8.0.1 is not compatible with the latest development versions of Chromium. It pains me to say, but the Chromium Authors are actually doing a good job. The same cannot be said for useless Apple; spend less time producing diarrhoea inducing adverts: develop mach-o linker.
https://reviews.llvm.org/source/llvm-github/browse/master/lld/MachO/
===================
Chromium for 64-bit macOS - All Codecs - Tuesday, 05 May 2020
Chromium 84.0.4134.0 (Official Build) (64-bit)
Revision 013465ba236dc65552565bef4ad83bb71f08e3c2-refs/heads/master@{#764922}
- clang/LLVM llvm-project-762fb1c40eea6878c2d6a1f0f1fc7915c8747981 (native polly linking)
No Sync • WebRTC • No Widevine • thinLTO • (compile & link) Polly • PGO
Chromium.84.0.4134.0.nosync.polly.lto.app.zip
https://github.com/macchrome/chromium/releases/download/v84.0.4134.0-r764922-macOS/Chromium.84.0.4134.0.nosync.polly.lto.app.zip
SHA1 227CDF84BD45E6240E5A21059B83D85D53512D40
===========
cflags = [
"-fprofile-instr-use=$pgo_data_path",
# It's possible to have some profile data legitimately missing,
# and at least some profile data always ends up being considered
# out of date, so make sure we don't error for those cases.
"-flto=thin",
"-Wno-profile-instr-unprofiled",
"-Wno-error=profile-instr-out-of-date",
"-Wno-profile-instr-out-of-date",
"-Wno-unknown-warning-option",
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
##"-Xclang", "-Rpass-analysis=polly",
]
ldflags = [
"-flto=thin",
"-fsanitize=cfi",
#####"-Wl,-lto_library", "-Wl,/Users/reggie/llvm-bootstrap-install/lib/libLTO.dylib", ## NOT SUFFICIENT!!!
##### MUST USE: export DYLD_LIBRARY_PATH=/Users/reggie/llvm-bootstrap-install/lib/libLTO.dylib
"-Wl,-mllvm", "-Wl,-polly",
"-Wl,-mllvm", "-Wl,-polly-2nd-level-tiling",
"-Wl,-mllvm", "-Wl,-polly-invariant-load-hoisting",
"-Wl,-mllvm", "-Wl,-polly-register-tiling",
"-Wl,-mllvm", "-Wl,-pass-remarks-analysis=polly",
]
https://bugs.chromium.org/p/chromium/issues/detail?id=1077605
https://chromium-review.googlesource.com/c/chromium/src/+/2181364
@everyone: There is also a nosync version by Hibbiki (= ungoogled)
https://github.com/Hibbiki/chromium-win64/releases/tag/v81.0.4044.138-r737173
I see updated ungoogled for Mac but not for Windows. I can't understand that.
I guess we have to think for move to Hibbiki's build.
+1 Hibbiki
Really? Marmaduke is pretty swift with the updates, but if you're that paranoid, you might as well have a second browser you can use for the few days it takes to get updated.
Anon5836 here
I forgot to add, the build was already updated on github (25 minutes ago), so i really don't get what you're complaining about.
I apologize but I cannot agree with your comment and I hope Marmaduke don't see it :)
@wth,
True. Allow me just to add to your comment the bugs=changes=improvements, which from time to time are coming with the newest releases :)
@Marmaduke when you can , it would great an update for Android too.
Thank You.
Regards. :)
Please note that this is not equivalent to ungoogled builds, which specifically include patches from Eloston (https://github.com/Eloston/ungoogled-chromium). The nosync variant does not include Google API keys (which are not included in official Chromium releases) during build process, but functionally is identical to sync variant if such keys are provided externally via environment variables. You can check differences between both builds on GitHub by comparing sync.args and nosync.args.
Also technically, as of writing this comment, Eloston's ungoogled variant is not updated for 138 yet (https://github.com/Eloston/ungoogled-chromium/pull/1029).
Hi and thanks for providing builds for the community.
I could not get swiftshader working last time I tried your x86 build - swiftshader is used on Chromium when no hw acceleration is available (such as my situation). Without it there are anomalies - audio stutters, etc. Also webgl does not work without it - easiest way to diagnose (also chrome://gpu reports no renderers available).
Marmadukes ungoogled build had the same problem but he/she was able to change the code to fix swiftshader.
Thanks for reading!
(This is not a major/urgent issue, this is something I experienced a few months ago. I have no opportunity to test your builds at present)
Works for me on 81.0.4044.138 x86 nosync variant, GL_RENDERER reports 'Google SwiftShader'. Demo on https://www.khronos.org/registry/webgl/sdk/demos/google/san-angeles/ also works properly.
Hi.
Thank you very much for the Android update.
Regards...
(Anon5842 here)
I apologise for the earlier message, it turns out it was an issue with the drivers of my Intel IGP. Swiftshader works on Win 7 but not Win 8.1 on all builds. Sorry I didn't diagnose this and pointed the blame at your build. Turns out I can use my Win 7 driver on 8.1 and it also allows swiftshader, now to test for OS instability.
Sorry again and thanks.
An user reported me an issue about your latest ungoogled versions: The hash values are not correct on your github page...but are good here.
https://github.com/macchrome/winchrome/releases/tag/v81.0.4044.138-r737173-Win64
https://md5file.com/calculator
I've checked and corrected the SHA-! values.
[EDIT by Jerry, 12 May 2020: Thank you! ;)]
A few FYIs regarding optimizations:
*Enabled profile-guided optimization (PGO) using project-generated profile.
*Added partial lining to the mix for both clang and lto codegen.
*Modified polly canonicalization passes to do aggressive instruction combining, scalar replacement of arguments, and slightly increased early inlining.
*Modified polly for more permissive scop detection.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v84.0.4145.0-r767690-win64-avx2
- The "AVX" version is optimized for computer with a CPU supporting the AVX instructions. (year: 2010+)
- The other one works on computer... SSE2 instructions. (year: 2000+)
- The "AVX2" (on #comment-5851)... AVX2 instructions. (year: 2013+)
@RobRich and all devs: Big thank you! ;)
@Anon5850: Maybe Marmaduke will be interested in this feature already implemented in the open-source Kiwi browser project. I do not know! ;)
[EDIT by Jerry, 13 May 2020: Corrected! Thank you @Anon5855]
I tried to retrofit wchen342's extension patches to my ungoogled Android 81.0.4044.138, but was not successful.
Personally, I think Google made the right call in not supporting extensions on mobile platforms: as long as javascript can be toggled on/off that's all that is required; nevertheless, if and when extensions can be gracefully incorporated I will.
[EDIT by Jerry, 13 May 2020: 👍]
I had an issue with chromium portable, here was my solution.
I had an issue where window's default browser directory for chromium (portable version at chromium.woolyss.com) was at the downloads folder and windows had not detected the missing executable for the default browser,
icon was missing too in w10 settings.
After trying many things I eventually got a fix, updating the directory values at
Computer\HKEY_CLASSES_ROOT\Chromium(randomstring)\shell\open\command
at "\HKEY_CLASSES_ROOT\Chromium(randomstring)" the random letters/numbers at the end of chromium will be different for everyone im assuming so just look for chromium and you'll see it.
good luck
Swap out d3dcompiler_47.dll with an earlier version if required.
Chromium v85.0.4148.0-r769185-Win64
Chromium for 64-bit Windows - All Codecs - Friday, 15 May 2020
Chromium 85.0.4148.0 (Official Build) (64-bit)
Revision 510cc5c9a476b73073d823ac84f3f0ac0921ebae-refs/heads/master@{#769185}
OS Windows
- SDK 10.0.19041.0 (Visual Studio 2019 16.5.5)
- clang/llvm default (GNU/Linux cross-compile)
- ThinLTO
- WebRTC
- PGO
No Sync - No Widevine
Chrome-bin.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v85.0.4148.0-r769185-Win64/Chrome-bin.7z
SHA1 2117AE4E4CC1DF7A78BE31B5B5B74AA44C73C5ED
Sync - Widevine
Chrome-bin-sync.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v85.0.4148.0-r769185-Win64/Chrome-bin-sync.7z
SHA1 48ABC499A24397943CC15C4A489BE133E3926AE7
https://github.com/macchrome/chromium/releases/download/v85.0.4148.0-r769185-Win64/mini_installer.exe
SHA1 E4D1466746A49F0C95ABC02BBD6F366C0F66CC1E
https://groups.google.com/a/chromium.org/forum/?_escaped_fragment_=topic/chromium-dev/-0t4s0RlmOI
cat chrome/build/win64.pgo.txt
>>> chrome-win64-master-cfc722972bb38f406ad47e4c56911f35ab1231f9-0000000.profdata
wget https://storage.googleapis.com/chromium-optimization-profiles/pgo_profiles/chrome-win64-master-cfc722972bb38f406ad47e4c56911f35ab1231f9-0000000.profdata
****
chrome_pgo_phase = 2
pgo_data_path="//chrome-mac-master-d2d91c2fe263909bb31bcfaf0ae882b731320f0d-0000000.profdata"
****
What are your recommended parameters for polly compile and link? Oh, and is there any benefit to using the "new pass manager"?
It has been working perfectly on every site for two weeks, now. Thanks a lot! :-)
HI. Thank You for Windows 32bit Update 84.0.4145.0.
Regards...
can those pgo profiles of master/lkgr also be used for the current stable build (83.0.4103.61)? Since there is no win64.pgo.txt file present in the tag 83.0.4103.61, but starting from dev version (84+). So for my last build i just took the one from the lkgr branch.
Regards
Hi.
Thank You for Windows Update.
If you have time can you Update Android too ; 83.0.4103.61 ?
Thanks
Regards.
https://www.zdnet.com/article/googles-chrome-will-give-you-an-always-show-full-url-setting/
Go to chrome://flags/#omnibox-context-menu-show-full-urls ➜ Enabled
Context menu show full URLs
Provides an omnibox context menu option that prevents URL elisions. – Mac, Windows, Linux, Chrome OS
Thanks for the explaination. What a disappointing development though. The context menu option only last for that session, then you have to tick it again! It seems this was added through gritted teeth haha.
You can still force it:
--disable-features=OmniboxUIExperimentHideSteadyStateUrlScheme,OmniboxUIExperimentHideSteadyStateUrlTrivialSubdomains,OmniboxUIExperimentHideFileUrlScheme
A humble suggestion about compression formats: xz format is natively supported by MacOS (decompression) and occupies about 2/3 of zip* — tested by myself on
Chromium.84.0.4134.0.nosync.app.zip = 99.5 Mb
Chromium.84.0.4134.0.nosync.app.txz = 66 Mb
For a number of reasons (including global warming ;-) ), it seems to me a good idea to use xz when possible — the same might be true for other platforms but I guess it would probably involve a third party app, so I understand the other devs might prefer zip for the sake of compatibility.
*P.S.: not always true, but in this particular case yes. ;-)
LOL! Greta, is that you???
Change compression format to save the planet. Now, this is a new low after the cow farts just a while ago.
https://blog.google/products/chrome/more-intuitive-privacy-and-security-controls-chrome/
Doja "I'm a stupid bint" Cat
You also will want to manually change config("optimize") to /O2 for Windows in depot_tools\chromium\src\build\config\compiler\BUILD.gn for PGO building assuming the change has not yet been backported. Not sure about older "stable" branches, but chrome_pgo_phase=2 now sets /O2 as the baseline optimization level due to how profile-guided optimization works. Example here:
https://chromium.googlesource.com/chromium/src/+/c7469664d0300ffcb8c2531d0569436401b92d2e/build/config/compiler/BUILD.gn#1960
---------------------
@marmaduke I have scaled back Polly for now given we are playing with PGO. I did enable it for both clang and LTO codegen with my current Win64 AVX build. I also have trial enabled partial inlining.
cflags:
"-Xclang", "-fstrict-vtable-pointers",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
"-mllvm", "-enable-partial-inlining",
"-mllvm", "-polly",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-position=early",
# "-Xclang", "-Rpass-analysis=polly",
ldflags:
"-mllvm:-enable-local-reassign",
"-mllvm:-regbankselect-greedy",
"-mllvm:-enable-partial-inlining",
"-mllvm:-polly",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-position=before-vectorizer",
# "-mllvm:-pass-remarks-analysis=polly",
thinlto:
-mllvm:-import-instr-limit=100
Also given we are playing with PGO, my current Win64 AVX build is built at O2 for clang and LTO optimizations. Ideally that should allow some functions to be better optimized for size where appropriate. I reevaluate with future builds.
Might as well disable PDB creation if not needed.
config("no_symbols")
if (is_win) {
ldflags = [ "/DEBUG:NONE" ]
While you are at it, might as well reenable sized deallocations, too.
depot_tools\chromium\src\build\config\win
"/Zc:sizedDealloc",
I am not sure Polly has been properly plumbed into the new pass manager, yet.
BTW, here is how I am pulling PGO profiles:
vpython D:/depot_tools/chromium/src/tools/update_pgo_profiles.py --target=win64 update --gs-url-base=chromium-optimization-profiles/pgo_profiles
Available targets are win32, win64, and mac. Profiles are deposited at depot_tools\chromium\src\chrome\build\pgo_profiles,
Thanks.
PDB creation is insane!
I've been testing sccache-dist, but it does not work. Build times are getting crazy. i really don't want to buy an AMD 3970/90x but might have to,
Really stupid decision to drop jumbo.
I am not expecting a substantial performance difference, but I am rolling an AXV2 test build at -O3 for clang and LTO codegen right now.
thx for clarifying. I'll try using the pgo data of the closest version to the current stable release. I'm currently experimenting with zen 2 builds (march=znver2, optimized for the current ryzen processor architecture).
If anyone is interested in those builds, let me know (;
I am getting the following errors at chrome://gpu on my Windows 7 machine (using Intel gfx). Everything works fine. I only ever had software rendering anyway. The referenced files don't exist, at least not ony my install. Anyone else getting these? Thanks.
[1500:1504:0527/072127.759:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: mf.dll: The specified module could not be found. (0x7E)
[1500:1504:0527/072127.759:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: mfplat.dll: The specified module could not be found. (0x7E)
[1500:1504:0527/072127.759:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: The specified module could not be found. (0x7E)
[1696:1712:0527/072253.726:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: mf.dll: The specified module could not be found. (0x7E)
[1696:1712:0527/072253.727:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: mfplat.dll: The specified module could not be found. (0x7E)
[1696:1712:0527/072253.727:ERROR:dxva_video_decode_accelerator_win.cc(1397)] : DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: The specified module could not be found. (0x7E)
GpuProcessHost: The info collection GPU process exited normally. Everything is okay.
@Doja Cat
for the DNS over HTTPS issue, i am referring to the ability to set custom DOH within Chrome settings. this has been live since v83 atleast.
Here is a screenshot.
If you notice carefully, it is under chrome > settings > Privacy and security > safe browsing. It allows 'auto mode' as well as custom DOH.
This is detailed in google's DOH pages quite extensively.
This particular feature is not yet available. The whole new security redesign page is behind experiment #privacy-settings-redesign but it seems that DNS settings are not yet part of it.
I advise you to compare your results to clean Chrome install.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v85.0.4157.0-r771869-win64-avx2
@Anon5886 Are you perhaps running Windows 7 N? Reason I ask is it appears you like do have the Windows Media Feature Pack installed. You can manually install it via KB968211. Here ya' go:
https://www.microsoft.com/en-us/download/details.aspx?id=16546
@Anon5885 With Zen 2 you should be able to manually force FMA optimizations as well. :) Try the following options when modifying depot_tools\chromium\src\build\config\compiler\BUILD.gn
Add to common_optimize_on_cflags:
"-march=znver2",
"/clang:-ffp-contract=fast",
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
"-mllvm", "-enable-partial-inlining",
Add to common_optimize_on_ldflags:
"-mllvm:-march=znver2",
"-mllvm:-fp-contract=fast",
"-mllvm:-enable-local-reassign",
"-mllvm:-regbankselect-greedy",
"-mllvm:-enable-partial-inlining",
@marmaduke Bumping clang optimizations to "-Xclang", "-O3", looks good IMO. Also ThinLTO at lto_opt_level = 3.
Even at -O3 PGO still is helping with some size optimizations as applicable, plus we get the other benefits of profiling.
I have added back more Polly options, too. Looking okay here.
cflags:
"-mllvm", "-enable-local-reassign",
"-mllvm", "-regbankselect-greedy",
"-mllvm", "-enable-partial-inlining",
"-mllvm", "-polly",
"-mllvm", "-polly-2nd-level-tiling",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-position=early",
"-mllvm", "-polly-register-tiling",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-run-inliner",
# "-Xclang", "-Rpass-analysis=polly",
ldflags:
"-mllvm:-enable-local-reassign",
"-mllvm:-regbankselect-greedy",
"-mllvm:-enable-partial-inlining",
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-position=before-vectorizer",
"-mllvm:-polly-register-tiling",
"-mllvm:-polly-run-dce",
# "-mllvm:-pass-remarks-analysis=polly",
Anon5886 here: I am not running with the Media Foundation Pack installed but I have never experienced the message before from Chromium in all the years running it on Win7. Either way I do not think my hardware is accelerated in Chromium. Gonna investigate the source to see for a change. Thanks for the clue!
The zip file is produced using the ditto command: ditto -c -k --sequesterRsrc --keepParent <archive> <input>
Some Apple services demand this (even if I do not use them.) I've noted the discrepancy in app size between my and official builds, and am not bothered
@RobRich
Thanks. I'll try to incorporate your suggested parameters into my dev builds.
@Anon5886
If you're using a version of Chromium built with: SDK 10.0.19041.0 (Visual Studio 2019 16.6.0) : 64-bit, try replacing d3dcompiler_47.dll with an earlier version.
@Anon5887
Compare and contrast the official Dev Chrome/Chromium versions. My bias is towards stable ungoogled: I build dev versions to mitigate changes to future stable versions.
thank you for sharing :) will try those flags in my next build. With just march=znver2 i already got a nice boost of about ~200-250 points in web.basemark.com, compared to generic builds.
Anon5886 here. Turns out it was a false alarm. I tried one of your older builds and do not get the message, so it is something they added in the latest. Not sure why I didn't think of doing this before (doh!)
Btw it is probably this change (thought it is 3 months old I guess it just got into release channel:
"Reintroduce LOG(ERROR) calls for fatal DXVA errors
the PLOG(ERROR) calls were removed on friday as part of a macro cleanup,
but we need non-debug builds to have notices that dll loading has failed
to avoid totally silent errors."
Thanks again guys.
Have GUI apps via VcXsrv and sound via PulseAudio working on Ubuntu 20.04 under WSL 2. Tested Dillo and Firefox so far.
Now to later see if building Chromium for Linux via WSL 2 can be viable enough. Previously I gave up under WSL 1 due to extremely slow I/O.
The speedtest-cli utility is showing about native network I/O for Internet transfers, so it probably will be down to disk I/O at this point.
Hi. Thank You for the Android update.
But error 404 with the download link
Regards.
thanks for making a version with sync and your continued updates!!!
Hi. If you're interested , here first release
of Chromium 83 for Android with extension.
https://github.com/wchen342/ungoogled-chromium-android/releases
To quote wchen342: This version is highly experimental and is not intended for daily usage yet!
Extension functionality will be incorporated when I'm satisfied that its implementation is robust.
Ok.It was just to keep you informed.
Regards.
Hi.
Looks like canvas spoofing feature not working in last build. Here (browserleaks.com/canvas) signature not changed.
Use your noggin and configure it.
This behaviour starts when ungoogled-chromium 80 is first introduced with the new SameSite behaviour, and disabling it on chrome://flags doesn't work.
The only real solution is to rollback to ungoogled-chromium 79
@Anon5903
and nope, before you say I'm stupid, I did disable "Clear cookies and site data when you quit Chromium" under chrome://settings/content/cookies so it keeps my cookies across sessions.
Now to update my build box to Win10 2004.
Next up should be Chromium itself. :)
----------------
Install WSL2:
https://docs.microsoft.com/en-us/windows/wsl/install-win10
I also had to install the latest WSL2 kernel update:
https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel
Now note the Ubuntu productid:
https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6
Process the productid to appx dowload links here:
https://store.rg-adguard.net/
Download the latest appx version. It will be around 800-850MB.
The downloaded appx file is just a compressed archive. You can unzip it to your desired location via 7-Zip or similar. :)
Enter the desired location, then simply run ubuntu.exe and follow the prompts.
----------------
https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md
Note before running ./build/install-build-deps.sh you might need to change how python is invoked. There are various ways. I simply used:
sudo apt install python-is-python3
Also be sure to comment out the snapcraft stuff before running the ./build/install-build-deps.sh script. I vaguely attempted setting it up, and it turned out not to be worth the trouble to me. I do not build Chromuium to snaps anyway.
Around line 540 in the install-build-deps.sh script:
# if package_exists snapcraft; then
# dev_list="${dev_list} snapcraft"
# fi
BTW, the python-is-python3 package will be removed by the install-build-deps.sh script, along with python 2.7 and 3.x being configured as needed.
@marmaduke: A Samsung engineer currently works on the native support of Chrome extensions for Android. ;) Thank you to the Kiwi Browser dev!
- https://chromium-review.googlesource.com/c/chromium/src/+/2222773
- https://bugs.chromium.org/p/chromium/issues/detail?id=1074710
@Hibbiki: Like ever, you are very responsive. Thank you very much too! ;)
Hi.Thank you for windows update...
Thanks so much for the Windows updates...always appreciated!
Windows 10 WSL2 manually updated kernel:
Clang-built linux-next kernels for WSL2 available here:
https://github.com/nathanchance/WSL2-Linux-Kernel/releases
See "Tell WSL 2 to use that kernel when booting up" on creating a .wslconfig config file here:
https://nathanchance.dev/posts/wsl2-kernel-clang/
----------------
My build box is doing a Chromium for Linux build right now via Ubuntu 20.04 running under WSL2. Hopefully should have a build pushed later tonight.
I will try to push updated Windows builds in the next day or two.
Hi. Thank You for the update.
Can you update for Android too ; 83.0.4103.96.
Thanks...
https://www.reddit.com/r/Android/comments/gy8ac5/the_brave_web_browser_is_hijacking_links_and/
On the Windows site, LLVM is reporting a broken function error during the LTO codegen of the v8_context_snapshot_generator executable. At least it is a known issue.
https://bugs.chromium.org/p/chromium/issues/detail?id=1091784
Yeah, that probably will take 5-7 years, knowing Chromium past history.
Trying to profit from browser forks, this thing always happens in the end!
https://github.com/wchen342/ungoogled-chromium-android/releases
https://www.nsaneforums.com/topic/376225-brave-blows-up-its-whole-reason-for-existing/
Hey, mate, I know it is a bit too much to ask but could you by any chance write a simple how-to to the dev environment you use to compile Chromium + Ungoogled? I want to migrate to it from my current daily pick but I need a few mods before it can be usable to me, that means I will have to compile it myself. I tried setting it up before but it requires 5 PhDs with 28 years of experience to do so, which is why I even ask to begin with. Honestly, I dont I ever managed to complie any c++ project on windows ever, it is such a mess.
Anyway, it would be really appreciated if you could share some wisdom.
The documentation to compile Chromium on Windows:
- Official: https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
- Ungoogled: https://github.com/ungoogled-software/ungoogled-chromium-windows
- Other: #source-code
How do you make a ("Ungoogled") Windows build from the source code?
Answer by Eloston at https://github.com/Eloston/ungoogled-chromium/issues/235
I cross build Chromium for Windows on GNU/Linux Debian. These instructions are concise and terse!
Before you even attempt to cross-compile ungoogled for Windows (it WILL fail) do a conventional build first.
https://github.com/macchrome/winchrome/releases/download/v83.0.4103.97-r756066-Win64/cross_build.txt
Where can i find debug symbols (for windows) for chromium browser?
- https://www.chromium.org/developers/how-tos/debugging-on-windows
- https://stackoverflow.com/questions/46078967/chromium-debugging-on-windows-environment (similar on Visual Studio 2019)
> I cross build Chromium for Windows on GNU/Linux Debian.
Oh, okay, that makes sense. Thanks!
i've tried that info but it works only with Google Chrome, not with pure Chromium downloaded from this site. Debuggers can't find symbols on that server (https://chromium-browser-symsrv.commondatastorage.googleapis.com)
https://github.com/RobRich999/Chromium_Clang/releases/tag/v85.0.4169.0-r777004-win64-avx2
I will try to get to the other Windows builds in the next day or so.
Back to Windows, Win32 building is complaining about a missing symbol. BTW, it is not related to the existing clang_rt.builtins-i386.lib library requirement. I have add a MS library include that hopefully should include the needed symbol. More info to follow. Rebuilding now.
I am not sure if is related to your building process or that's a issue with ungoogled but the flag chrome://flags/#fingerprinting-canvas-image-data-noise is not present in the branch 83.0.4103.97.
The result of that the canvas fingerprint spoofing is not working in this version.
For Gianna Floyd:
I'n'I nah come to fight flesh and blood,
But spiritual wickedness in 'igh and low places.
So while they fight you down,
Stand firm and give Jah thanks and praises.
'Cos I'n'I no expect to be justified
By the laws of men - by the laws of men.
Oh, true they have found me guilty,
But through - through Jah proved my innocency.
(So Much Things to Say - Bob Marley)
ungoogled-chromium-83.0.4103.97-2_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v83.0.4103.97-r756066-Win64/ungoogled-chromium-83.0.4103.97-2_windows.7z
SHA1 0C34F7153311125889D31F5866A6BCBF0CD73246
Like ever, thanks a lot for your great work!
@Drago: Exactly! Try this flag: --disable-reading-from-canvas
@AngeloG:
https://linuxmint-user-guide.readthedocs.io/en/latest/chromium.html
https://forums.linuxmint.com/viewtopic.php?f=42&t=321953
@RobRich: I prepare an entry for your Win64 AVX2 build ^^
https://github.com/RobRich999/Chromium_Clang/releases/tag/v85.0.4169.0-r777004-win64-avx2
Hi. Thank You for Windows and Android Update...
Or even try to school ya! Oh, no!"
Go get the unG and sync Mac updates, oh yeah!
Revision ce7134bb3d95141cd18f1e65772a4247f282d950-refs/branch-heads/4103@{#694}
Portable Chromium ungoogled for 64-bit Linux - Thursday, 18 June 2020
- Ungoogled - https://github.com/ungoogled-software/ungoogled-chromium-portablelinux
- Built on Debian (9) Stretch. Custom Kernel 5.3.4 [libatk1.0-dev 2.30.0-2~bpo9+1]
- Default Chromium (customised) compiler used
- All Codecs
- Hardware Acceleration Video Decode - vaapi patches applied: built against: libva 2.6.1
- Widevine
- thinLTO, AFDO and polly optimised
- Install instructions in README
Tested under Ubuntu 18.04.4 LTS and Fedora 32
apt install libatomic1 (if required)
apt install vainfo
Need to install libva-2.6.1:
https://github.com/intel/libva/releases/download/2.6.1/libva-2.6.1.tar.bz2
./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
chrome://flags/
Override software rendering list - Enabled
ungoogled-chromium_83.0.4103.106_1.vaapi_linux.tar.xz
https://github.com/macchrome/linchrome/releases/download/v83.0.4103.106-r756066-portable-ungoogled-Lin64/ungoogled-chromium_83.0.4103.106_1.vaapi_linux.tar.xz
SHA1 7778CBB5E3C0CB956FD43B44FBC1D23DCD341683
it might be a good idea to indicate on your blog the current release of Widevine CDM (found in Marmaduke builds) which is 4.10.1679.0 on June 02, 2020.
someone knows why clock extensions (with checking system clock) dont work any longer?
----------------
@Jerry Thanks. I will try pushing my next AVX2 build. Hopefully should be tomorrow.
BTW, we might be dropping Win32 depending upon how my next build attempt goes. I have no real use for the Win32 build, and it has been causing lots of local build headaches here. I will let you know.
Next week, l will prepare an entry for your builds: RobRrich's AVX2, Marmaduke's ungoogled-version on Linux.
@Anon5949:
Yes it is possible but "not friendly": https://www.andreafortuna.org/2019/09/24/how-to-install-latest-widevine-plugin-on-chromium/
@RobRich:
About your win32 version, ok. You will confirm this to me! ;)
@Bernd:
Prefer the stable version or the other development version.
Got problems with prime video : error 202099750.
I'm pretty sure it's comming from ungoogleed chromium as my other browsers works ok.
Thanks
I only found Marmaduke version that support it, but it is portable and missing the google stuffs.
Hi. Thank You for Windows quick update. :)
-password manager won't save password
-some cookies, NOT ALL COOKIES (usually cookies that makes logins persist) get erased after chromium exit, even if Clear cookies and site data when you quit Chromium is disabled even if chrome://flags/#same-site-by-default-cookieschrome://flags/#cookies-without-same-site-must-be-secure are both disabled
Chromium 79 crashes with teams.microsoft.com
For example:
https://chromium.woolyss.com/feed/windows-64-bit?stb=1 - Would include just stable releases.
Or maybe you could add a wildcard filter to search any tag like:
https://chromium.woolyss.com/feed/windows-64-bit?filter=ungoogled
https://chromium.woolyss.com/feed/windows-64-bit?filter=no-sync
I'm only interested in certain releases, so that's why I ask. Thanks for considering!
https://bugs.chromium.org/p/chromium/issues/detail?id=1097947
Cheers for the Win32 ungoogled update, the milkybars are on me!
-password manager won't save password
-some cookies, NOT ALL COOKIES (usually cookies that makes logins persist) get erased after chromium exit, even if Clear cookies and site data when you quit Chromium is disabled even if chrome://flags/#same-site-by-default-cookieschrome://flags/#cookies-without-same-site-must-be-secure are both disabled
Chromium 79 crashes with video conferencing (I think webrtc video)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v85.0.4181.0-r781571-win64
It is "experimental" because I opted Chromium into the Windows segment heap, which potentially could help with memory usage, especially on systems with many processor cores and lots of open browser tabs. Windows 10 version 2004 or later is required for support, otherwise Chromium will fall back to the Windows legacy heap for earlier OS versions.
https://chromium-review.googlesource.com/c/chromium/src/+/2163163
I did not notice any stability issues in a quick check locally, and Microsoft already is using the segment heap for its own current Edge Chromium builds anyway. No real idea on any potential performance impacts, though, since building with LTO currently is disabled here.
Examples:
- Stable (Hibbiki): https://github.com/Hibbiki/chromium-win64/tags.atom
- Ungoogled (Marmaduke): https://github.com/macchrome/winchrome/tags.atom
- AVX (RobRich): https://github.com/RobRich999/Chromium_Clang/tags.atom
How to get the ATOM URLs of any Github project?
Go to the "releases" page (like https://github.com/Hibbiki/chromium-win64/releases) then subscribe to the ATOM feeds.
@RobRich: Like ever, I like very much to read you and test your releases.
Interesting enough, I was only a few hours ahead of the curve this time, as segment heap support just officially landed in the trunk.
https://chromium.googlesource.com/chromium/src/+/d52a99dda8eec5936d0db15f59398b29c246786b
-------------
Win64 SSE2 build with Win10 (v2004) segment heap support. Polly and PGO optimized, though no LTO.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v85.0.4181.0-r781571-win64-sse2
Hi.Thanks for the Windows update. :)
It might not be an ideal fix, but it should work in the meantime. Details here for those interested:
https://bugs.chromium.org/p/chromium/issues/detail?id=1097947#c10
Thank you very much for the 86... sync update. H.265 is getting more and more important and is already used in DVB-T2 and partly also in media libraries and streams on the web.
Thank you very much that you've taken your time and resources to build this amazing chromium binary, I've a question though if I would like to have a Widevine support on my Chromium can I follow this guide that is stated here #widevine ?
Or can anyone give me some references on how to add the Widevine Components? Sorry for the noob question 😅
I am currently using https://github.com/RobRich999/Chromium_Clang avx2 chromium
Thank you
The newest 86... sync version by Marmaduke also has Widevine components.
https://github.com/macchrome/chromium/releases/tag/v86.0.4185.0-r769185-Win64
Hi! Thank you for your reply, but it is currently not possible if I want to use the RobRich compiled chromium? I've tried copying the WidevineCdm folders to the Chromium Folders but it's still not detected on chrome://components/
Congratulations! Now I have the 86... sync version on Windows 10 in use for 5 days and I can say: Everything ok, no issues, no problems - in use Intel graphics 530 and 630.
>> BTW, we might be dropping Win32 depending upon how my next build attempt goes. I have no real use for the Win32 build, and it has been causing lots of local build headaches here. I will let you know.
>> @Bernd: Prefer the stable version or the other development version.
Thats pity because this system is not able to use x64 since windows 8 (i tried, has win7 x64), but runs win8 and win10 ltsc very smootly. although i also own a more modern computer which is only for testing purpose for several win10 versions only x64. nevertheless it lacks other components i need for convenience and integration into my household.
anyhow i should be able to compile my own build if someone would point me out which compiler and build build and how to get the builds, ok?
Thank you. I added the "widevine" tag on the Marmaduke's win64 dev version.
@Bernd:
Check the #source-code sub-section.
@RobRich:
I added your #windows-64-bit AVX2 version. So now, you can update it on the site, yourself.
@Marmaduke:
- I added your #linux version. Like RobRich, you can update it on the site, yourself.
- Also I removed your Win64 dev "nosync" version from the site. I think this one is redundant and there are enough releases for the public. Hope you understand!😉
- Currently, a developer make a portable version of your "ungoogled" version. I contacted him to credit your work.
https://github.com/portapps/ungoogled-chromium-portable/issues/9
Anyway, thanks to all developers and users. 🙏
The Chromium and Ungoogled-chromium community is growing every day on the Web. 👍
When I created this website in 2013, the Chromium project was unknown to the public. Today, after...
- Opera (chromium) launched in February 2013,
- Google Chrome 64-bit launched in August 2014,
- Ungoogled-chromium launched in December 2015,
- Vivaldi and Brave launched in 2016,
- Microsoft Edge (chromium) launched in December 2018,
...Chromium is known to users looking for a free and open source web browser.
Chromium is a greatest project. This browser supports cryptographic encryption algorithms, when other browsers have no way to resolve a page with unsupported protocols and ciphers.
I want to ask some off-topic questions. I'm newbie at linux and android. Can you guide me (poke my nose) to linux and android system info (articles, links, books) about system administration and system setup on those platforms?
Thanks a lot.
> Win64 SSE2 build with Win10 (v2004) segment heap support. Polly and PGO optimized, though no LTO.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v85.0.4181.0-r781571-win64-sse2
This build crashes for me after opening on Windows 7. I tried with a new user profile, nada. Thanks, cheers.
Not to nag, i really appreciate your builds. It's been 28 days, are we getting new dev builds soon?
I'd love to try AVX/AVX2 version, but with Google sync enabled. Perhaps there may be version like that in the future?
Updated Win64 builds done and pushed to public.
Updated Win32 build now available. :D
> all-codecs
very appreciated because the "authors" build dont support video at all.
Quick FYI. Clearing history might hang with the current AVX2 build. Considering Win64 AVX2 takes *hours* to build for me, it probably will be a few days before attempting an update. Consider ccleaner or similar in the meantime if encountering the issue.
[EDIT] Reinstalled Chromium and history clearing is working again. Must have been some trivial local issue. Anyway.
Chromium.app.ungoogled-84.0.4147.89-rev1.zip
https://github.com/macchrome/macstable/releases/download/v84.0.4147.89-r768962-Ungoogled-macOS/Chromium.app.ungoogled-84.0.4147.89-rev1.zip
The dav1d (AV1) CODEC does not play nicely with polly optimisation.
thanks as always marmaduke for your loyalty to us
Hi.Many thanks for the updates
@Marmaduke if you can make an update for Android too. Thank you... :)
Thank you.
When I start chromium with flag --incognito, there are some symbols missing in the address bar. No forward/backward-button, new tab without text, settings button only visible when hovering.
When I start chromium in normal mode, everything is fine.
Opening a new incognito window when a normal instance is running already is fine, too . . . .
So the issue only occurs when I start chromium with the incognito flag set as the first instance.
Weird
---
Sorry guys, above was only an issue in connection with the material light incognito theme.
Looks like that theme is no longer compatible. Sorry again
If still happening, open about:gpu in another tab while playing the affected video(s) and look for possible video playback errors in the log messages at the bottom of the page.
Thanks for your ungoogled builds, I have used them for a few months. I get less video performance using v84 of your 32-bit build (higher cpu usage, sometimes causing stuttering). Not seen this before. v83 is fine though on same videos. Chrome stable channel (official) v84 has no problems on same videos. I'm not expecting to diagnose this, just posting incase you perhaps had issues building that could explain this rare case.
Thanks again.
I wish to compile Chromium for Windows from source, to make a build with all-codecs+ (Marmaduke), Widevine, etc.
- From which Chromium source have I to start?
- Which are the correct GN flags to use?
- How can I pass parameters to Clang? I have VS2019 installed.
- There are some patches to be applied to the source code before to start building?
Some links where I can start & study are welcome.
For my previous build tests I followed this lineguide:
https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md
In my previous attempts to build, I used the following GN flags, using the official Chromium sources see the webpage lineguide above), without any success (the resulting build is still a Debug build, very slow, h264,MPEG-4 file are not played at all and some errors are shown while starting).
is_official_build = true
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
chrome_pgo_phase = 0
current_cpu = "x64"
enable_google_now = false
enable_hotwording = false
enable_iterator_debugging = false
enable_nacl = true
ffmpeg_branding = "Chrome"
is_component_build = false
is_debug = false
proprietary_codecs = true
symbol_level = 0
target_cpu = "x64"
exclude_unwind_tables = true
remove_webcore_debug_symbols = true
enable_webrtc = false
enable_widevine = false
#icu_use_data_file = true
#syzygy_optimize = true
enable_hevc_demuxing = true
enable_ac3_eac3_audio_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
It seems that I do something wrong, no idea of what.
Many thanks in advance
what about:
media_use_ffmpeg = true
media_use_libvpx = true
blink_symbol_level = 0
Thanks,I'll try to add those flags and rebuild (uffff... other 5 hours of build time)
I hope I'm using the right sources this time: https://storage.googleapis.com/chromium-browser-official/chromium-84.0.4147.89.tar.xz
This one seems to be the latest stable version (as reported in Sources section #source-code)
I'll let you know the results.
Many thanks
Start with a trunk build for simplicity's sake. You can attempt branch builds later IMO.
Some of the attempted build options are out of date or unneeded, plus way overdone for an initial build attempt IMO. Let's pair down the options somewhat to try a more basic trunk release build.
target_cpu = "x64"
is_official_build = true
is_debug = false
is_component_build = false
is_debug = false
enable_nacl = false
proprietary_codecs = true
use_thin_lto = false
chrome_pgo_phase = 0
symbol_level = 0
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
Get that working, and we can go from there with build options and optimizations.
For the curious, that is a Mint 20 system RDP remoting into a Windows 10 system running Ubuntu 20.04 under WSL2 with graphics and audio support enabled. That is my current local setup anyway, but I am thinking about setting up SSH with X tunneling to remote into WSL2 as an alternative.
Hi. Great , thank you for the Android update. ;)
Compiler clang (+lld_linker +thinlto +pgo/afdo +polly +avx +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v86.0.4216.0-r792159-linux64-deb
Instruction scheduling and SIMD width have been optimized for the AMD Jaguar microarchitecture, though the build should still work fine with most x86-64 processors offering AVX support.
https://en.wikipedia.org/wiki/Jaguar_(microarchitecture)
The build is working quite nicely thus far in local usage with an older AMD A6-5200 quad-core notebook. Even using Vulkan GPU hardware acceleration. The OS setup is Linux Mint 20 with 5.7.10-050710-generic kernel and Mesa 20.2.0-devel running AMDGPU with RADV+ACO.
When you will be building next Chromium Ungoogled please consider removing this path as described in the issue:
https://github.com/Eloston/ungoogled-chromium/issues/1113
It breaks a lot of extensions and some interoperability when Chromium is the only browser (for example localhost authorization for apps like Dropbox or OneDrive that use loopback).
target_cpu = "x64"
google_api_key = "no"
google_default_client_id = "no"
google_default_client_secret = "no"
use_official_google_api_keys = false
is_official_build = true
is_debug = false
symbol_level = 0
is_component_build = false
strip_debug_info = true
enable_nacl = false
use_thin_lto = false
chrome_pgo_phase = 0
proprietary_codecs = true
ffmpeg_branding = "Chrome"
enable_webrtc = true
rtc_use_h264 = true
rtc_use_lto = true
use_openh264 = true
enable_hangout_services_extension = true
enable_widevine = true
enable_hevc_demuxing = true
enable_ac3_eac3_audio_demuxing = true
enable_mse_mpeg2ts_stream_parser = true
media_use_ffmpeg = true
media_use_libvpx = true
blink_symbol_level = 0
Testing it in the Video/Audio test page (https://tools.woolyss.com/html5-audio-video-tester) H263, H264/AVC, H265/HEVC and MPEG-4 files are still NOT working. And I don't understand how to solve this.
Also,while starting Chromium, I get this big error page. And I don't understand why.
Also the build is SLoooWW. I don't understand if it's a release or a debug version (I set the flags in GN but I still see the .pdb files)
Is there anyone that can help me to solve the issues?
Could someone write down a step-by-step guide on "How to build a stable Chromium release with ALL codecs enabled" starting from "Get the right sources and build it with the right compiler/linker/GN parameters/flags"?
Thanks! :)
How do you know that Chromium 84.0.4147.89 has the same security vulnerabilities as Google Chrome? Isn't it rather the added Google code for all the synchronization, spying and automatic updating functions? Do not panic! Google doesn't say which vulnerabilities are in itself.
https://chromereleases.googleblog.com/2020/07/stable-channel-update-for-desktop_27.html
Try having a look at Chromium source code. Can't think of a recent security issue that affected Chrome, but not Chromium.
The Google Chrome is chromium source code (ungoogled and no-sync) plus Google's own code with sync etc. What is the logic?
V8, WebView, SCTP, CSS, Skia, WebUSB (?) exploits are all applicable to Chromium, i'm not sure why this was even an argument in the first place.
I'd be grateful if someone with access to a DTK-2 would test the AV functionality of this browser, particularly the output of chrome://media-internals Hardware video acceleration is being used when the mojovideo decoder is used.
Sync • WebRTC • Widevine (enabled) • All Codecs • macOS arm64
Chromium.86.0.4218.0.arm64.sync.app-rev1.zip
https://github.com/macchrome/chromium/releases/download/v86.0.4218.0-r793075-macOS/Chromium.86.0.4218.0.arm64.sync.app-rev1.zip
SHA1 E8D15B2A245CE06B873D28B09C7BD43ACB5D6CAB
Hi. Thanks for Android Update.
@Hibbiki
Hi. Thanks for Windows update.
:)
Thanks for the latest stable Android release.
Please next time, if possible, keep the same package full name so it does update itself and you don't have to set it up all again from scratch 😅
Thanks also for you work on the Windows versions.
Suggestions URL with %s in place of query
for getting predictions for google in omnibox
After noticing some performance drops using marmaduke's ungoogled I did some experimenting:
Chromium v84.0.4147.89-r768962 was dropping frames when watching videos. I reverted to Chromium v83.0.4103.116-r756066, performance returned. I tested hibbiki's v84.0.4147.105-r768962, performance was the same as Chromium v83.0.4103.116-r756066.
So I wondered the reason? I notice with Chromium v84.0.4147.89-r768962 marmaduke used PGO but hasn't for other builds. While this is supposed to give a performance improvement I wonder if it is to blame. hibbiki's releases do not seem to use PGO (I have only tested their latest release).
Specs: ancient Core2Duo, 4gb ram, win7 x64 (its old, 480p is smooth, any higher stutters due to no acceleration...strangely debian manages 720p smooth)
Could PGO have been to blame? Has anyone else noticed similar performance drops using PGO, or marmadukes latest (v84)?
Thanks for reading all of this, and of course thanks to contributing builders!
if i do --force-dark-mode the pdf view in chrome also gets inverted.
i don't want that to happen. how do i deal with this.
Invariant load hoisting and stripmining prevectorization are back working with Polly. :)
I also dropped the Polly early inlining pass and lowered the LTO instruction import limit to hopefully help with code bloat. I am not too concerned about either.
I run Polly during clang and LTO codegen passes, so there are plenty of opportunities for inlining before Polly runs in LTO.
Setting the LTO import limit to 30 is the same ChromeOS is (was?) using with negligible performance difference and still three times higher than the project's own default limit for Windows. That said, I probably will drop it down to 10 for Win32 due to older and lower-power processors with smaller caches.
Hi. Thank You for the Windows Update.
:)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v86.0.4229.0-r796289-linux64-deb
----------------
@Anon6037 Welcome!
Also LLVM has updated the processor model used for x86-32 building, so those with processors later than the P4 might see a little performance bump. YMMV as usual.
There seems to be a single flag within the cef build that "enables proprietary codecs". I don't want to enable all of them, just h.264. Do I have to code out all of the others I don't want to block them?
Hi. Thank you very much for the very quick Windows Update :)
Cheers for the ungoogled update. Can I confirm PGO is not used for x86 build?
To be blunt; AV1 is a crap CODEC: on the Android (appropriate) platform VP8/9, HEVC and H264 are all hardware accelerated, but AV1 is not.
I did not use PGO or polly optimisation for the current Windows ungoogled build - x86; but, that is not the issue, on the previous build PGO, polly and LTO were not used for the DAV1D (AV1) CODEC; the problem was the lack of optimisation. The AV1 codec needs to be optimised LTO (and PGO), but does not play nicely with polly optimisation. The fact that on the macOS platform, on certain graphics card, there is an issue with polly optimisation would seem to suggest that the Chromium testing procedure is not particuarly rigorous nor adventurous.
Please create new release Chromium 86 win64. Thanks.
Please don't pressure Marmaduke. He will release the next "widevine", "all-codecs+", "sync", "win64" when he is ready to do so.
Remember, these Dev builds are being released by someone who is taking time out of their day to provide a build to the general public and get's nothing in return for doing so. Well, hopefully at the very least some patience and gratitude from everyone here. :)
Cheers!
Hello, Bad news...
I abandoned version 86.0.4229.0 (796260) • Sunday, 9 Aug 2020 it is so buggy
I tested the version 86.0.4233.0 (797989) • Thursday, 13 Aug 2020 more limited but with which I do not encounter the same problems.
Finally, I am using version 84.0.4147.125 (768962) • Tuesday, 11 Aug 2020 @Hibbiki which works perfectly.
Been using my current public AVX build here. Seems okay here.
I do know my current public AVX2 build has a minor issue with some GitHub pages, though it is the only site I encountered the issue. I might around to an AVX2 update today.
Go here http://ultrastream.eklablog.com/films-exclus-c28814232/45
Then look that http://www.allocine.fr/_video/iblogvision.aspx?cmedia=19568515
Video is choppy.
On other sites, unable to view videos ...
For me your video works nicely.
Demo: https://chromium.woolyss.com/f/video-chromium-robrich-avx2-86.0.4209.0-790620.mp4 (10 MB - 33 seconds)
Processor : AMD Ryzen 7 1700x (https://i.imgur.com/KWhSiOs.png)
Graphics card: MSI GeForce GT 1030 2GH LP OC (fanless)
Thanks Rob for all, like ever! 😉
@LUC77600 it is working here. Did you check about:gpu while playing the video to look for errors?
Playback via Chromium on my notebook at the below link. Intel Kaby Lake quad-core proc with GTX 1050 graphics.
https://drive.google.com/file/d/1x4q000x6Xn89OPovNjQeZeiuw34kf4ht/view?usp=sharing
Broken for me too in several ways but its 4229 so browser bug not bad build
I use Nvidia quadro K2000, last driver installe...
I don't know how to save the video on my PC or use the transfer links through Google tools or other ...
But to describe the problem quickly, the image changes dimension during the video at a regular pace: full screen and slightly reduced screen ...
https://pastebin.com/HnNfpKgC
Hi. Can you , if you agree do an update for Android. With all new fix of Bromite.
Thanks
Many thanks for your tireless builds! :)
I came here to add another strange video issue to the above mentioned: embedded videos won't work for me - unless in private mode. Not the end of the world, just peculiar.
I will try to push updated builds in the next day or two. :)
For older machines ungoogled uses slightly less resources because of the lack of 'components' (and their updating) and maybe because of the pruning of binaries in the build process.
Same problem for me. The hourglass runs as if the browser was looking for a file that cannot be found ...
@RobRich
if that can help
It seems to me that these 2 problems are similar.
Going through multiple servers lengthens transfer times. In the case of the trailer of "Last city of Z", the path is lengthened compared to this one http://www.allocine.fr/video/player_gen_cmedia=19567873&cfilm=223754.html and I the impression that the image format is lost periodically.
In the other case, we will look for a file through a server that may be "distant" and there is no feedback ...
But I'm probably wrong ...
Hi. Great ; thank you for the very quick Update.
:)
To know this you simply have to look at what ungoogled-chromium removes/modifies:
https://github.com/Eloston/ungoogled-chromium/tree/master/patches
List of patches to change usability and privacy
https://raw.githubusercontent.com/Eloston/ungoogled-chromium/master/pruning.list
List of binaries used during build process that are removed
https://github.com/Eloston/ungoogled-chromium/blob/master/docs/design.md#source-file-processors
Replaces references to google domains in source code with non valid web addresses
Also standard Chromium has 'field trials' and other auto-updating components such as flash player in chrome://components (ungoogled-chromium blocks component updating/installing), '-disable-component-update' can be used to disable components in standard Chromium if you wish.
Also is there a difference between running it via 'chrome-wrapper' or './chrome'? Everything seems to be the same but I noticed that Easystroke recognizes it as two different programs, 'chromium-browser' and 'chromium-devel' so I was wondering if one method is preferable.
chrome-wrapper looks like a bash script to perform post-install tasks so running once is enough
https://chromium.googlesource.com/chromium/chromium/+/master/chrome/tools/build/linux/chrome-wrapper
chrome would the main binary, anything else is probably also scripts (but im just guessing)
Thank you for this job. It works fine for me.
Always problems with the Henry++ launcher (2.57). It runs in a loop without seeing the new version installed ...
Of note I setup a paired-down Polly config to establish a baseline for running only during the LTO codegen pass late before the vectorizer, thus dropping the additional Polly pass I was doing during early during clang codegen. It might actually improve interprocedural optimizations via Polly.
That is a YMMV situation especially when combined with my ongoing efforts to reduce bloat to potentially improve processor code caching, but Basemark Web 3.0 looked inline with my expectations during a quick test of my latest public AVX2 build, so hopefully I am on the right track.
Hi. Thank you for 87.0.4241.0 (800773) • Saturday, 22 Aug 2020 ; 64bit No Sync.
:)
Revision 617e31799027e2f45ca53cba1e8fc0bc7a82eca1-refs/heads/master@{#800881}
Compiler clang (+lld_linker +thinlto +pgo/afdo +polly +avx +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v87.0.4243.0-r800881-linux64-deb
----------------
The default optimization levels for Linux building are all over the place. Clang can be Os, O2, O3 depending upon the code paths, while LTO is set to O2. Technically, there also is a O0 code path, but I will digress on the technical reasons for it.
When building with PGO/AFDO, it should make sense IMO to let LLVM deal with the code size optimizations since we have profile data available, so I have modified optimization levels to O2 except for the O0 path.
I have not done any benchmarks, yet, so YMMV.
[EDIT : ^Make that Oz, O2, O3 with Clang. Oz, as in stricter optimization for code size and no autovectorization. o.0 Anyway.]
On this version 87.0.4241.0 (800773) • Friday, 21 Aug 2020 (AVX).
Streams cause chromium cache abuse errors.
For example, in the event of a momentary interruption of a stream (network error), Chromium displays pieces of the stream that it has stored.
It sounds funny, but it's okay for a while.
That’s all for now.
----------------
Chromium 87.0.4244.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 9ca452aad21cc2afed505a4d14b83eac54dce308-refs/heads/master@{#800967}
Compiler clang (+lld_linker +thinlto +pgo/afdo +polly +avx +compiler_optimizations +linker_optimizations)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v87.0.4244.0-r800967-linux64-deb
Slammed back to O3 across the board for Clang and LTO codegen, along with Polly early in Clang and late in LTO. :)
Looks like I will be doing the same for the next round of Win64 builds, too, thus concluding yet another semi-annual attempt to reign in code bloat. Back to what generally works for me.... and likely most others as well.
Very much thanks for the 87.0.4243.0. A courageous step forward into the future - very fast and stable. Best use for IP-TV.
Thanks from me too. So you now build with PGO? Does that add substantial build time? Thanks if you have time to answer.
I use the old V3 API.
On the september 07, 2019 you said me : « […] Do not worry, old parameters like ChromiumType=dev-codecs-nosync-experimental will continue to work only for compatibility with older chrlauncher. I hide these obsolete parameters for people […] »
But since few days this link ( dev-codecs-nosync ) seem not to update : https://chromium.woolyss.com/api/v3/?os=windows&bit=64&type=dev-codecs-nosync&out=json
It reply :
[version 86.0.4185.0, revision 769185]
where I was rather waiting for :
[version 87.0.4243.0, revision 800872]
(https://github.com/macchrome/chromium/releases/)
Can I have a friendly reminder of the (obsoletes) possibles parameters that are they always usable with #API version 3 ?
FYI, I today use :
dev-official
dev-codecs-sync
stable-codecs-sync
dev-codecs-nosync
ungoogled-chromium
dev-nosync
I dropped :
stable-codecs-nosync
dev-pgo-nosync
dev-codecs-nosync-experimental
Hello,
I decided in July to clean the website. My explanation is viewable at https://chromium.woolyss.com/?all=1#comment-5977
(This link will show you all comments). A screenshot, if you prefer:
If you need a similar "dev-codecs-nosync" version, use other versions. All of these following RobRich builds have the H.264 codec support and are "no-sync":
- https://chromium.woolyss.com/api/v3/?os=windows&out=json&type=dev-sse2-nosync (SSE2 support for old computer)
- https://chromium.woolyss.com/api/v3/?os=windows&out=json&type=dev-nosync (AVX support for recent computer > 2011)
- https://chromium.woolyss.com/api/v3/?os=windows&out=json&type=dev-avx2-nosync (AVX2 support for recent computer > 2013)
About your comment, I see, I need to clean the API v3 too ;)
Thank you very much,
Regards
These Chromium project builds are very, very much appreciated.
Marmaduke has stealthily updated ungoogled!
Pages "won't load" or "getting random crashes" is not paricularly useful information.
Try to reset all flags to default settings
On chrome://flags/ page "Reset All" button
https://reviews.llvm.org/rGa6a37a2fcd2a8048a75bd0d8280497ed89d73224
It is something to seriously consider adding locally IMO when building with ThinLTO due to multi-threaded locking with the default Windows thread-safe global heap. I have been using it for months with no known issues or regressions to note.
You might need to edit rpmalloc source for it work.
Enabling preload probably does nothing on Windows, but anyway, enable override and preload in rpmalloc.c:
#define ENABLE_OVERRIDE 1
#define ENABLE_PRELOAD 1
Comment out the static asserts in malloc.com if hitting a build error:
// _Static_assert(sizeof(size_t) == 8, "Data type size mismatch");
// _Static_assert(sizeof(void*) == 8, "Data type size mismatch");
// _Static_assert(sizeof(size_t) == 4, "Data type size mismatch");
// _Static_assert(sizeof(void*) == 4, "Data type size mismatch");
I typically build LLVM without asserts enabled.
A couple of other allocators are supported as well, but YMMV on performance and memory usage. The patch started with rpmalloc, which is what I have been locally using for months now.
In theory it looks like mimalloc might be beneficial for building on lower memory systems, though it touched around five times as many memory pages as rpmalloc when test building LLVM, so wall clock build time was slightly slower in dev testing.
I have 64GB in my build box, I am still thinking about roiling a local mimalloc build for testing. If so, i will let ya'll know.
Chromium devs have a discussion on adding support in its LLVM checkout here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1111798
A fixed version was released for windows builds of ungoogled-chromium, version number is the same.
ungoogled-chromium-85.0.4183.83-2_Win64.7z
Note the '-2', please check you are using the fixed version.
Hi. Thank you so much for all the updates. Is possible an update for Android too ?
Thanks in advance...
The build uses O2 across the board so PGO actually can do its thing regarding size optimization of various functions, but I also enabled the newly introduced Machine Function Splitter optimization pass. MFS splits hot and cold function parts using PGO profile data for the goal of "decreasing fragmentation and improving icache and itlb utilization."
Additionally I am trying out a new feature to "Interleave to expose ILP for small loops with scalar reductions," plus I am running extra cleanup passes following the auto-vectorization passes.
I am seeing small performance improvements compared to my usual O3 builds in local benchmark testing. :) YMMV as usual.
BTW, Poilly is down to simply "-mllvm:-polly" only during link time optimization for the build. I will try to reevaluate its config in the near future.
And many thanks for your work, as usual :)
-----------------
Win64 SSE2 build updated. Same updated performance modifications as its AVX counterpart. Win32 to follow later.
----------------
Win32 updated. Same updated performance modifications, too.
An updated Win64 AVX2 build might be a day or few away.
----------------
Updated Linux build available.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v87.0.4255.0-r804541-linux64-deb
The previous sample-based AFDO profiling using a profile derived from the Android build has been replaced with instrumentation-based PGO profiling closer in technique to what the project has been rolling out for Windows an MacOS. One of the most immediately visible changes is the .deb installer file size is down about 10MB.
Otherwise, I have carried over my recently updated performance optimizations plus moved to expand Polly optimizations options.
I have yet to try the build on my primary Linux notebook, but it seems to be working fine under WSL2 on my Win10 build box.
----------------
The Kraken JavaScrupt benchmark of recent Chromium builds running on the same system. One via native Win10. Another under Ubuntu via WSL2.
I found similar results in SunSpider. Not a big deal or even a concern, but something mildly interesting IMO.
I rolled my recent changes into the AVX2 build, plus started adding back more optimizations to Polly. The end results looked pretty good in a quick round of benchmark testing.
------------------
Finally had a chance to run my latest Linux build on a native OS install. Working nicely here IMO, even with Vulkan enabled.
BTW, part of the Linux file size reduction is not just perhaps PGO replacing AFDO, but also a lowering of the LTO instruction import limit to 10. I built code at O2 since we have potentially more accurate PGO profiling available, too, versus the default project config of mixed Oz and O3 code paths for Linux builds.
I use Chromium (hibbiki latest) with h264ify extension to force h264 videos on youtube. This has worked great...until today! Some videos are showing the 'Your browser does not currently recognise any of the video formats available.' message. So I did some diagnosing and the videos in question are defaulting to AV1.
I am worried YT are removing h264 video support. Has anyone else noticed a change recently?Here is a sample (music) video: https://www.youtube.com/watch?v=aSkFygPCTwE
Does Chromium support AV1? I still can't play it with h264ify disabled.
Thanks guys.
You should try the enhanced-h264ify extension. This will allow blocking multiple video formats.
Thanks for the suggestion. But it seems AV1 was being blocked by h264ify anyway.
It's funny, 10 minutes after I posted I restarted the browser (incognito, so no cache to clear per se) and it was playing h264 (avc1) again with the extension enabled! I think this can be chalked up to a YT user experiment where they disable something or make a visual change, then monitor forums for complaints.
Sorry for the false alarm. But I hope it is just that and we don't see them dropping support when introducing av1 more widespread.
Thanks.
Thank you very much for the Android update...
@Hibbiki
Thank you very much too , for the quick Windows update...
:)
Thanks so much for "Chromium build 87.0.4259.0 (804906) • Tuesday, 8 Sep 2020 widevine, all-codecs+, sync, win64".
Greatly appreciated! Cheers! :)
Has anyone else noticed in the latest two builds of ungoogled chromium on windows that the middle mouse button scrolling has become very erratic, changing speeds way too rapidly as you drag the mouse up and down and that it's also very jittery?
I couldn't test this with the other builds and I use a 144Hz monitor.
Thanks for checking! Just tried Hibbiki's latest build and I have the same issue with it, then the latest v87 from RobRich, same issue.
Can't find any mention of this problem on the chromium bug tracker.
I think the problem is that scrolling accelerates like 6 times faster on these newer builds.
Normally, the further you move your mouse vertically from the point where you pressed the mid. mouse button the faster scrolling you get. but the acceleration curve seems to be totally messed up now, at least for me, no idea why, even tried it with empty profiles, using a GTX 1080 Ti
ungoogled-chromium-84.0.4147.125-1_windows.7z - doesn't have this weird issue so I will stick with that for the time being.
https://github.com/macchrome/droidchrome/releases/tag/v85.0.4183.101-r782793-Ungoogled-And64
=====================
Chromium v85.0.4183.101-r782793-Ungoogled-And64
@macchrome macchrome released this Sep 9, 2020
Chromium v85.0.4183.101-r782793-Ungoogled-And64
Chromium for 64-bit Android - Wednesday, 09 September 2020
Chromium 85.0.4183.101 (Official Build) (64-bit)
Revision 26317c7557ab33f01a03713219a869c2b59550d0-refs/branch-heads/4183@{#1767}
OS Android 9: SM-G960F Build/PPWS29.120-2
OS Android 64-bit: Only for Oreo 8.1.0+ & Pie 9 & 10
Official build
>>>> All Bromite patches applied <<<<
=======
HEVC and AV1
"No Search" option (Replaced Google search engine with nosearch)
LTO
AFDO
No Sync • No Widevine • ThinLTO • >>> Bromite <<< • HEVC
=======
arm64_ChromePublic_HEVC.apk
https://github.com/macchrome/droidchrome/releases/download/v85.0.4183.101-r782793-Ungoogled-And64/arm64_ChromePublic_HEVC.apk
SHA1 C56CDC110E3EFC95295FACF6FD4E28B07AA9B8D8
===========
HEVC patch derived from (Nik): https://github.com/henrypp/chromium/blob/master/hevc_support_new.md
Incorporates patches/techniques from https://git.droidware.info/wchen342/ungoogled-chromium-android
Incorporates patches from github.com/eloston
Incorporates patches from github.com/ungoogled-software
Incorporates inspiration from github.com/Zoraver
Expresses admiration for the great https://github.com/vit9696 (I've mastered OpenCore - reluctantly!)
Incorporates Marmaduke's imagination and the fact suckling from mummy's breast ia a distant memory!
And...the Byzantine Chromium Authors.
===
My builds are private builds, which I will withdraw if anyone requests.
I DO NOT DO SPOON FEEDING!
Thanks for your hard work.
Stay safe!
Please do not stop the publication of your precious works. If users have problems, it is mostly because of their corrupt OS installation, drivers or hardware components. - Thanks, thanks, thanks ...
one thing incase you haven't tested, try with hardware acceleration disabled
thanks for the suggestion, it doesn't make any difference unfortunately :|
size : 79.5 MB
link #1 : https://easyupload.io/uh64nz
link #2 : https://gofile.io/d/ANg9O7 (slow)
sha256: 26B63F62CE2E29794C54963BD9AF848A23A2797128643B8DDD662FC3368702DD
This is a 1080p 120fps mp4 video demonstrating the problem. (best viewed on a 120Hz+ display)
At this point I'm really just looking for feedback from anyone who might have the same problem, because I can't find anything wrong with my setup.
It could be a Vanilla Chromium / Upstream problem or something on my end, or both.
btw. the current Google Chrome v85 is doing the exact same thing.
[ Windows 10 x64 Enterprise v10.0.19041.508 | Intel Core i7 6700K @ 4.6GHz | DDR4 32GB @ 3200MHz | GTX 1080 Ti , Driver 452.06 DCH ]
Thank you for anyone providing feedback!
Thank you for the Admin for running this site!
Thank you for the builders for providing the best versions of Chromium that ever existed!
Try changing the flag "Percent-based Scrolling". - The problem is the mouse. Which mouse? Logitech? I had problems with Logitech. Then I removed the utilities and its drivers - the onboard drivers of the OS are completely enough. And check the settings in the system.
Thanks, this sounded very promising, but unfortunately it didn't help:
I removed "logitech gaming software", the logitech HID device drivers plus any remaining ghosted devices and then restarted the system.
I tried setting the flag, but didn't notice any difference.
(it's a G700 btw. so good guess:) )
https://www.howtogeek.com/437624/how-to-enable-google-chromes-new-extensions-menu/
i want the overflow menu again, not this slow crap.
any other switch or option for it?
This switch is now standard in Google Chrome and cannot be removed. It is also present in the Chromium version 87.0.4259.0 sync by Marmaduke (as in his previous version). This makes it easier to manage the extensions and to hide or show the buttons for the single extensions if desired.
can you re-enable the flag availability if you enable one of the 'temporaily unexpire' flags? example:
Temporarily unexpire M84 flags.
Temporarily unexpire flags that expired as of M84. These flags will be removed soon. – Mac, Windows, Linux, Chrome OS, Android
#temporary-unexpire-flags-m84
An updated Polly config, too. I was able to enable and significantly expand many options since I am running Polly only during LTO codegen, versus the time needed to run Polly during both Clang and LTO codegen.
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-allow-nonaffine",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-analysis-computeout=8000000",
"-mllvm:-polly-codegen-generate-expressions",
"-mllvm:-polly-delicm-max-ops=10000000",
"-mllvm:-polly-delicm-overapproximate-writes",
"-mllvm:-polly-dependences-analysis-level=access-wise",
"-mllvm:-polly-dependences-analysis-type=memory-based",
"-mllvm:-polly-dependences-computeout=5000000",
"-mllvm:-polly-ignore-aliasing",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-optree-max-ops=10000000",
"-mllvm:-polly-opt-outer-coincidence=yes",
"-mllvm:-polly-register-tiling",
"-mllvm:-polly-run-dce",
"-mllvm:-polly-vectorizer=stripmine",
# "-mllvm:-pass-remarks-analysis=polly",
I normally would not allow nonaffine writes as they can complicate Polly scheduling. However I am letting them proceed (for now) since I am able to contribute more build time and complexity to a single Polly pass during LTO codegen.
Probably the biggest crasher in Polly for me right now is PHI normalization, so it remains disabled. I might submit a bug comment to the mailing list sometime, though it is not really a big deal for us IMO.
One of the more impressive LLVM options added recently is the Machine Function Splitter. I suggest enabling it during clang codegen if building with PGO enabled. I have been using it in recent builds.
https://reviews.llvm.org/rG94faadaca4e1704f674d2e9d4a1d25643b9ca52c
https://bugs.chromium.org/p/chromium/issues/detail?id=1122950
It was fixed in this commit:
https://chromium.googlesource.com/chromium/src/+/7ce5fd6a9017536aa012501fddd59e19038ca898
It's already fixed in RobRich's latest avx2 build!
Cheers!
I've used Machine Function Splitter (MFS) in my current Windows dev build (Chromium v87.0.4259.0-r804906-Win64) and will do so in future Chromium release builds - Mac, Windows, Linux - when the default compiler supports MFS.
I've followed your lead, am using polly only during LTO codegen; particularly since discovering that "thin_lto_enable_optimizations" was disabled by default when building Chromium for Linux.
Appreciate the new link time polly parameters.
----------------
Speaking of Linux, I migrated the building of LLVM to GCC 10.x instead of the dated GCC 5.3 checkout the Chromium project uses by default. Not that I keep a record of timestamps, but it seems like LLVM might be a little faster building Chromium now. Could be placebo, too. Anyway.
I build clang/LLVM for Linux more or less the Chromium way: https://commondatastorage.googleapis.com/chromium-browser-clang/Linux_x64/clang-llvmorg-12-init-5627-gf086e85e-2-buildlog.txt - a bootstrapped PGO build using pgo_training-1.ii. Where I differ from the Chromium Auhhors is that I build the first stage compiler with clang.
STAGE I - Building bootstrap compiler 28m35.120s
/home/acer/cmake/cmake-3.16.4/bin/cmake -GNinja \
-DLLVM_ENABLE_PROJECTS:STRING="clang;lld;polly;compiler-rt" \
-DCMAKE_BUILD_TYPE=Release \
-DLLVM_TARGETS_TO_BUILD=X86 \
-DCMAKE_C_COMPILER=/volumes/disk2/clang-11.0.0/bin/clang \
-DCMAKE_CXX_COMPILER=/volumes/disk2/clang-11.0.0/bin/clang++ \
-DCMAKE_AR=/volumes/disk2/clang-11.0.0/bin/llvm-ar \
-DCMAKE_RANLIB=/volumes/disk2/clang-11.0.0/bin/llvm-ranlib \
-DLLVM_ENABLE_ASSERTIONS=ON \
-DLLVM_ENABLE_TERMINFO=OFF \
-DLLVM_USE_CRT_RELEASE=MT \
-DLLVM_ENABLE_LIBXML2=FORCE_ON \
-DCMAKE_EXE_LINKER_FLAGS= \
-DCMAKE_SHARED_LINKER_FLAGS= \
-DCMAKE_MODULE_LINKER_FLAGS= \
-DLLVM_ENABLE_PIC=ON \
-DLLVM_ENABLE_LLD=ON \
-DCMAKE_INSTALL_PREFIX:PATH=/home/acer/stage1 \
-DLLVM_POLLY_LINK_INTO_TOOLS=ON \
-DCMAKE_POSITION_INDEPENDENT_CODE=ON \
../llvm
time ninja
Hibbiki, @Marmaduke, @RobRich ; we are very lucky that you do the great work, which you do as chromium! I use ungoogled as my browser, and the resource consumption on my pc is minimal, I also have Hibbiki's. Warm greetings to all of you from my far away place in the world.
----------------
Updated Linux 64-bit build for Debian, Mint, Ubuntu, etc.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v87.0.4269.0-r808691-linux64-deb
Hi. Thank you very much for the very quick Windows update. :)...
However on my request to comply to the open source license of the Bromite patches, the issue was simply closed: https://github.com/macchrome/droidchrome/issues/5
@csagan5
Consider your request closed here, too. Go Away!!
@csagan5 is the Bromite developer and his request is valid in asking @marmaduke to abide by the open source license.
release the laytest android. we know its baysed on bromium cos you say so.
perhaps you should you take out a advert on broadway!!
Hi.Thank you for the update , no sync work great...
Could you please check with the internal staff?
Does this feature only appear after the Android 87 Canary version?
Because neither the developer version nor the 86 version appeared.
https://9to5google.com/2020/09/02/chrome-secure-dns-android/
thanks.
@Hibbiki: Thanks for your builds (using nosync, works great).
i want the overflow menu again, not this slow crap.
any other switch or option for it?
Why has the Android Chromium version recently changed its package id? Before it was "org.chromium.chrome" and now it is "org.chromium.chrome.stable".
This is giving us issues because it is not updating the already existing package.
Complain to Google about this! Or create your own build! Use Vivaldi or Opera or * or *!
Try posting to the github issue page if you haven't got a reply yet
----------------
Win32 build updated.
1) thanks for your work! :D
2) I do not know if only a my problem. With version: Version 85.0.4183.121 (Official Build) (64-bit) (by Hibbiki), is not possible to use Spotify, because automatically (when try to play a track) skip the first 8 / 10 tracks and play the 11th for only ten sec.
I tried to disable all extension and navigate anonymous but the problem persists.
Tested on a Chrome 85.0.4183.121 the issue is absent.
Thanks
I've also done a polly optimised version: takes 1.77 times longer to produce; not sure if it's worth the extra effort!
https://github.com/macchrome/chromium/releases/tag/v88.0.4284.0-r813632-Win64
I will probably try out your polly optimised version too!
Thanks again! I have tested the 813632 polly optimized with BaseMark Web 3.0 - with Intel HexaCore i5-9400 2.9 MHz (without turbo), graphics 630. It is 13% faster than the 813834, namely 813632 with 599.06. (Of course there are faster cards from NVIDIA etc.). I am very happy now.
Check widevine is working in your build, spotify requires this. Here is a test page, scroll down and check for tick next to widevine: https://bitmovin.com/demos/drm
Only hibbiki 'sync' builds have widevine, as per https://github.com/Hibbiki/chromium-win64/releases
Cheers!
@Marmaduke and @Hibbiki as always a big thank you for the updates you don't know how much I and the community appreciates them! Cheers!
Thanks for the Update.
Open frame (Video Frames) in new Tab is gone in V86 or is it just in the ungoogled version?
https://github.com/macchrome/winchrome/blob/86.0.4240.x/patches/final.txt
Mupperty
----------------
@Marmaduke You can drop the Polly config back dramatically if build times are causing concerns. Outside of maybe some corner cases, the resulting general browser performance difference would be probably a percent or few at best.
Scaled back but still viable IMO for Polly during LTO codegen:
"-mllvm:-polly",
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-register-tiling",
"-mllvm:-polly-vectorizer=stripmine",
----------------
My build times have stretched into multiple hours each even on my 32-core build box, thus why I am pushing update intervals out to like two to three weeks.
I run other LLVM options beyond Polly, like extra vectorization cleanup passes, extra dead code elimination passes, extra loop scalar reduction optimizations, etc. Toss in a modified LLVM build, like for example using modified x86 target descriptions for certain builds. I am also pushing VS2019 optimizations when building LLVM, so the build times all add up quickly here.
Actually i can go even heavier into Chromium optimizations, including rolling back in some really low-level LLVM stuff I have taken out in recent months due to build time issues, but it is going to get even more ridiculous on my current hardware. Especially when we are talking about a percent here and there for whatever benchmark(s).
My latest Linux build: https://github.com/macchrome/linchrome/releases/tag/v86.0.4240.75-r800218-portable-ungoogled-Lin64 the time difference between a PGO and PGO/Polly compile was +13%.
The increase in build time pales into insignificance given Google's egregious abandonment of jumbo/unity.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v88.0.4294.0-r817403-linux64-deb
Admittedly I actually do that for a specific notebook here. Just figure I might as well push the builds to GitHub as well.
On a potentially interesting note, I am currently doing Linux builds using Windows WSL2.
Thanks.
Hi. If possible , an update for Android. It's great. Thanks...
MS has made a bug with the October updates that affects Intel Graphics 630 and HDMI. First of all the HDMI then very often did not output any signal when booting. A new update from Intel itself solved this problem, but not completely. Your 88* versions have problems with the audio track in MPEG4 videos. Either there is no sound or it is not synchronous with the pictures. The 86* version of Hibbiki does not have this problem. What is the cause?
There are two versions of v88 for windows: polly and non-polly optimised. The Intel 630 does not work well with polly optimisation.
I won't consider AV playback issues unless - particularly on dev versions of Chromium - the format of the video and audio stream is stated. You're using v88 of Chromium so make the comparison with the respective development release. Or at the very least use v86 of my (polly optimised) ungoogled build.
I do not know the cause of the issue, nor should you ask me; by doing a respective comparison the cause of problem could be ascertained: perhaps, polly optimisation.
Dev versions are inherently unstable.
@Daigo Hoping to have build updates within the next day or two.
I am experimenting currently with rolling back in some of those previously mentioned low-level LLVM optimizations, but I am hitting a crasher building a specific component.
I must congratulate you: Your Chromium 86* has much better rendering of moving vector-based Canvas elements than Google Chrome, as I can see in the Basemark Web 3.0 test. Diagonal lines are completely clear and not toothed, like Google. This is your secret.
uh-oh!
Yeah, not good. Although not classified as critical either.
Bug in FreeType font rendering library. BTW, does anyone know if Chromium-based Microsoft Edge is affected as well?
Or do they use DirectWrite or something instead of FreeType?
I have cleaned out the old MSVC stuff and related conditionals in....
D:\depot_tools\chromium\src\chrome\installer\mini_installer\mini_installer_exe_main.cc
....to resolve the issue; again for me locally. No idea if others are being affected or not.
Example here:
https://pastebin.com/xujUdMHt
I will try to get various new builds out later today or tomorrow. :)
Examples:
- https://chromium.googlesource.com/chromium/src/+log/86.0.4240.75..86.0.4240.111?n=100
- https://chromium.googlesource.com/chromium/src/+log/86.0.4240.75..86.0.4240.111?pretty=fuller&n=10000
- https://chromium.googlesource.com/chromium/src/+log/86.0.4240.75
- https://chromium.googlesource.com/chromium/src/+log/86.0.4240.75?format=JSON
@Marmaduke: Just for info, I reorganized the #mac section.
Like ever, thanks a lot to all developers and users. 👍
----------------
Updated Win64 AVX build now available. More to follow tonight or tomorrow.
----------------
FYI on an updated Polly config.
"-mllvm:-polly",
"-mllvm:-polly-allow-nonaffine",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-analysis-computeout=8000000",
"-mllvm:-polly-codegen-generate-expressions",
"-mllvm:-polly-delicm-max-ops=10000000",
"-mllvm:-polly-delicm-overapproximate-writes",
"-mllvm:-polly-dependences-computeout=5000000",
"-mllvm:-polly-ignore-aliasing",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-optree-max-ops=10000000",
"-mllvm:-polly-optree-normalize-phi",
"-mllvm:-polly-opt-outer-coincidence=yes",
"-mllvm:-polly-opt-simplify-deps=no",
"-mllvm:-polly-precise-fold-accesses",
"-mllvm:-polly-precise-inbounds",
"-mllvm:-polly-run-dce",
"-mllvm:-polly-vectorizer=stripmine",
# "-mllvm:-pass-remarks-analysis=polly",
----------------
Multi-level tiling is out, so drop these:
"-mllvm:-polly-2nd-level-tiling",
"-mllvm:-polly-register-tiling",
The features are there, but it turns out the needed modeling heuristics are not. No reason to waste any build cycles on them IMO.
----------------
More granular dependency analysis is out, so drop these:
"-mllvm:-polly-dependences-analysis-level=access-wise",
"-mllvm:-polly-dependences-analysis-type=memory-based",
They are seriously blowing up build time for certain components with little to no performance benefit.
----------------
Phi normalization and price inbounds are back working without blowing up or stalling build times.
Before the operand tree could cause an *exponential blow up* for multiple-use instructions, but a recent commit has added an additional caching mechanism to the operand tree, thus eliminating much of the previous build time cost.
----------------
I have also rolled back in some additional low-level LLVM tweaks for further evaluation; particularly related to register optimizations. YMMV.
----------------
Updated Win64 AVX2, Win64 SSE2, and Win32 SSE2 builds now available, too.
-------------------
FYI. It is not crashing the GPU process, so "whatever" for the most part, but Skia seems to be generating error messages in the GPU log with the current nVidia graphics driver on my primary notebook. Conversely, the current Intel graphics beta driver does not.
Turning off Skia is a workaround if affected and desired. Again, a "whatever" issue IMO, but nonetheless potentially annoying if needing to diagnose other GPU loggings. Rendering performance appears to be about the same either way.
chrome://flags/#enable-skia-renderer
-------------------
^And after a restart, Skia quit generating the GPU log errors. Okay.... so maybe disregard the above. Anyway.
Allow me a few words about "ZenMate VPN": I use the extension, but only temporarily, to bypass country locks and still be able to watch videos in the corresponding countries. This works really well. - On the first click I ignored the start page and closed it. I did not register and did not click on the free trial. The second time I opened the extension I could choose in which country I want to be virtually. Then a DNS server of Cloudflare (quad1) connects to a proxy of the selected country and then to the selected website. When I want to surf normally again afterwards, I deactivate the extension. Of course this is much faster and much easier than if I have to change the whole OS - with "Free Avira Phantom VPN" it is even easier, using the DNS servers of Google (quad8).
Browsec is classified as "Not recommended"... :-o
I haven't tried any, but this one gets a good review and they talk about a "generous free version": https://vpnpro.com/vpn-reviews/windscribe-vpn-review/
Note: ZenMate VPN in the free version is not a real VPN service provider, it switches together with the DNS service Cloudflare (quad1, 1.1.1.1) to a suitable proxy server, which interposes itself instead of the official provider and gives a different IP address instead of the one of the existing provider. This is only valid for the browser in which the extension is currently activated and not for the whole OS, other internet programs (e.g. MailClient) work with the official access and IP adress.
Many thanks for latest Android update
@RobRich
Many thanks for latest avx 64bit update
Sorry, my post was for @Jerry, but the "@Jerry" header disappeared when I copied it back after the failure to send my comment... ;-)
I also wanted to get (ungoogled?) chromium and i don't know yet which method to install and update is better. (chrlauncher or chocolatey?). how do you handle this?
chrlauncher:
Can be made portable (pass --disable-encryption and --disable-machine-id)
1 folder portable
Checks update every 48 hours (forgot the exact number)
Utilities to set as default (uses chrlauncher though, so no jump list support for "New Incognito Window")
Contributor ungoogled-chromium builds (currently: @Marmaduke), seems more regular builds are posted:
https://github.com/macchrome/winchrome/releases/
chocolatey:
Command line installation and update (be sure to add task scheduler entry for it)
Jump list support because uses chrome.exe directly
Chrome.exe sets itself as default
"Official" ungoogled-chromium builds (currently: https://github.com/tangalbert919), less regular builds, see:
https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/windows/64bit/
Those switches are not listed on peter.sh. only here
https://github.com/Eloston/ungoogled-chromium/blob/master/docs/flags.md
see also
https://github.com/Eloston/ungoogled-chromium/pull/591
I downloaded the ungoogled build via chrlauncher.
But I it seems that google sync is available? I thought it was removed?
@anon6232 Signing in shouldn't work
I used the setdefaultbrowser.bat from chrlauncher but everytime I klick on a link the edge browser opens. Is this a known problem?
Hi. Thank you for 88.0.4312.0 (823019) • Sunday, 1 Nov 2020 No AVX 64 bit. :)
Win32 updated now, too. I will try to have a Win64 AVX2 build available in the next day or two.
Updated Linux build for Debian, Mint, Ubuntu, etc. now available as well. Link:
https://github.com/RobRich999/Chromium_Misc/releases/tag/v88.0.4314.0-r823096-linux64-deb
Thank you very much for the new update. The canvas elements are again better displayed than in Google Chrome.
1. I disable Chrome and keep updated Android System WebView, Chromium compatible with built-in WebView?
2. Chromium features like AdBlocking applied to build-in WebView?
3. There is any issue with disabling built-in WebView and just using Chromium build?
4. Chromium builds, specially on Android, supports Google Safe Browsing service while Bromite patches applied?
Thank you again,
Stay safe.
Hi. Thank you so much for the very quick update... :)
Regards.
----------------
Speaking of graphics, a quick note of potential interest about the latest Intel GPU drivers for Win10:
"Performance improvements when using Chrome YouTube Media Playback."
https://downloadcenter.intel.com/download/29988/Intel-Graphics-Windows-10-DCH-Drivers
87 released, no? Any update on Ungoogled?
There is no release yet 87, there was a stable version 86.0.4240. 193 , but now 86.0.4240. 198 !!
My issue is that 1password only works with browsers that are identified as legit (such as Firefox, Safari, Chrome, Vivaldi and Opera) and ignores Chromium. :-(
They talk about a "browser signature"... is there any place where this info is accessible or is it deeply hidden in the code?
[EDITED: ... Ahem! "about:config" is of course for Firefox, sorry for the blunder. ;-) ]
- Use an alternative to 1password (https://alternativeto.net/software/1password/)
- or use a signed browser (like #windows-on-arm, Google Chrome, MS Edge, Opera, Vivaldi...)
https://github.com/RobRich999/Chromium_Misc/releases/tag/v89.0.4328.0-r827861-linux64-deb
Probably will have updated Windows builds in the next day or two.
Regards.
It seems that you are doing well; saw that you have updated Chromium. Cool and thank you.
Regards... :)
Google needs to get its act together: stop acting like an idiot first year Computer Science under-graduate (the it works brigade!) and actually think about what you are releasing.
Stop spamming us with sub-standard releases; get your excrement together.
Google, you're a bloated green-wash embarrassment!
First of all, thanks for the Nov 17 Ungoogled Win32 update.
Second, what do you "won't be building the initial releases of 87.0.4280.x"? Are you discontinuing your work on it or there's something remarkably wrong with version 87?
Thank you and keep up the good work!
Hi. Thank you for the quick v 87 update. Regards. :)
I might be mistaking but I thought I found the ungoogled updater https://github.com/NeverDecaf/chromium-web-store here a few months ago and I can't find it anymore, although you mention the windows ungoogled-updater by NeverDecaf.
I've been using it since I found it and it's working perfectly on Mac (and I suppose on Windows too). :-)
@Hibbiki! Thank you for your constant updates too.
@Marmaduke: Like all developers, thank you for your all work. I understand your point of view and the work done. Maybe, you could release only the first MAJOR version, if you prefer. ;)
@Aargl: ungoogled-updater is a python script. Source code: https://github.com/NeverDecaf/ungoogled-updater
Thank you for your work for builds. They work perfectly here.
Hi. Thank you for the new update. Regards. :)
Win64-ungogled . . . . thank you for the latest build !
https://github.com/macchrome/winchrome/releases/tag/v87.0.4280.66-r812852-Win64 was built with patches that were meant for v86?
Bro, that's a good question! There is clearly something wrong with ungoogled-chromium!
@Marmaduke
Explain how you managed to build the browser?
I was mentioning https://github.com/NeverDecaf/chromium-web-store for you to add it here, if you like. ;-)
It's an add-on specifically for the ungoogled versions of Chromium, for updating the other add-ons — otherwise they never get updated...
It shows a red number on its icon when add-ons updates are available, then you have to update them by yourself.
Marmaduke uses the current patches of ungoogled-chromium + the last stable version of Chromium (Note: security holes corrected in v87 ^^).
- Eloston's patches: https://github.com/Eloston/ungoogled-chromium/tree/master/patches
- Release: https://github.com/macchrome/winchrome/releases/tag/v87.0.4280.66-r812852-Win64
- Security fixes: https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_17.html
Do not trust anybody! I encourage you to check your network usage with tools like DevTools, Wireshark, tcpdump, top (to display Linux tasks), Fiddler, mitmproxy...
https://en.wikipedia.org/wiki/Comparison_of_packet_analyzers
@Aargl:
The link is in the official FAQ and on this site from the beginning! ;)
Interesting behavior on 4312 and 4330 builds, with some url in the address bar you can't open context menu by right-clicking an empty space of the address bar. Need to click on the url.
Tyvm much @RobRich for the updates btw :)
Not sure on the URL bar stuff. Like ya'll said, it could be a revision issue. Depending upon what I do for turkey day, I might issue another round of builds before month's end.
v85 to v86 - https://github.com/Eloston/ungoogled-chromium/pull/1210 : +1,720 / −2,109
v84 to v85 - https://github.com/Eloston/ungoogled-chromium/pull/1159 : +1,575 / −849
v83 to v84 - https://github.com/Eloston/ungoogled-chromium/pull/1109 : +1,165 / −1,025
v81 to v83 - https://github.com/Eloston/ungoogled-chromium/pull/1047 : +3,495 / −1,854
B6EA2EC0C3C060BE55B7BB278E8EF3C9F68625B7
Ah! Ah! So that's were I found it. :-D
Sorry.
Please rebuilding the build Ungoogled into the latest changes in the branch!
ox Bro, check this topic https://github.com/Eloston/ungoogled-chromium/pull/1261#issuecomment-731622375
it says: "Will test on windows tomorrow." !!
It crashes randomly on youtube pages and shows a black screen on full screen videos when you wake up your monitor.
Guys see this topic: https://github.com/Eloston/ungoogled-chromium/pull/1261#issuecomment-732008717
Merge pull request #1261 from Zoraver/master https://github.com/Eloston/ungoogled-chromium/commit/1f7cdef6dfa8f612afde8f988131f210612333e0
Please update Ungoogled by 87.0.4280.67
https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_17.html
chrome://flags/#disable-accelerated-video-decode
I think this is just some kind of regression in this build. It's not big deal, I can wait for the next iteration of your cooking. ;)
----------------
Speaking of graphics, ya'll might want to poke at hardware-accelerated GPU scheduling if running Win10 and a GPU compatible with the feature. Turned it off on my notebook, and Basemark Web 3.0 actually improved.
Hello,
I am seeing random crashes of Chromium 89.0.4330.0 win64 AVX. No consequence, just relaunch Chromium and reactivate the crash page.
Windows 10 20H2 system updated and drivers too.
I've noticed the same. No big deal, and please don't feel obligated to push another build just because we report these issues @RobRich. Build another whenever you want, i'm not here to beg. Ty :)
Sure, but that's not the only problem.
https://cryptauthdevicesync.googleapis.com
This service used by ChromiumOS (and derived) is responsible for syncing device metadata (metadata corresponding to each device on a given account) with the CryptAuth back-end.
- Source code: https://chromium.googlesource.com/chromium/src/+/refs/heads/master/chromeos/services/device_sync/
- Command-line flags: https://chromium.googlesource.com/chromium/src/+/refs/heads/master/chromeos/services/device_sync/switches.cc
CryptAuth is a Google service that manages authorization and cryptographic credentials for users' devices (eg. public keys).
https://chromium.googlesource.com/chromium/src/+/refs/heads/master/chromeos/services/device_sync/cryptauth_api_call_flow.h
Hi. Thank you for all explanation.:)
Regards.
I can't recall, but at what point are outdated versions marked with the "OLD" tag?
There is at least one Dev version here that is nearing the 2 month mark, and I can't recall what the criteria is.
Thanks! :)
Ahh I didn't realize it was specifically for stable versions, which is indeed important. It would be nice to see it activated for dev versions too after a fair considerable amount of time has passed. If that said Dev version is unable to be updated by a developer before the "OLD" tag is applied to it, it gives possible concern and reason for a user to move away from it to another version (AKA: Stable), until Dev version is brought back up to date. :)
--------------------
@marmaduke
Thanks for the very latest dev build "89.0.4342.0 (831777) win64, sync, widevine, allcodecs+"
Much appreciated!
Cheers! 🍺
----------------
A follow-up on a previous post. Disabling hardware-accelerated GPU scheduling appears to have resolved a rarely occurring but nonetheless intermittent issue on my primary Win10 notebook with Intel+nVidia graphics. The 3D performance difference generally is around 1-2FPS in most reviews anyway, so whatever IMO.
https://www.google.com/search?q=hardware-accelerated+GPU+scheduling
https://duckduckgo.com/?q=hardware-accelerated+GPU+scheduling
Thank You for the Update 89.0.4343.0 (832360) • Wednesday, 2 Dec 2020 ; modified all-codecs no-sync win64.
Regards :)
----------------
Note my Linux build has been promoted up to my release repository. It no longer is tuned specifically for AMD Jaguar, though it still does require AVX support. Currently it also requires libc 2.35.1, so it will need a rather modern version of Debian, Mint, Ubuntu, etc. to work.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v89.0.4344.0-r833256-linux64-deb
It might not follow the same release schedule as Windows builds, but I will try to keep the Linux build updated as possible.
Hi. Great, thank you very much for the update. Regards...
https://wicki.io/posts/2020-11-goodbye-google-fonts/
....due to change in how Chrome now caches content.
https://developers.google.com/web/updates/2020/10/http-cache-partitioning
Hi. Thank You For The Update. Regards...
So many thanks
Anyone else remember the old Chrome Comic page 26
https://www.google.com/googlebooks/chrome/small_26.html
Does that remain true, or have google been trying to add too much bloat that they are themselves undermining its original promises, by providing more and more complex holes/mistakes to be manipulated?.
I ask because it seems to me they are having to shore up exploits a lot more frequently, and the "Jail" is maybe not as effective as we all once hoped it would be.
Chromium is more secure than Firefox.
Point of view of different security experts:
2020: https://madaidans-insecurities.github.io/firefox-chromium.html
2020: https://grapheneos.org/usage#web-browsing
2018: https://marc.info/?l=openbsd-misc&m=152872551609819&w=2
2017: https://news.ycombinator.com/item?id=13623735
2016: https://medium.com/@thegrugq/tor-and-its-discontents-ef5164845908
The pwn2own (the hacking competition) has much higher points/bounties for finding Chrome vulnerabilities than finding Firefox vulnerabilities:
2019: https://www.zerodayinitiative.com/blog/2019/1/14/pwn2own-vancouver-2019-tesla-vmware-microsoft-and-more
2017: https://www.zerodayinitiative.com/blog/2017/1/18/pwn2own-returns-for-2017-to-celebrate-10-years-of-exploits
https://github.com/RobRich999/Chromium_Clang/releases/tag/v89.0.4349.0-r834134-linux64-deb
I have dropped the AVX requirement.... for now? I have Linux coming and going on various systems, and I not too inclined to roll multiple builds with different SIMD levels for Linux at this time. Maybe later if/when I ever update the build box.
Will there be a separate build for when Mac changes over to ARM?
I see at https://omahaproxy.appspot.com/history.json for Chrome they are starting to differentiate between "mac" and "mac_arm64" for the OS.
Thoughts? (Especially from @Marmaduke ?)
Thanks for all your hard work by the way :)
AFAIK, there still are needed commits for establishing a M1 target in LLVM, though I suppose Apple could land commits to its own XCode branch of LLVM before sending them upstream. In LLVM land, I think the MacOS 11 triple still targets A13 for now.
YMMV, as the only "Mac" I currently own is an ancient PowerBook G4. ;p
Binary sizes are up slightly, but optimizations are as well. Looks okay here so far, but YMMV as usual.
But on some sites I can't bypass cloudflare's "checking browser" thing. It gets stuck in infinite loop. I've noticed this behavior with 4343 and 4349 builds. New experiments from Google, I assume.
BTW, I would suspect any installed content filtering extensions if routinely encountering Cloudflare Browser Integrity Check (BIC), as the service can trigger on certain HTTP headers or even just a lack of a viable browser user-agent string.
heh, I tried to change the user-agent to Firefox, it worked, BIC allowed me to go to webpage :)
chrome://flags/#freeze-user-agent flag made Chromium version in user-agent 89.0.0.0, BIC still does not give access.
----------------
Updated Win64 AVX2 build now available.
hope you ok with noob questoin.
is there anyway to add patches from example github /patches/extra/ungoogled-chromium/ to an existing build and .exe that one has? Or only way is to build like
source code- prnue - patches- etc?
thanks
If willing to undertake the process, building Chromium tends to be more time consuming than outright difficult to accomplish IMO.
Hi. Could you plan when you will have time an update for android.
Thank you.
Chromium 89.0.4353.0 (Official Build) (macOS_arm64)
Revision 4345fb8e2b4613593965a8a9ebbb7aa0c28d7803-refs/heads/master@{#836066}
OS macOS Version 11.0.1 (Build 20B28)
- only for macOS_arm64
- official build
- Xcode 12.2 (12B45b)
- macOS SDK 11.0 (20A2408)
Sync • WebRTC • Widevine
Chromium.89.0.4353.0.sync.app.zip
https://github.com/macchrome/chromium/releases/download/v89.0.4353.0-r836066-macOS/Chromium.89.0.4353.0.mac_arm64.sync.app.zip
SHA1 E99D55FCBB062A855512226289A2371B0C85381E
INSTRUCTIONS: unzip; xattr -rc Chromium.app
Test Codecs at https://tools.woolyss.com/html5-audio-video-tester/ (and let me know)
Chromium 87.0.4280.88 (Official Build) (macOS_arm64)
Revision 89e2380a3e36c3464b5dd1302349b1382549290d-refs/branch-heads/4280@{#1761}
OS macOS Version 11.0.1 (Build 20B28)
- only for macOS_arm64 (Apple Silicon)
- official build
- Xcode 12.2 (12B45b)
- macOS SDK 11.0 (20A2408)
No Sync • Codecs+ (HEVC, etc)
Chromium.app.ungoogled-87.0.4280.88.arm64.zip
https://github.com/macchrome/macstable/releases/download/v87.0.4280.88-r812852-Ungoogled-macOS/Chromium.app.ungoogled-87.0.4280.88.arm64.zip
SHA1 6B7E90B680BFCAC81F84455603E716103D77D634
Additional information: https://chromium.googlesource.com/chromium/src.git/+/master/docs/mac_arm64.md
Chromium for macOS_arm64 - Friday, 11 December 2020 Chromium 89.0.4353.0 (Official Build) (macOS_arm64)
says the file is damaged on M1, 11.1 OS. The 87 build posted later loads fine.
Appreciate the feedback.
I don't have access to Apple Silicon: would you test the functionality of the codecs - particularly HEVC/H265 https://tools.woolyss.com/html5-audio-video-tester/
CPU usage on the chrome(renderer) process is ~37% when watching the HEVC L3 video.
Thanks.
Good to have confirmation that HEVC works. CPU usage seems a bit on the high side and would suggest that HW video acceleration is not been utilised. On the Android (9+ 64-bit) platform HEVC is HW accelerated.
I have two questions: I am using the version installed from chocolatey, however, the valid version there is 87.0.4280.66, while the current version (87.0.4280.88) indicates that "Validation Testing Failed". Is it safe to update to the latest version? My other question is: when I click a link to a Zoom meeting, unlike Chrome or Edge, it doesn't open the app. Is this due to a configuration or a bug?
Hey, I've noticed that between your Ungoogled Chromium 83 build and latest one (86) there was difference in package name. Old name was "org.chromium.chrome" an new one is "org.chromium.chrome.stable" which breaks update compatibility. Do you know what gives, was this your mistake when building APK?
https://github.com/Hibbiki/chromium-win64/releases/tag/v87.0.4280.88-r812852
https://github.com/macchrome/chromium/releases/tag/v89.0.4342.0-r831777-Win64
can you updated the website?...
As reported here previously by user @Daigo: https://chromium.woolyss.com/?all=1#comment-6280
This behavior doesn't happen with Chromium vanilla from here: https://chromium.woolyss.com/download/
It does on Rob's builds, even with clean profile/installation.
There's also this website, ghacks, where text is in front of the images, as you can see here:
Again, this also does not happen with Chromium vanilla, it displays them well:
It does on Rob's builds, even with clean profile/installation.
@Jerry, not sure if i can mention other websites here, if not, then please delete the above.
Just my feedback as considering the above either this got fixed recently by Google (after latest build by Rob - 89.0.4349.0 (834217)) or is something in Rob's configuration affecting these.
Ty
Thank you for the christmas gift :) , android update. Regards ...
Merry Christmas! Happy Holidays!
And happy holidays to all!
Merry Christmas and all the best wishes
----------------
Clarifying my earlier post:
"The project does not test code above O2" on Windows. There are a few components built at O3 on some platforms.
----------------
I might be adding another OS platform to my builds depending upon how it works out. Possibly more info to follow.
With your recent update - 89.0.4367.0 (839243) avx - both issues i had previously listed have been fixed.
Thanks and happy holidays to everyone!
Hello from a fan,
I use the start page shortcuts a lot. In this latest version, the history replaces 2 of the 8 sites stored on the home page. In addition, these historical links are presented without an icon ...
I would like to know where these homepage sites are saved.
Thank you.
PS: this version 89.0.4367.0 (839243) • Thursday, 24 Dec 2020 (AVX) is very fast, it is very pleasant.
---------------------------
Linux build update:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v89.0.4368.0-r839313-linux64-deb
Thanks!
Hello
I put "Repeatable queries on the New Tab Page" on disable.
It seems good now.
Thanks
I've spotted yet another issue with your builds, and as before, this issue is not reproducible on Chromium vanilla (todays builds) or even with Marmaduke's build - 89.0.4342.0 (831777) • Monday, 30 Nov 2020
It does on yours however, even with a fresh profile/installation.
As always, just leaving feedback, no need to push another build(s) just because of this.
Regards
--------------
Duh, forget to describe the issue on above comment.
The website in question: https://forums.blurbusters.com/search.php?search_id=active_topics
The issue:
I am on an iPad right now, but IIRC, there used to be an about:flags related to LayoutNG. If curious, check if still there and try disabling it to see if the issue goes away.
----------------
Looks like the LayoutNG flag is gone. Anyway.
----------------
I mentioned maybe another OS platform awhile back. I was considering building Chromium for FreeBSD, as I used to be a PC-BSD user years ago. I do not really feel like dealing with it right now after the efforts just to get a working DE, audio, drivers, etc. on a FreeBSD install under virtualization. Maybe sometime later.
I merged your respective comments.
I checked the issue but I think it is a problem about the HTML source code of the website and the layout engine. Note there is no issue like that on other websites using the same phpbb forum engine and same page:
- https://forum.mxlinux.org/search.php?search_id=active_topics
- https://forum.audacityteam.org/search.php?search_id=active_topics
- https://forum.videolan.org/search.php?search_id=active_topics
- https://forum.openoffice.org/en/forum/search.php?search_id=active_topics
@RobRich:
Your #linux release is on the site, now. You can update it yourself! ;)
Ok about FreeBSD.
A fresh installation on a new tablet with Android 10 shows that connecting a Bluetooh mouse it cannot close tabs with a mouse wheel click nor open a link on a new tab using mouse right button. On an older table with Brave Browser all that works (same bluetooh mouse). I would not install Brave on the new tablet to test this.
Tanks,
Angelo.
HAPPY NEW YEAR TO EVERYONE ABOVE AND TO THE ENTIRE CHROMIUM COMMUNITY!!!
Cheers!
~Dustyn~
----------------
Since we are rolling into a new year, Win64 AVX r839847 represents a cleanup and re-baselining of my optimizations. Optimized paths are back up to O3, while Polly is back down to a more conservative configuration. Basically I am cleaning out accumulated cruft. Any performance changes aside, various browser features I quickly tested seem okay.
"-mllvm:-polly",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-vectorizer=stripmine",
# "-mllvm:-pass-remarks-analysis=polly"
I still need to do some performance testing, then look into what other optimizations might get back into or added to the mix, though I suspect performance should be fine as is. Some of the optimizations in my mix have been features added for whatever reasons but later seemingly abandoned by LLVM devs over the years of the project's development, so it is time to locally refactor IMO.
Happy New Year!
Angelo
I will try to have the other Windows builds updated today or tomorrow.
Report to https://github.com/Eloston/ungoogled-chromium/
Thanks for the Update... :)
Regards.
Thanks you for the new very fast Chromium.
Anyway, hopefully Windows builds are okay. Should know something in awhile.
Performance looked okay in a few quick benchmark runs. Let me now if encountering any serious performance regressions.
Thanks for the updated stable! Works good (as always).
Tiny question: There are 2 .manifest files in this release. Can I delete the old version .manifest file? Just want to keep it clean. Thanks again.
I will have to think a little more about similar optimizations for Win32, as I tend to try reigning in possible bloat due to typical end-user system memory limits there.
Linux still is a question mark. I build LLVM locally using GCC 10.x, so I might have to pull an LLVM project nightly build and see if it is maybe a local compiler issue affecting building there.
----------------
@Anon6379 You should fine deleting in the previous manifest file.
One question only: why don't you build a Win64 AVX2 version for stable chromium?
Thanks for your works.
I used to think that your O2’s, O3’s optimizations or whatever is useless in real world but this 89.0.4384.0 (avx2) version seems pretty much nippy / rapid to me.
I would have to test this with benchmarks and real numbers but maybe there really a difference finally…
In short, the most important being the fact that you allow all of us to always have a super recent Chromium.
Note: Also thanks for the Linux version which I use in Debian and also works great!
Note2 : Do you have a familly or similar ? You seem to have worked on Chromium and around Christmast and around Eve…
----------------
@Anon6383 Thanks, too. The latest performance difference probably is related to changes around instruction and register scheduling. Outside of the usual stuff with clang and lld optimizations like O3 and lto, I am dealing with tweaking options deeper inside LLVM.
BTW, no significant other or children, so yeah, I have some free time to poke at Chromium as a hobby.
----------------
Appears the Linux SSE2 building issue is affecting Win64 SSE2 as well, so it is something in the difference between instruction set selection. I am thinking maybe it is happening in Polly. It could take awhile to track down the underlying issue.
Anyone else the same?
I am still tracking down my LTO build issue with SSE2, so I probably will be rolling new builds across the board in the next day or two anyway.
Hello
+1 "status_access_violation" with last version 89.0.4384.0 (841850) • Sunday, 10 Jan 2021 AVX Win64...
For some videos, not systematically.
CPU, memory issues as I read
Or codec problems
I don't understand...
Looks like it was more a revision issue than an optimization issue.
I have a question about running two versions of Chromuim at the same time.I often require different sessions, meaning two profiles and two installs (not two windows)
I've noticed some strange behaviour and wondered if there was a guide out there?
Cheers!
does anyone know if ther's some open source chromium based browser with changes to the UI in code (no extensions)? For example, add (and handle) a custom status bar with buttons, add a title, sliding panels, etc.etc.?
If someone knows something about, please let me know
Many thanks
Rob
Hi. Thank you for the Ungoogled Update.
Regards... :)
Latest Ungoogled highly appreciated, many thanks for your efforts !
FreeSMUG used to be my source for keeping my mac browser current. Unfortunately, they have discontinued providing new builds. Does anyone else maintain up-to-date mac builds of the stable version? The ungoogled version seems to receive frequent updates, but I have found that I don't really care for it and it seems unstable on one of my systems. So I'd be more interested in a "googled" version. TIA!
Build it yourself!
maybe look at how a portable version is setup: https://portapps.io/app/ungoogled-chromium-portable/#modifications
Admittedly I have no use locally for Win32 builds. I suspect Hibbiki and Marmaduke are in similar situations, too.
https://www.xda-developers.com/google-cracks-down-third-party-chromium-browser-chrome-sync/
But I can see it being useful for people who don't care, does this mean Chromium builds here would also need to not include it?
Hello.
I am using Chromium in portable version with Henry ++ Chrlauncher configured for automatic Chromium update.
Although the latest version fixed the video issues, Chromium was slow and "fell asleep" on a blank page when I was no longer working on my PC. Ctrl + R didn't work, but it was enough to minimize the window and then maximize it to make the blank page animate again (???).
I decide to do a big cleaning. I delete the Chromium folder (portable folder) and by chance I find a Chromium / Profile folder in AppData / Local. This Profile folder contains information about the latest installed version. I also delete it because in the Chrlauncher script the Profile folder should not be there.
Starting with a fresh installation of the latest AVX Win64 version, there is no longer any problem. Chromium has become very fast again.
So, I am wondering about the management of the different versions (stacking), the browser reset options, the history cleaning and about this folder in AppData ...
This is my last experience as well as my last thoughts.
Thank you for your attention and your work.
About Chrlauncher and portable, admittedly, I have little to no idea about them. I do not generate the portable version. AFAIK, Jerry appears to have a script to do that when I push new build links to the listings here.
Hi guys! I'm unable to import an html bookmark file generated by Marmaduke's Chromium Mac Ungoogled, be it in Marmaduke's Android version or in Bromite, I always get an error "insufficient memory" although I've got 1.5 Gb free...
Is it a known issue? (I'm using LineageOS 9 on a Samsung S6)
This will become an issue when Sync will stop working — I must say that I haven't tried Sync neither, as it's a phone someone gave me and I've not used it extensively yet...
I'm going to try Chromium instead of Mozilla Firefox browser. I'm don't trust Firefox Privacy anymore. They are going to censorship internet.
https://twitter.com/mozilla/status/1347633954497548289?s=20
Please help clarfiy this. thanks!!
----------------
@PA I have not really followed the issue since I do not use sync, but AFAIK the changes largely relate to third-party stuff like extensions. I doubt you will see any changes to basic sync features if creating and using you own personal API keys. YMMV, of course.
Is it even only possible to discart it from building and stay on/keep [Manifest 2]
Please help clarfiy this. thanks!!
-------------------
Is there a way to use chrlauncher with google chrome?
I’m currently running Marmadukes 89.0.4342.0 (831777) which is from 2020-11-30
Is that version still ok to use?
If not, how can I downgrade to Hibbikis 87.0.4280.141 (812852)
(I want sync, you see)
Running the mini-installer does nothing, deleting everything but the user- profile folder within the Chromium folder doesn’t work either.
Any tips?
Thanks
An automatic downgrade from V89 to V87 is unfortunately not possible. I have deleted the Chromium with the program "Geek Uninstaller". But before that I copied the folder "User Data" in users/NAME/local/Chromium to another folder. Then I used the mini_installer of Hibbiki's version 87. After that I replaced the folder "User Data" with the old folder of this name, which was saved before. This is the easiest way to do this.
I guess I’ll try deleing the entire chromium folder next…
I recommend only using the latest versions of Chromium (stable or later). The reason being once a security patch is in the source, even if the bug report is still private, anyone can see the code changes and (try to) make an exploit for it. A sandbox wont protect you from bugs in the browser if you rely on this.
D:\depot_tools\chromium\src\build\config\win\BUILD.gn
....
"Chrome currently requires SSE3."
I will update the labeling of my upcoming formerly SSE2 builds at GitHub accordingly.
Taking a look at news about planned Chrome changes, apparently the requirement landed in v89 without me noticing it.
----------------
Here we go....
Commit: https://chromium.googlesource.com/chromium/src/+/5bb2864fdd57e45c84459520234b37a01e7a015a
Bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1123353
Design doc: https://docs.google.com/document/d/1QUzL4MGNqX4wiLvukUwBf6FdCL35kCDoEJTm2wMkahw
The design document specifies the next SIMD goal will be landing the requirement for SSSE3. No ETA on that change, yet.
"Jumping to SSSE3 would let us enable a fast path in snappy, and perhaps other libraries. This jump would also allow us to remove a dynamic dispatch alternative in each of the following third-party libraries: BoringSSL, dav1d, libaom, libvpx, PDFium, Skia."
SSSE3 adds 16 more instructions to SSE3.
https://en.wikipedia.org/wiki/SSSE3
I was a Mozilla Nightly user for years before that. I still keep it installed and routinely updated for compatibility testing, the rare site broken in Chromium, and similar.
Hi. Thank you for the windows quick update...
Regards. :)
Thanx @Hibbiki for update!
Basically I am appending the SIMD requirement to the build header, plus I have added an AVX build for Linux.
Current builds:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v89.0.4387.0-r842692-win64-avx2
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4394.0-r844986-win64-avx
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4394.0-r844986-win64-sse3
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4394.0-r844987-linux64-deb-avx
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4394.0-r844987-linux64-deb-sse3
Win32 will be like the following when released, probably Thursday:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4394.0-r844986-win32-sse3
----------------
Win64 AVX2 building is behind slightly due to that particular system being offline for hardware repairs. Hoping to have it fixed by weekend.
----------------
@Jerry Sending ya' an email about the changes. TIA!
Sorry about my comment above. New measurements: equally fast. Thanks again for the excellent work.
Error code: STATUS_ACCESS_VIOLATION
Thank you for the up-to-date, stable, Mac build!!
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4396.0-r845617-win64-avx
YT and Tw working here during a quick test.
Please let me know if there are any significant performance regressions.
Win64 SSE3 currently building.
A thank you from one of your 32-bit users.
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4396.0-r845617-win64-sse3
Hello,
For me v90.0.4396.0-r845617-win64-avx, Hat's Off !
Thks
I rolled back to a subset of my optimizations. Now I get to find which specific optimization is the underlying issue.
----------------
Win32 SSE3 updated build:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4396.0-r845617-win32-sse3
----------------
Quick FYI for Mamaduke and any others using Polly when building on Linux. As of a recent LLVM revision, apparently Polly is no longer working via LLD ldflags when using ThinLTO. While it *might* not be as optimal, you still can run Polly early via Clang cflags for now if desired. I suspect that is what I will be doing until whatever the cause is resolved.
Think I might have found a responsible commit. Having to rebuild its parent LLVM checkout to verify. It could take awhile to resolve at the project level assuming the suspect commit is responsible.
----------------
Well, that was not the right commit. Anyway. Maybe poke at it more later.
----------------
^Actually it appears I could be wrong. o.0
The "issue" is not probably an issue at all. It looks like only certain build targets now qualify for LTO optimization above LTO=0 to speed build times.
Take a look here:
https://source.chromium.org/search?q=//build/config/compiler:thinlto_optimize_max&sq=&ss=chromium
LTO=0 is basically more or less just multi-threading linking. LTO=2 or above invokes levels of actual link-time optimizations. BTW, YMMV on what worthwhile optimizations LTO=1 does.
Anyway, IIRC, I recommended trying something like the above a long time ago in an ongoing dev discussion regarding build times.
I will have to redo placement and invocation of some of my extra optimizations as a result.
----------------
Clang is invoking LLD linking via the clang++ -fuse-ld=lld option for building Chromium on Linux. Yay?
On Windows ninja justs call LLD directly. I never really looked into it on Linux, but I suspect it did the same there until recently. ??
Reason? Trying to pass "-Wl,-mllvm,-polly" via a LLD ldflag when using LTO no longer works. Sigh. Of note Polly is not core to LLVM.
However an option core to the LLVM internals like "-Wl,-mllvm,-enable-local-reassign" apparently will pass through the fuse.
TLDR? Run Polly at its early position in Clang when building on Linux for now.
----------------
BTW, here is the Chromium commit for those curious:
https://chromium.googlesource.com/chromium/src/+/1cda6e7869534d75defd1b3a86cbdd38e562f3fd
Build times on the dev's system do look considerably better according to the commit.
ThinLTO caching should (or might?) be working without file leakage on Windows, too. Details here:
https://bugs.chromium.org/p/chromium/issues/detail?id=871962
https://reviews.llvm.org/D94962
My setting of link-time code generation to O3 for the select targets is just a matter of a different code placement in the build config. No big deal there.
I might have to break up parts of my Polly config to correspond to the two LTO optimization levels.
For example, running stripmining on the LTO O0 targets probably is a waste of time due to a lack of autovectorization. I might try -polly-vectorizer=polly instead there, assuming Polly's own vectorizer no longer crashes on Chromium code, along with maybe the Polly inliner since there is no link time optimization to do LTO inlining pass.
Conversely, I could continue with the preferred -polly-vectorizer=stripmine for LTO O3 to let LLVM deal with autovec there.
Yeah, potentially lots of "my mileage may vary" (MMMV?) stuff of course. I will try to have something out in the next day or two. Likely a Linux build first since that is where I am currently poking at code.
----------------
Circling back to the recent sync inquiry.
"We won't remove the API from your key, but we'll limit the quota to the quota for development. It's true that this will make the keys unsuitable for production use."
Source: https://groups.google.com/a/chromium.org/g/embedder-dev/c/NXm7GIKTNTE/m/Qxcew5lfCAAJ
Chromium *builders* pushing public builds with google_default_client_id and google_default_client_secret enabled in the build arguments are most likely to hit the issue. Sync and perhaps other API features will stop working for those builds if/when rate limit quotas for the specific keys are met.
Chromium *users* obtaining their own API keys and setting them through local system environment variables are likely to be okay as I doubt you will hit the dev rate limit quota via personal use.
If anyone here likes using sync, I strongly suggest obtaining your own #google-api-keys
--------------
Linux AVX proof-of-concept build:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4398.0-r846489-linu-deb-avx
Performance did take a slight but noticeable hit, though I only ran a subset of my usual optimizations to get a build done. Probably will have to redo some of the opts due to running Polly early during clang codegen now.
----------------
/depot_tools/chromium/src/build/config/compiler/BUILD.gn
Add the Polly cflags. I used a subset for Polly for testing.
"-mllvm", "-polly",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-enable-delicm=false",
"-mllvm", "-polly-ignore-aliasing",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-position=early",
# "-Rpass-analysis=polly",
Then I added stripmining to the Linux (else) section under the "thinlto_optimize_max" target settings.
cflags = [ "-mllvm", "-polly-vectorizer=stripmine", ]
There is no use wasting build timefor stripmine prevectorization on the $$$thinlto_optimize_default" targets since LTO codegen at O0 does not perform autovectorization.
----------------
On a related tangent regarding Linux builds, I would suggest changing the Oz cflag under "optimize" to at least Os, too. Oz disables autovectorization in favor of further squishing binary size. O2 would actually be even better IMO if using PGO. ;)
----------------
I need to see if the Polly inliner will help anything for performance on Linux. I know it largely pulls in lots of redundant libc++ functions, which probably is not going to do much IMHO.
Admittedly it has been awhile since I have dealt with tweaking Polly at the early position during clang codegen. I was kind of hoping those days were behind us for ThinLTO building on Linux. Oh well.
----------------
While I have yet to test it, for Windows you should be able to invoke Polly to run during *LTO codegen* via ldflags as we have been doing for awhile now, then add a ldflag for stripemine to "thinlto_optimize_max" target settings.
Add the Polly ldflags:
"-mllvm:-polly",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-ignore-aliasing",
"-mllvm:-polly-invariant-load-hoisting"
# "-mllvm:-pass-remarks-analysis=polly",
And under the Windows section of thinlto_optimize_max:
ldlags += [ "-mllvm:-polly-vectorizer=stripmine" ]
--------------
For consistency's sake I have moved -polly-vectorizer=stripmine back with the rest of the Polly cflags for building on Linux. The wasted cycles probably might add up to few minutes difference anyway.
Cheers!
https://chromium.woolyss.com/api/v3/?os=windows&bit=64&out=json&type=dev-avx2-nosync
[ "version": ] "89.0.4387.0"
https://chromium.woolyss.com/api/?os=windows&bit=64&out=json&type=dev-avx2-nosync
[ "version": ] "90.0.4400.0"
It seems that you have updated your API according to the new Chromium’s variants of RobRich (SSE2, SSE3, AVX2, etc.)
However, it looks like only the official API has been updated, not the old V3 version.
Note that I am not migrating to your last version’s API because it no longer contains the ["download":] variable that I use …
If it's possible to easily update V3 too : I'll take.
Otherwise, I would change my API usage during the 3rd coming Corona lockdown to be compatible with the latest API in it actual version.
Thank you @Jerry !
common_optimize_on_ldflags += [
"-mllvm:-polly-allow-nonaffine",
"-mllvm:-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm:-polly-ignore-aliasing",
"-mllvm:-polly-invariant-load-hoisting",
"-mllvm:-polly-opt-outer-coincidence=yes",
"-mllvm:-polly-vectorizer=stripmine",
# "-mllvm:-pass-remarks-analysis=polly",
]
LTO=O0 targets will ignore Polly. LTO=O2 (and higher) targets will use Polly.
After running various Polly configs against a Chromium component where I know it does optimize several loops successfully, I dropped a few of the more advanced and experimental options, plus returned to the default limit values for computeout, delicm ops, etc. with seemingly little-to-no change other than reducing build times. :)
Of the remaining options, allowing non-affine writes is still somewhat a question mark IMO. Polly has a more difficult time with schedule optimization of non-affine writes, thus why it is disabled by default, but Chromium is not exactly complex HPC-class code, either.... so, "whatever" I suppose? Polly does find more successful SCoPs with non-affine write support enabled, so I will leave it enabled for now pending further performance analysis of/when I feel like it.
Hi.Thank You Very Much For The New Windows Update. :)
Best Regards...
https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop_19.html
>Chrome 88.0.4324.96 (for Mac and Linux) and 88.0.4324.104 for windows
I meant that. I guess something Windows specific to note the tiny version incremention. And that changelog doesn't stop loading on my side lol.
https://chromium.googlesource.com/chromium/src/+log/88.0.4324.96..88.0.4324.104?pretty=fuller&n=10000
That narrows it down immensely. Yay!
Looks mostly just where various dependencies where branched for the stable release, then some minor changes in the build configuration files for whatever reasons. I suppose there could be a change in one or more of those dependencies as branched specifically to address a Windows issue, but that is further than I am digging into the commits. ;)
Talking of changelogs, at least Mozilla try to give a user friendly overview. Hell breaks lose if you try to view all changes on bugzilla still. Kind of annoying trying to narrow down a problem that introduces itself.
Very good, the Google services are now customized. But anyway, I have deactivated all the remaining ones. Passwords I have not saved, nor address entries, nor using SaveBrowsing (I use uBlock Origin and Malwarebytes). As default search engine I now use Fireball (fireball.de). It is like the former best search engine called "Altavista". Not as commercially overloaded as Google's. Thanks again!
Sadly, I am not kidding. It is getting as bad or worse than building Chromium with LTCG+PGO via Visual Studio years ago. o.0
I am still building for the foreseeable future, but being realistic, there will be an eventually where it comes down to increasingly invasive build times versus a complete build box replacement, and I am not really seeing the return-on-investment for me to spend another $2-3K (or more!) on hardware just to build a web browser.
--------------
More build breakage for Chromium on Windows, this time between Scalar Evolution and Polly. Yay? Polly is about to be turned down to just its default state and maybe stripmining, and then if it not working, maybe siimply moved back to clang codegen on all platform platform targets.
Another part of the issue could be this new split LTO approach, too. I might have to go back to building everything either completely with or completely without ThinLTO enabled. Hopefully more to follow....
--------------
FYI about LLVM branching. Trunk is now version 13.
https://lists.llvm.org/pipermail/llvm-dev/2021-January/148123.html
I am using the Stable build by Hibbiki on Windows 7 SP1 x64.
That said, Win7 is EoL even if Chromium or whatever browser does run on it, thus the platform is a potential security risk in and of itself.
--------------
Turned on assertions in LLVM on Windows. Build failure related to masked interleaving during loop vectorization. Another extra non-default LLVM optimization to drop. "Fun" stuff.
--------------
Chromium's bundled LLVM checkout seems considerably faster than my own local LLVM builds as of late. I know Chromium does multi-stage bootstrap builds of LLVM with ThinLTO+PGO in the mix, while I build my local checkouts using VS2019 with a few optimization tweaks. There did not used be a substantial enough performance difference for me to care. Hmmm.
--------------
I just "fixed" a large part of the build time performance regression(s) with my build box. I turned off Spectre and similar mitigations.
I had mitigations turned off previously, then enabled them like last year IIRC with no big issue to note, but apparently there has been some mitigation introduced in the meantime that was really tearing into system performance.
Opteron (piledriver) procs are not subject to Meltdown by default, and it is not like I use the system for much other than building software, so I am not concerned really about the other mitigations.
🔴 [Edited by Jerry: ^typo: "no big issue" ;) ...and your others comments are merged 😉
Also, I will update your entries and APIs as soon as possible!]
Ungoogled Chromium isn't even updated to use v88 yet, so Marmaduke cannot make a build until upstream is done.
Check out the progress for v88 here - https://github.com/Eloston/ungoogled-chromium/pull/1342
Of course, the OS remains the same (Windows 7 x64).
Google might start to enforce AppContainer (OS security measure) is supported. Support started in Windows 8. They could cut Win 7 off that way, in the name of 'security'. Just a guess/prediction.
>> ...Win7 is EoL ....
Actually is not exact - i.e.:
....
Extended support until October 12, 2021[104]
Extended Security Updates (ESU) support until October 14, 2024[8]
- so Win7 is alive.
cant wait for chromium 90 from Rob :)
https://github.com/RobRich999/Chromium_Clang/releases
Consider a Chromium dev build somewhere between alpha and beta software, though being more realistic in my own experience, it is more likely to have some potentially unstable or otherwise "not-quite-right" feature than introducing an outright glaring security issue. However, as with practically all development software and I as I often type here, *YMMV* as usual.
Consider a Chromium dev build somewhere between alpha and beta software, though being more realistic in my own experience, it is more likely to have some potentially unstable or otherwise "not-quite-right" feature than introducing an outright glaring security issue. However, as with practically all development software and I as I often type here, *YMMV* as usual.
---------------------
@Jerry Thanks for your efforts and support! :)
---------------------
I am working on Linux build updates right now. Appears I have Polly working properly again during LTO codegen. Clang calling LLD through a fuse did not appear to be the issue, so I am assuming perhaps a local LLVM checkout was built with the proper Polly flag being set.
Also I am turning on optimized LTO codegen for all build targets again to simplify my optimization efforts. I am taking a "whatever" stance as long as it actually generates working performant builds. On a related note, Linux builds now have a set LTO instruction import limit of 10.... after a little prodding by me. ;) That matches Windows builds and hopefully should improve Linux build times a little.
AVX2 building is going to be the lagging for awhile longer. I will try to get that system back online and building shortly. I have the parts here. Just have not really felt like tearing down the notebook. I suggest opting for AVX builds in the meantime.
---------------------
The notebook issue is part of the reason of my interest in Linux building, because I am currently using my Linux notebook. ;)
---------------------
FYI. I had to manually disable the GPU blocklist to enable hardware acceleration after installing my latest Linux AVX build on my system.
chrome://flags/#ignore-gpu-blocklist
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4403.0-r848298-linux64-deb-avx
---------------------
Current Polly ldflags during LTO codegen on Linux:
"-Wl,-mllvm,-polly",
"-Wl,-mllvm,-polly-vectorizer=stripmine",
# "-Wl,-mllvm,-pass-remarks-analysis=polly",
Yeah, that simple, which is typically how Polly is used typically anyway. I might add back invariant load hoisting and/or minimum loop profitability at 40 in the future, but for now Polly is working as expected and not causing intermittent build failures.
Likely I will use the same Polly config for upcoming Windows builds, too. Expecting to have those builds hopefully this weekend.
---------------------
Linux SSE3 build:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v90.0.4403.0-r848298-linux64-deb-sse3
RE: win7 support, will be interesting to see if they support until end of ms esu updates (2023 iirc). also i know companies planning to purchase premium support/custom patches from ms, i wonder if they can pay google too or can manage the code themselves somehow. interesting indeed.
Thanks a lot for the V90 (using mini-installer). A perfect work, without issues, best image quality with Intel graphics, all ok.
Are you planning on having your SSE3 builds for Windows shared here at the top of the page? And if so, will they be tagged as "SSE3"?
Cheers! :)
"SSE3" is the minimum system requirement for Chromium (and all Chromium-based) browsers. So, there will be no "SSE3" tag! ;) https://support.google.com/chrome/a/answer/7100626
Hi.
What do you think of BriskBard Web browser ?
https://www.briskbard.com/
https://www.briskbard.com/?lang=en&pageid=features
From the dev:
"BriskBard is a freeware web browser for Windows that also includes an email client, a media player, a news aggregator, an FTP client, a newsgroups reader, a contact manager, an IRC client and several web developer tools.
It uses multiple open source components (OpenSSL, Hunspell, CEF4Delphi, SQLite, Indy, etc.) and I'm the maintainer of one of those projects called CEF4Delphi at GitHub. BriskBard can be considered "mostly" open source because only a small fraction of its code base is close source.
BriskBard has a fully portable version and it can even be executed from a read-only device, although I would recommend to use a USB drive to store bookmarks, messages, settings, browser cache, etc.
The default rendering engine is Blink and it's available in English, French and Spanish."
This would help those still using Win32. They probably do not have the additional video codecs that are in Marmaduke's builds though.
Never heard before your comment. Thank you very much. I used it today all day. It is an interesting project with an up-to-date Chromium version. It is not fully open source but uses lots of open source projects. It has some limitations like : using only open source codecs, no extensions support, limited APIs support... The author says at https://www.briskbard.com/forum/viewtopic.php?t=269 : BriskBard uses the same way to monetize a free service that many other apps and blogs use : ads and affiliate marketing. Personally, this project is not enough mature for me.
@Ungoogleable:
Thank you for the suggestion. Of course, it is possible to add builds from other developers. I need to ask them before to add their releases.
@Marmaduke:
Do you plan to continue to support the Win32 version?
Hi.
Always welcome.
Thank you for your valuation.
Best regards... :)
Hi.
Thank you very much for the last update xxx.146
Regards ... :)
Chromium GPU on Intel HD Graphics: https://pastebin.com/Ysg7CNEE
Chromium GPU on GeForce: https://pastebin.com/7KQCTaiC
As I see on news that now google released fix for CVE-2021-21148: Heap buffer overflow in V8 on Chrome 88.0.4324.150 is it possible to have MacOS Ungoogled Chrome to be updated?
Thanks In Advance and Wishing you well on the other side of the screen
Hi.
Great. Thank you very much for the very quick update of Ungoogled xxx.150
Regards... :)
What about with HW acceleration disabled?
@Hibbiki
Thanks for win32 update against in-the-wild.
https://www.zdnet.com/article/google-chrome-syncing-features-can-be-abused-for-c-c-and-data-exfiltration/
Hi.
Thank you for last quick update xxx.150 .nosync is great. Regards... :)
https://chromium.googlesource.com/chromium/src/+/7d556c3e8a3eb00d7ea7cffbf6686ee57956b7bd
About LLVM in general, the new pass manager (NPM) is now the default PM, though Chromium is sticking with the old PM until any related breakages can be resolved.
I have submitted a question to Polly devs about NPM and NPM+ThinLTO support.
Thanks for sync heads up. Here are more details for technical minded:
https://isc.sans.edu/forums/diary/Abusing+Google+Chrome+extension+syncing+for+data+exfiltration+and+CC/27066/
Info about SYNC versions of Chromium:
Google will restrict access to private Chrome APIs from March 15, 2021. So Chromium users will probably no longer be able to synchronize their data with their Google account. Wait and see!
- Official post: https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
- Official discussion: https://groups.google.com/a/chromium.org/g/embedder-dev/c/NXm7GIKTNTE/m/ec6ArH9SBwAJ
Thanks in advance!
End-users with their own API keys for personal use on one or even a few local systems probably will be okay.
*Builders mass distributing publicly with API keys likely will not.*
"We won't remove the API from your key, but we'll limit the quota to the quota for development."
^Source: https://groups.google.com/a/chromium.org/g/embedder-dev/c/NXm7GIKTNTE/m/ec6ArH9SBwAJ
Thanks for the update for Ungoogled Chromium MacOS :)
Updating Chromium to 88.0.4324.150 didn't solve the problem with 100% CPU usage on Windows 7 x64 by main process.
Hi. Thank you for Android update.
But bromite have very selly patch now
-do not permit user-installed certificates
https://github.com/bromite/bromite/blob/master/build/patches/Do-not-permit-user-installed-certificates.patch
That's crazy :(...
Regards ...
Fork of Firefox: Iceraven.
With better privacy and access to about:config. Extensions support.
https://github.com/fork-maintainers/iceraven-browser/releases
Even if you don’t write it anymore, we agree that your still adding the following options to your Ungoogled Android 64 builds :
★ All Bromite patches applied,
★ HEVC and AV1,
★ "No Search" option (Replaced Google search engine with nosearch)
https://github.com/macchrome/droidchrome/releases
Ungoogled dev by wchen342
https://uc.droidware.info/
In beta stage . Support extension
https://uc.droidware.info/extension.html
https://www.lesnumeriques.com/
The top menu never shows. No extention in cause, I've tested, and it works ok with firefox.
I noticed that for a long while not only last version.
I'm using Marmaduke ungoogled
https://github.com/llvm/llvm-project/commit/222d380d2f57cc71bb613b5c01ecf17cd1f61fa2
I will have to further test for working Polly support during LLD/LTO codegen with NPM enabled, but either way, the commit should allow Polly to at least run early during Clang codegen with NPM enabled.
🔴 [Edited by Jerry - Feb 10, 2021: Please check your mailbox! ;)]
Hi.
My pleasure.
You're welcome.
Best regards.
Will reinstall the 150 version and give that a try.
My recommendation is to install the AVX build in the meantime.
Understood. Thank you very much for the reply.
P.S. I am grateful to everyone who maintains this project all these years.
Hello,
I note a consistency problem between the different versions of Chromium offered here: AVX, AVX2 and non-specific and those you offer on your Github space. The Chrlauncher script is not aimed at the correct directories. For example, there is no longer a script for the SSE2 version, and there is no script for the SSE3 version ...
Having said that, I can now use the AVX2 version with FMA.
It works great on my new PC, while the AVX version still has tabs crashes in the background.
Let me explain: I am doing research on the internet and for that I am going to open a tab, a second, a third, etc ... so as not to lose information that I have found and that I want to check elsewhere. When I go back to a previously opened tab, this tab seems empty! I always have to reduce the page to refresh it otherwise it is the blank, inert page ...
Thank you for your attention and for all this work.
I suppose the AVX tab crashing issue could be revision related, though I am not experiencing it here. It sounds like maybe a tab or resource management issue, which Chromium has introduced various features to address, many of which likely are now default since I am not seeing the about:flags for them anymore. It can take several revisions if there are corner-case issues and similar after landing new features as default.
On a positive note, hopefully I should have an AVX2 update later today or tomorrow. :) It still needs some work, but I am typing on the system used for AVX2 builds right now.
--------------------------
About building, Win32 building failed yet again. I might poke at it a little more, but I am unlikely to spend serious time debugging whatever is happening. I no real use for the build anyway, so it already very low on my Chromium priority list. I might eventually discontinue it.... again.
Thank you very much for your report. Note the SSE3 is the minimum system requirement since Chromium 89.
Therefore, SSE2 is no longer supported. Do you need a release with the SSE2 support?
https://docs.google.com/document/d/1QUzL4MGNqX4wiLvukUwBf6FdCL35kCDoEJTm2wMkahw
(https://archive.vn/ZxkfA)
About chrlauncher, it was a mistake in my APIv3. I updated it.
In the chrlauncher.ini file, write a "ChromiumType=xxxxxxx" value:
- dev-nosync or dev-robrich (SSE3)
- dev-avx-robrich (AVX)
- dev-avx2-robrich (AVX2)
@RobRich:
Ok about your 32-bit release. Good luck in your dev work!
I corrected your typo! ;)
----------------
AVX2 is building, so hopefully it will be ready to go public tomorrow.
----------------
I *might* have Win32 fixed. It appears Win32 has been failing on an AVX2 intrinsic during LTO codgen. I turned off AVX2 support in the affected libaom source configuration files. I have a build cooking to verify.
D:\depot_tools\chromium\src\third_party\libaom\source\config\win\ia32\config\aom_config.h
D:\depot_tools\chromium\src\third_party\libaom\source\config\win\ia32\config\aom_config.asm
I seriously doubt many (if any?) Win32 users are running Chromium on AVX2-compatible processors anyway, and if so, why?! Either way the libaom component still should work okay, just without AVX2 acceleration, so whatever IMO.
----------------
Win32 failed.... again. It still is trying to pull in AVX2 code. BTW, libaom aside, apparently libvpx pulls in similar intrinsics as well.
Quickly editing some config files buried in the source is one thing. Trying to track down and eliminate the litany of failing AVX2 instructions is something else.
I will think about some more potential workarounds and poke at the issue later.
Sort of bad news? Win32 still is falling locally even with Chromium's own LLVM checkout. Bizarre. I have a possible idea, though it should not really matter. I might try poking at it again tomorrow.
Congratulations on fixing your AVX2 building machine/environment and finding the right builds’ arguments.
As soon as AVX2 released, immediately installed !
Quick Benchmark,
( 90.0.4404.0-AVX ) VS ( 90.0.4417.0-AVX2 ):
Moteur : [4404 AVX] [4417 AVX2] ( ± diff % )
Octane : [34478 pts] [34750 pts] ( + 0,79 % )
Ares-6 : [28.23 ms] [27,44 ms] ( + 2,80 % )
Kraken : [1137.2 ms] [1130.2 ms] ( + 0,62 % )
Test with empty [user data] folder on first launch, to be equitable.
As versions are very close, gain probably come from your build arguments/codes optimizations than be revision related.
Congratulations,
Keep going !
----------------
An updated Win32 build is available now. Finally! I will push it to public in a few minutes.
It kept failing on practically any component pulling in AVX and AVX2 intrinsics. Those advanced SIMD code paths are relatively worthless for most Win32 use cases due to x86-32 processors lacking such support, but they are pulled in for correctness and coding simplicity anyway.
I was able to quit approaching the issue from a per-component standpoint. Instead I started looking at more build systemic possibilities.
I knew a recent Chromium change was to set -msse3 as a cflag across the whole build. Among one of the primary charges I made was to move -msse3 to common_optimize_on_cflags. That should not matter, as affected components typically set their own superseding SIMD cflags per each SIMD code path anyway, but I suppose there have been more bizarre corner cases in my years of building Chromium.
Next I also removed /Oi from common_optimize_on_cflags and changed /O2 to -Xclang -O2 and -Xclang -O3 depending upon the optimization paths. Again those should not matter from MSVC compatiblity standpoint in LLVM, but I wanted to cover multiple bases. BTW, ThinLTO codegen is O2 instead of O3 to limit binary size and memory overhead as usual for my Win32 builds.
So whatever or all of the above fixed it, and Win32 is building.... for now. ;)
I hope they don't stop official 32-bit support for some years. A 32-bit OS is still noticeably faster on older 64-bit machines (like mine! ram is adequate btw). And Chromium on older such setups doesn't feel like it is struggling compared to Firefox.
90.0.4417.0 (853576) • Saturday, 13 Feb 2021"
@RobRich
Nice work - it's fun - it'll be nice to see this version updated frequently with all codecs and others. ;)
what is the major difference between "Ungoogled Chromium" (win-x64) build provided here and the one on github (https://ungoogled-software.github.io/ungoogled-chromium-binaries/)? Is it only the "Safe Browsing" part or are there any other changes?
As far as I undestand, they're both compiled from Eloston's repo, however yours appear about a week earlier, than the ones by Ungoogled Software repo, which makes me wanna switch, given that both builds are equal.
Thanks!
Hello. These releases are different but use the same base. There are more services here: quick update following the latest stable version, "Safe Browsing", more codecs, widevine support... Thanks a lot to Marmaduke. 😌
https://chromium.woolyss.com/?all=1#comment-6279 (Can be long to load!)
Hello, previous version "v90.0.4396.0-r845617-win32-sse3" work very well and incredible fast on my old laptop Toshiba U300, but the new release "v90.0.4417.0-r853576-win32-sse3" don't work anymore. Why?
Thank's for your good job!
I check Win32 build for basic usage before them pushing to public, but I test them under a Win64 environment. I have no Win32 systems in active use.
Hi, the new Win32 release work on Win64 machine, but not on Win32 (sse3) computer. It looks like a 64-bit version and not a 32-bit version. Available for testing if needed...
Thank's
That build came off a different build box, so I probably should have looked closer. I am logged into my usual build box now. I will try rolling a new Win32 build.
Thanks!
no problem and thanks again for your work
------------------
After numerous build iterations of libvpx, I think my recent Win32 build failures are related to an older LLVM optimization I usually set for pre-register-allocation scheduling. I suppose something has changed in LLVM. Anyway. Now to see if I get a full build done.
--- org/third_party/libvpx/BUILD.gn 2019-07-29 21:37:01.000000000 +0100
+++ new/third_party/libvpx/BUILD.gn 2019-07-31 09:44:42.712302900 +0100
@@ -70,6 +70,7 @@
cflags = [
# libvpx heavily relies on implicit enum casting.
"-Wno-conversion",
+ "-mllvm", "-polly=false",
# libvpx does `if ((a == b))` in some places.
"-Wno-parentheses-equality",
It was a LLVM tweak for how I setup pre-register-allocation scheduling in the optimization pipeline. It was breaking AVX/2/512 instruction assignment on for the x86-32 target. It is no big loss, especially on register-limited 32-bit platforms, so "whatever" IMO. Took long enough to find in my local build configuration. o.0
----------------
Polly is fine for libvpx within reason. ;) The biggest issue usually is build time regression. Invariant load hoisting and stripmining in particular can cause huge build time regressions for some of the media components, and even more so if setting a very low loop instruction profitability threshold.
My current Polly config? During LTO codegen:
common_optimize_on_ldflags += [
"-mllvm:-polly",
# "-mllvm:-pass-remarks-analysis=polly",
]
I have found it is not worth the build time regressions to further tweak Polly in hopes of maybe finding (often far) less than a 1% performance difference.
----------------
On a side note, setting a cflag for Polly only works if using it during clang codegen. ;) You will need to set a ldflag if using Polly during LTO codegen, which is my recommendation for ThinLTO due to ideally wanting to run Polly right before the LLVM autovectorization passes.
I trying new 32 bit version, work well and it's fast. Thanks :)
Hi.
Big thanks for the ungoogled ... 182 update.
Regards. :)
Thanks for the ungoogled update :)
Is it possible to get a "sync" function enabled 182 version? For Mac
@RobRich
Hello.
It seems to me that my frozen tab problem happened with all 90. versions of chromium (89. not sure). A priori, the problem does not come from Windows 10 up to date ... and chromium either ...
So I check on the side of the ad-ons I installed, Adguard and Video downloader.
On the chromium.woolyss page, you recommend µblock origin.
So I installed µblock and deactivated Adguard (NB extra µBO is no longer available on the chrome webstore).
The problem has disappeared !!!
I used Adguard because it seemed to me to be more efficient than µblock. I don't remember if I made any particular settings in Adguard or is it already in the standard version of Adguard, in any case, there is a conflict with the new versions of chromium.
I remind you that the tabs that have been inactive for some time are frozen, we reactivate them by clicking on the Adguard shield ...
If you could check your end for confirmation.
Thank you.
I'm having a hard time finding some on the net while some distro are having stable 32 packages.
thanks anyway, great site.
Hi. Thank You for your latest update...182 nosync is great.
Regards... :)
Thanks
https://github.com/NeverDecaf/chromium-web-store
btw, this link will (eventually) load ALL comments:
https://chromium.woolyss.com/?all=1#comments
(tiny tiny request i may have asked before):
Could you compress your 7z archives please if it is no trouble? It helps when sending them with tiny upload limits. Thanks for your great service.
Hi.
Thank you for the Ungoogled update ...190
Best regards. :)
Why does the ungoogled-chromium build state the revision is 88.0.4324.182 which is the latest tag, but the release name and binaries are of 88.0.4324.190, I understand it is just a patch that bumps dependencies and replace refs with revision hashes. Just some minor nitpiks, thank you for your work.
Regards
index 91cc343..aaaabd0 100644
--- a/DEPS
+++ b/DEPS
@@ -49,7 +49,7 @@
vars = {
- "buildspec_platforms": "linux64, mac64, win, win64",
+ "buildspec_platforms": "win, win64",
# Variable that can be used to support multiple build scenarios, like having
# Chromium specific targets in a client project's GN file or sync dependencies
# conditionally etc.
diff --git a/chrome/VERSION b/chrome/VERSION
index 2fa1610..81097d9 100644
--- a/chrome/VERSION
+++ b/chrome/VERSION
@@ -1,4 +1,4 @@
MAJOR=88
MINOR=0
BUILD=4324
-PATCH=182
+PATCH=190
Thank you and very much appreciate all your hard work and support with your chromium builds.
I always look forward to your chromium releases.
Salute to you Sir
Kind regards,
Chris
The current latest stable version (well, up until yesterday it seems, but even the Omaha Proxy site gives different version numbers for different platforms right now) has this version info:
`88.0.4324.182 (Official Build) (64-bit) (cohort: Emergency)`
What is this "cohort: Emergency" about?
This is not normal, I think. It usually says "cohort: stable", as far as I know.
🔴 [Edited by Jerry - Feb 26, 2021: I do not see "cohort: Emergency" on the Omaha Proxy site]
Hi. Thank you for the update nosync ...190. Regards...
It included the mini_installer.exe in the archive file. I see marmaduke has already uploaded new archive and linked to it :)
Thank you for great browser and site!
Incorrect timezone in Chromium 90.0.4399.0 for 64-bit Windows.
I'm in Moscow, Russia. Should be GMT+03:00 instead of GMT-03:00
Have tested on the same PC three different Portable versions
More tools - Developer tools - Console
Date()
---1---
Correct GMT+03:00
chrlauncher-win64-stable-ungoogled
88.0.4324.190 (2202) Tuesday, 23 Feb 2021
---2---
Not Correct GMT-03:00
chrlauncher-win64-dev-codecs-sync
90.0.4399.0 (846566) Sunday, 24 Jan 2021
---3---
Correct GMT+03:00
chrlauncher-win64-dev-official
90.0.4428.0 (857020) Tuesday, 23 Feb 2021
🔴 [Edited by Jerry - Feb 26, 2021: I updated the timestamp of "chrlauncher-win64-dev-codecs-sync" based on its release's relative time: Jan 24, 2021, 5:37 PM UTC]
Thank you for all the Mac builds that you provide! I see that you have made an 'up-to-date' ungoogled version available. Unfortunately, every time I have tried an ungoogled version (including your latest version), it immediately crashes on my system. Oddly enough, all the other versions work fine. So would it be possible for you to update the 'sync' version to the latest stable build? I would be very appreciative!!
Can you consider building a version from the dev/canary branch instead of the latest version. I think dev/canary versions are more "stable" than regular snapshots and don't contain random annoying bugs here and there.
For example, 91.0.4431.0 (858332) doesn't save and apply features in the Labs menu.
From here https://omahaproxy.appspot.com/ the latest dev/canary versions are (for win64)
Dev - 90.0.4427.5 (856944)
Canary - 90.0.4430.1 (857950)
The proposal might be considered if I had the build box resources, but I do not at this time, nor am I inclined to spend thousands of dollars to replace my admittedly aging 32-core Opteron box with modern HPC-class hardware. ;)
There is a slight problem in ungoogled chromium browser. I have some bookmarks,search set to duckduckgo and using a custom
dns provider. Everything is there if I launch the browser with chrlauncher. However if I launch the browser from the bin folder
everything is missing. It is essentially acting like a separate profile. Is it supposed to behave like that ?
Thankfully energy costs are not too bad where I live, so I can look at some of the older less energy-efficient architectures that still offer lots of cores/threads. Admittedly, it is more like I am not going to spend serious money on unneeded hardware just to build a browser, though.
My 32-core Opteron build box is a holdover workstation, plus upgrades over the years, from back when I actually had a more viable use for such computing resources. FWIW, I can do most of my desired computing tasks on an older notebook or even an base model iPad these days.
Hi.
Thank you very much. For the very quick update 89 ... 72 . nosync
Regards...
Thank you, ever so much. for the up-to-date, sync version for Mac!!
@Marmaduke
To clarify Chromium timezone issue.
If Greenwich Mean Time is 08:00:00 (consequently Moscow Time is 11:00:00)
and I open site
https://time.gov
in Portable Chromium for 64-bit Windows
chrlauncher-win64-dev-codecs-sync
90.0.4399.0 (846566)
I see
Coordinated Universal Time (UTC) 08:00:00
Your Device's Clock (UTC-3) 05:00:00 A.M. <-- incorrect
If I open the same site on the same PC
in Portable Chromium for 64-bit Windows
chrlauncher-win64-stable-ungoogled
88.0.4324.190 (2202)
I see
Coordinated Universal Time (UTC) 08:00:00
Your Device's Clock (UTC+3) 11:00:00 A.M. <-- correct
It is hardly cutting-edge by a *wide* margin, but I should have well less than $300 in a second 32-core + 64GB system when done. I have my previous workstation drives, GPU, etc. for it collecting dust anyway. At least it should allow me to split up the build workloads. :)
I have another old Opteron server currently not in use as well. However I think it has a couple of ancient K10 procs, so no AVX but SSE3 would be okay. Hmmm.
Otherwise, next will to be looking into Win64 AVX2 building. I have been building it on a DTR-class notebook, which is doable for the immediate future but admittedly not ideal. I would prefer to build AVX2 more than once or twice per month, plus perhaps add a Linux AVX2 build, but the current AVX2 cycle likely will remain until I do something else on the more "modern" hardware front.
-----------------
Just stumbled across Opteron 6380 pulls for just $18 each at eBay. Even slightly better than the 6378 procs in my current build box. Ordered!
-----------------
FYI, particularly for Chromium builders tracking Chrome stable branch releases. Google intends to move Chrome to a 4-week "milestone" release cycle later this year, plus the addition of an 8-week "extended stable" release cycle. The current schedule is to land the change starting with Chrome v94.
Source: https://blog.chromium.org/2021/03/speeding-up-release-cycle.html
On a more positive note, I have been able to go ahead with migrating Linux building to LLVM's new pass manager.
Hi. Thank you so much for Ungoogled update 89....82 Windows.
Regards... :)
Google will restrict access to private Chrome APIs from March 15, 2021.
So You think to create build 'no-sync' after that date ?
@Jerry Might be worth removing that notice from site? I don't think anyone building sync variants here is NOT using official """secret""" Google API keys.
Hi. Thanks for your latest nosync ...82 update .
Regards... :)
Hi, I also had no idea you had a Github page https://github.com/Hibbiki/chromium-win64/releases with a NoSync version, been using Sync all this time because I wanted the convenience of your Installer for stable version .. Now I can have Stable with All Codecs, Installer and NoSync .. WOOT! :) Thank you.
thanks for Your reply and for new sync build.
Hi. Thank you so much for "ungoogled-chromium-89.0.4389.82-1_Win64" build release.
Kind regards,
Do you plan on releasing that small change soon, or wait for the next version I expect rather soon?
I prefer to keep the notice on the site because it affects all Chromium-based browsers using the Google API keys (yours too!). The Google API access will be limited by a quota. In short (and if I well understood 😉), Google wants: 1 developer = 1 Google API keys for 1 Google account. Let's see!
@V:
About the Chromium timezone issue. Thank you for your #comment-6577 That is strange!
@RobRich:
When I compare my machine with yours, it is like to compare Formula 1 with a "daddy car" 😄
@David:
Here, the full list of changes between the "72" and "82" minor versions.
https://chromium.googlesource.com/chromium/src/+log/89.0.4389.72..89.0.4389.82?n=1000
@Anon6590:
No issue like that for me. Tested at https://tools.woolyss.com/html5-audio-video-tester/
Like ever, thanks a lot for all developers and users. 😔 👍
It feels more like traveling on a fleet school buses here these days. Relatively slow going (frequency+ipc), but lots of seating (cores).
https://en.wikipedia.org/wiki/Instructions_per_cycle
From what I can see, Chromium has its own sync with its own account to share passwords etc. over the net (but no Google cloud) with others in that Chromium account - see settings and avatar icon for the profile. Another issue that worries me a bit is the non-complicated access of extensions: either from Google or Opera. Because most extensions are thirdparty, Google has no rights there.
By the way, I also unzipped an archive of a no-sync version and moved the unzipped folder to the folder "Programs" in Windows 10. The chrome.exe there uses the same user data including the extensions installed there - so also a method to get the extensions.
NPM implements the newer simple loop unswitching pass versus the older legacy loop unswitching pass. I had to disable the non-trivial loop unswitching enhancement used at -O3 to get NPM working for Windows building. I have had issues with the past when attempting to enable non-trivial loop unswitching with the legacy pass manager as well, plus it is not even invoked by default in the NPM at -02 and lower anyway, so whatever IMO.
https://www.deskmodder.de/blog/2020/01/10/chrome-portable-updater-x64-x86-canary-bis-stable/
https://groups.google.com/a/chromium.org/g/chromium-dev/c/MINcpzo3Zo4
As I noted while skimming recent posts, here is the Chromium Q4'20 security report for those interested:
https://groups.google.com/a/chromium.org/g/chromium-dev/c/qh2Zl_oC3Xo
A quand un Chromium qui éteint le Pc à la fin des téléchargements...?
Serait-il possible, à chaque mises à jour, ou chaque builds de retranscrire les modifications dans un fichier "log" en français.
Merci a toute l'équipe.
Pulling source and building should remain usable, but there likely will be no updated Chromium revisions available this weekend barring something truly serious, so do not be concerned if a git pull does not bring in fresh code until late Sunday or whenever maintenance concludes.
When will we see an updated linux build?
Chrome 89.0.4389.90 Stable Channel Update is out (March 12th) - Includes 5 security fixes
ici
https://chrome.google.com/webstore/detail/auto-shutdown/gkmonffckeeffppchajngpdakfppalfo
information
https://add0n.com/auto-shutdown.html
changelog in french -> ask author, auto logfile pas possible
Thank you Sir for your ungoogled build 89.0.4389.90 (843830).
Kind regards,
Hi . Thank you for the last Windows Ungoogled update ...
Regards. :)
Thanks as always Marmaduke.
Hi . Thank you for your last nosync Windows Update.
Regards... :)
I should be receiving my other build box early this week. I will need to do some hardware upgrades, install Linux, and hopefully get it churning out builds by maybe next weekend or so. Currently I do Linux builds under WSL2, so even if just shifting Linux builds to another system, that will cut down current builds on my Windows build box from five to three.
more codec's then actually needed but not all the patches actually needed
would like to see tag changed from "ungoogled" to "partial ungoogled"
you cannot be ungoogled with google inside
https://safebrowsing.google.com/
https://en.wikipedia.org/wiki/Google_Safe_Browsing
spyware crapware https://en.wikipedia.org/wiki/Google_Safe_Browsing#Privacy
came for ungoogled got googled by these wannabe ungoogled browsers, these ungoogled browsers would never be missed because they never existed in the first place
why not make two web browsers one for the far left wing democrats with there safe space google safe browsing inside
and ungoogled for normal human beings
https://github.com/Eloston/ungoogled-chromium
passing google off as ungoogle makes me wonder if you actually work for google to spread the google faith
https://listverse.com/2008/04/12/10-post-modern-religions/
https://www.thechurchofgoogle.org/
Church of Google
Also known as: Googlism
Founded by: Matt MacPherson
Info: Google.com, the world renowned search engine, has a following. These people believe that Google, being omniscient and omnipresent, is the closest Mankind will come to knowing and facing a god. Google can solve all their problems through knowledge, and knowledge is power. They even have nine proofs of Google’s godliness.
More and more users ask me for an "Installer" version of ungoogled-chromium. Is it possible for you to compile it?
@Anon6619:
1) Do you really understand that ungoogled-chromium is a fork of Chromium, a Google project?
A "Google project" does not mean it is the evil. You probably use Google stuff in different products without knowing it. It does not mean all communicate with Google. For example, the two secure software, Signal and Bitwarden, are based on Electron (using Chromium rendering engine). Please read the #project part.
Eloston and his team do a great job to remove Google stuff about the user privacy. However, like all software, it is possible there are vulnerabilities in ungoogled-chromium that could communicate with Google. The source code of Chromium is very big. In other words, when you use ungoogled-chromium, are you sure there is no communication with Google?
2) Marmaduke's builds have a different configuration than Eloston's builds.
Marmaduke's builds support more things than Eloston's builds. They support more codecs, widevine, safebrowsing to have a similar experience as Google Chrome with less communication to Google.
3) In the Marmaduke's builds, all ungoogled-chromium patches are applied except "Safe Browser". It means this patch is not applied. It does not mean Google Safe Browsing is active. Safe Browsing in ungoogled-chromium is an opt-in option (at chrome://settings/security). This option is disabled by default. So there is no communication with Google.
4) Finally, do not trust anybody!
I encourage you to check your network usage with tools like DevTools, Wireshark, SmartSniff, tcpdump, Fiddler, mitmproxy...
If you are a beginner, use the simple SmartSniff (https://www.nirsoft.net/utils/smsniff.html), on Windows.
Start SmartSniff → Then start ungoogled-chromium → In SmartSniff, check the communication with Google!
You will see Marmaduke's builds do not communicate with Google... like those of Eloston.
http://links.twibright.com/
Better use Lynx instead. Be sure to turn off cookies and caching. ;)
https://invisible-island.net/lynx/
————————
I actually like text browsers. Links was especially useful back in my college days. Students would overload the campus computer labs and library to "surf the web" on networked desktops. Meanwhile, I and few others would just pick from a myriad of typically unoccupied old "dumb" terminals connected to VMS running on a centralized DEC Alpha box. Login via a shell account, load links, and get to work on whatever projects.
🔴 [Edited by Jerry - Mar 15, 2021: Links added ;)]
So why don't I just use "ungoogled" no-Sinc? There is only one thing left: extensions from the Google store. But there I don't have a connection all the time, not for many days or weeks. But if I ever need something, I can access it quickly and easily. I also use Fireball as my default search engine. Google's Widevine is needed, but does nothing report to Google.
So I hope that Hibbiki's Sync version will continue to be built. Or do I have to worry? Thanks a lot.
Hi. Can you think to update android , in bromite they dropped the patch don't allow personal certificate .
Plz. Thank you.
Regards...
https://git.droidware.info/wchen342/ungoogled-chromium-android
Now I just intalled the "nosync" version of Hibikki from GitHub: mini_installer.nosync.exe. All without Google, but with the ability as before to easily and quickly install extensions - without cumbersome contortions of chromium-web-store - by simply going to the Chrome Web Store website. Hibbiki already has this built into its version. After all, the Extensions are not from Google but third party. So what else is not compliant? Is the crucial difference just that we can install Chromium properly this way? I think Hibikki has this all well in hand.
It is now very desirable to link in https://chromium.woolyss.com this stable installer version nosync by Hibikki. Thanks in advance.
Hi. Thank you very much for your android update :) ... Regards...
Obviously Google is trying to kill Sync on Chromium. The Ubuntu Snap updated on March 4 to proactively remove the Sync functionality (as far as I can tell). So even if I created my own developer API keys, I still wouldn't be able to log in. Here we are after the March 15 cutoff, and the Chromium 89 via Hibbiki's installer on Windows continues to let me log in. I'm trying to reconcile the difference, so that I can decide how to proceed.
Why is Hibbiki's version continuing to function (on the Windows side of things)? Has Google not yet followed through on their threat to put Chromium's API keys under a quota? Or is that edition using the Google Chrome ("private") API keys?
Also, why no Linux edition, downloadable here, with Sync? Like I said, the Snap package removed Sync, and the Ubuntu Apt PPA was just abandoned due to these revelations (and therefore outdated, and should no longer be linked from here). Thanks.
Thank you all for your effort and support! 😙
@Marmaduke:
1) More and more users ask me for an "Installer" version of ungoogled-chromium. Is it possible for you to compile it?
2) I know you prefer ungoogled-version. Can we remove your "sync" release because it is less used by users?
@Anon6626:
https://uc.droidware.info/ : I never used it personnally. However, it is up to date. 👍
Marmaduke already releases an ungoogled version. Also, there are other efficient open-source browsers : Bromite, Kiwi Browser (It supports all extensions from the Google Web Store).
@voidxor:
> Why is Hibbiki's version continuing to function?
Agree, it works. I tested today :
It works because Hibikki uses his own Google API keys and never shares them publicly. The problem is about the Google API keys used by the Linux teams. These teams shared their Google API Keys publicly (with the Google agreement). More and more users/developers used their Google API keys on non-Chrome browsers. Google put a quota on March 15, 2021.
Official discussion: https://groups.google.com/a/chromium.org/g/embedder-dev/c/NXm7GIKTNTE/m/ec6ArH9SBwAJ
> Why no Linux edition, downloadable here, with Sync?
There is no "sync" version because no developer compiles it. It's that simple!
Here, there are 3 kinds of users :
- The users who want a similar experience as Google Chrome. They will choose the Hibbiki releases.
- The users who want an ungoogled version. They will choose the Marmaduke (or Eloston) releases.
- The users who want to test and use the latest Chromium version. They will choose the RobRich, ARM or "official" releases.
If a serious developer compiles a "sync" version on Linux, I will share it on the site! 😉
Anyway, you can use your own #google-api-keys
Chromium for 64 and 32-bit Windows - Saturday, 13 March 2021
Chromium 89.0.4389.90 (Official Build, ungoogled-chromium)
Revision 62eb262cdaae9ef819aadd778193781455ec7a49-refs/branch-heads/4389@{#1534}
OS Windows
SDK 10.0.19041.0 (Visual Studio 2019 16.8.4)
clang/llvm (Default)
Standard build of Eloston's ungoogled-chromium. All patches applied apart from "Safe Browser"
No Sync - WebRTC - Widevine - All Codecs - Ungoogled
ungoogled-chromium-89.0.4389.90-1_windows.7z (64-bit)
https://github.com/macchrome/winchrome/releases/download/v89.0.4389.90-r843830-Win64/ungoogled-chromium-89.0.4389.90-1_Win64.7z
SHA1 10E3BE3F2D7D64EC26C173E04F5BAE5CF57C3F66
mini_installer.exe (64-bit)
https://github.com/macchrome/winchrome/releases/download/v89.0.4389.90-r843830-Win64/mini_installer.exe
SHA1 EA1147599135FCCCA513BDC1385BAA07150643B3
================
All sync and 32-bit Windows versions can be removed; they can be obtained form my github.
Thanks a lot for the mini-installer for Windows 64 on GitHub. I have been using it. All good except for one thing. OK, you don't like Google that much, neither do I and neither does Stefan Ries in Germany with his browser called "Iron".
One thing is missing though, adding extensions, directly without detours from the "chrome web store". As an interim solution I installed Iron, which uses the same "User Data". There I can directly add the extensions. These can then also be used at the same time in your Chromium.
Translated with www.DeepL.com/Translator (free version)
Thank you for the recent "sync" version for Mac!
As far as Hibbiki compiling with his own keys, he must have an unlimited quota then, right? I don't want my (minimal) sync activity to count against a developer's personal quota.
I had already read through that central discussion and many parallel ones while researching my sync issues. Google's treatment of the Linux package maintainers makes me sick.
As far as me being able to generate my own Google API keys, I read through those instructions, but am doubtful that it would work with an ungoogled Chromium. Surely the ungoogled/nosync editions are compiled *without* the APIs in question, right?
Technically in theory one might use Google's own API Keys, but that probably will not last long if abused, plus it could very well attract the wrong type of (legal?) attention due to being against program terms. I have seen talk about it, but it is definitely not something I would recommend doing. o.0
Someone else will have to answer the ungoogled aspect regarding sync, but otherwise, most relatively standard no-sync builds simply do not have API Keys set during the build process. Such no-sync builds can have sync enabled at run-time by users adding the needed API Keys as environment variables. Jerry has info here:
#google-api-keys
Is it possible for you to implement the browser extension patches to your android builds? As mentioned by another user the project was abandoned and it worked pretty well. I don't know if i can bother you with this but if you have time can you give it a look? The patches are already made so i guess it will be no trouble but maintaining it for next releases is another thing.
https://github.com/wchen342/chromium-android-extension
Ok. I re-display it just for you.
We (Marmarduke and me) have planned to remove his "sync" version on Windows (#comment-6631) because:
1. I think we have got enough Chromium releases for the Windows part. This one is redundant.
2. It is obsolete because Marmaduke prefers to focus his efforts on ungoogled versions ; and I think he is well busy with his all releases. ;)
3. Anyway, you can find it on its Github page.
4. "sync" can be broken, bugged (regression bug) because it is a Chromium's development version.
5. Few users use it.
6. Google announced it speeds up its release cycle (https://blog.chromium.org/2021/03/speeding-up-release-cycle.html). So there will be more work for developers to re-compile the "stable" Chromium version.
@RobRich:
Thank you for your neat explanation.
@Marmaduke:
Thank you very much. I am currently adding your "Installer" version of your ungoogled version. When ready, you will update it yourself! ;)
I do not plan to remove all "sync" releases. I would like to keep only "sync" releases of STABLE Chromium. In the developpment versions, the syncronization can be easily broken or bugged (regression bug).
----- 📢📢📢📢📢 --------
REQUEST FOR ALL:
Finally, this main page is very long. If we decide to keep all of these Chromium releases, here, I will split this page as a blog space.
Project:
- On this main page, there will be all Chromium releases and the comments' system.
- On other pages, there will be the other content, like a standard blog.
What do you think about that ?
Thanks for providing mini_installer for ungoogled, much appreciated!
Thank you very much. Please, make sure the "ungoogled" word is present in the URL (like on your zip archive) when you upload your release on the site. 😇
@David:
Thank you for you answer. I am ok for a blog because it is easy for me to maintain it. I do not want to manage a forum. As you know, I like the "all-in-one" style page but today it is too long! ;)
> split this page
Reasonable idea 👍
Hi. Blog is a great idea ... Best regards.
Thank you for the explanation in regards to the initial removal of Marmadukes Dev sync version.
As appreciative as I am, please do not feel you need to repost it because of me. If Marmadukes sync build is no longer being used by many individuals, and you and Marmaduke agree with the removal, I'll support that decision 100%. :) I've always used the sync version, but I'm beginning to think perhaps I should also stop using it. There just aren't enough frequent Dev sync updates anymore to risk it's continued use on my system. It sits for too many months without an update which isn't good in terms of security. So perhaps it's removal would be in the best interest of all users here? Unless you and Marmaduke wish to keep it posted with more actively maintained updates (wonderful news for me of course! haha!) with this split page blog idea. But I don't see Marmaduke having the extra time to dedicate to a more timely updated Dev sync build. So I think I'm going to try in the next little while to either move to RobRich's Dev SSE3 build (My computer is too old and very sadly doesn't support his AVX builds. My CPU supports only as high as SSE 4.1), or I'll go to Hibbiki's Stable sync build.
Thanks for the info!
Cheers! :)
~Dustyn~
Thank you for the latest android update
Thanks. Greetings.
Yes, I had read Jerry's section about the Google API keys on this page, as well as the official API keys page. Before following all of the instructions, I was hoping somebody here could confirm if that would actually work on the stable ungoogled binaries for Linux. And no, I don't plan to use Google's private keys.
@Marmaduke or @Eloston
Can either of you confirm my previous question about whether the Sync API is even compiled into the stable ungoogled binaries for Linux...such that keys are the only thing missing?
@Dustyn
For what it's worth, I've been using Hibbiki's stable sync build for two or three years and experienced no problems! Rock solid, thank you Hibbiki!
Thanks for letting me know your experience with Hibbiki's stable version. Good to know! :)
For now, I transitioned to RobRich's 91.0.4437.0 (859720) | https://github.com/macchrome/chromium/releases/tag/v90.0.4399.0-r846566-Win64
It's the only one out of his Dev releases that I can use that works on computers without the AVX intruction set.
Hibbiki's stable version I will have to try out at some point if RobRich ever decides to stop updating his SSE4 version. :)
Cheers!
Sincerely,
Dustyn
-----------------------
WHOOPS! Wrong link posted! That was for the Dev version by Marmaduke that I just switched away from. I'm now using the Dev SSE3 version by RobRich:
https://github.com/RobRich999/Chromium_Clang/releases/tag/v91.0.4454.0-r864947-win64-sse3
🔴 [Edited by Jerry - Mar 24, 2021: Merged comments]
C:\Users\USERNAME\AppData\Local\Chromium\Application\89.0.4389.90\Installer
Trying to play the films there makes the site give an "Error code 83" .. Apparently its something to do with Widevine
The #widevine (Please read this part!) support is ready but you must to install this plugin yourself.
To help you, I exceptionally share a ZIP archive of this plugin (Thanks Marmaduke!) 😉
1. Download this archive: https://chromium.woolyss.com/f/widevine.zip (24.7 MB)
2. Unzip it and get the corresponding version to your system.
3. Go to your main Chromium repository and find the "WidevineCdm" folder.
4. Drag-and-drop the unzipped content to your Chromium's "WidevineCdm" folder.
5. Launch Chromium browser.
6. Go to the top of this website and check if the Widevine tag is displayed ^^ (Screenshot: https://i.imgur.com/F1jXvgR.png)
@Dustyn:
I merged your comments. Also, like I said in my #comment-6641, I removed the Marmaduke's DEV version with "sync" ;)
@Albers:
Yes. They are similar. The "Installer" version is an 7-zip file with a launcher. You can unzip it to compare.
I mentioned it because previously I have always used Hibbiki's Stable Installer with Sync on this website, and Disney+ was never a problem (without any manual installation of Widevine needed)
Whereas recently I found out Hibbiki has a Github page with a NoSync version of the same build, so started using it and found the Widevine issue
So I naturally thought there is something amiss with the NoSync version if the Sync version previously worked fine with Disney+
🔴 [Edited by Jerry - Mar 25, 2021: Agree. Thanks you for your report. I updated his release on the #windows-32-bit part]
Not sure if it will become a routine build, but I have rolled a Linux 64-bit AVX2 build for experimentation. As usual Debian, Mint, Ubuntu, or similar with libc 2.35.1 or later required.
https://github.com/RobRich999/Chromium_Misc/releases/tag/v91.0.4460.0-r866979-linux64-deb-avx2
anyone know where to get a free premade chromium release with Tor built in?
https://www.torproject.org/
kinda prefer chromium over firefox for ease of use and performance
i wanna use for regular surfing and dark web surfing without the bugs in firefox
Thank you very much for the latest installer. Now I can watch videos from German Mediatheks with H.265 - Great thing!
cheers for the new update, seems you built it faster than Eloston and co.
Hi. Thanks for the last update ...114
Best regards... :)
Thank you Sir for the latest 89.0.4389.114 (843830) release.
Kind regards... :)
Marmaduke, help!
Hi. Thank you very much for your Android update xxx.105. Regards... :)
Chromium 91.0.4467.0 (Official Build) (64-bit)
fc33847bc50c0cee9b891c558794a67ecbe56c72-refs/heads/master@{#869045}
OS Windows
- Dev build
- SDK 10.0.19041.0 (Visual Studio 2019 16.9.0)
- clang-12.0.0/llvm - default
- ThinLTO
- WebRTC
- PGO
Sync - Widevine
Chrome-bin-sync.7z (chrlauncher formatted)
https://github.com/macchrome/chromium/releases/download/v91.0.4467.0-r869045-Win64/Chrome-bin-sync.7z
SHA1 46299BBE90087D6A0BA882721A59D930D9FD388E
mini_installer.exe (64-bit)
https://github.com/macchrome/chromium/releases/download/v91.0.4467.0-r869045-Win64/mini_installer.exe
SHA1 836FBCF93AA6F0063EC1A03573C72D89D3CFB602
I was trying out your "ungoogled-chromium_89.0.4389.114_1.vaapi_linux.tar.xz" release and note that in chrome://settings/security - under Advanced - "use secure DNS" option is missing. Is this by design?
Kind regards,
The Chromium tree is closed currently for infrastructure maintenance through sometime tonight, so I am looking at hopefully having updated Windows and Linux builds later this week.
Why are the beta builds (colored blue) for Windows 64bit from Marmaduke (mcchrome/winchrome) not listed on the site anymore? Even if M. doesn't create a new version every day but only after 2 months, these builds are always of best quality and mostly already stable and already a big step into the future of Chromium. With Widevine and all codecs incl. H.265/HEVC these builds are a real alternative to Google Chrome and are quite presentable. They merit without any doubt the greatest attention.
> two 32-core systems for building
Nice!
There is this search engine called Google...
https://www.bleepingcomputer.com/news/security/google-chrome-for-linux-is-getting-dns-over-https-but-theres-a-catch/
#win64-dev-avx2-robrich
:)
32-core? waoooow! It is a monster. 😄
@wth:
https://chromium.woolyss.com/?all=1#comment-6641 (This link will display all comments)
Tell me what do you think about our decision.
Thanks for latest android update. Much appreciated.
Thank you for the "clarity" with the web link. I am learning something new everyday.
Kind regards,
Well, the comment of 19 Mar 2021, 04:04 is outdated, because Marmaduke has just released again a sync version Chromium 91.0.4467.0. Why didn't he put out an "ungoogled" one there? What's going on there? Chaotic, confusing, unrealistic. But I think Marmaduke already knows what he is doing.
I have been tweaking some optimizations to hopefully improve build times. I do not think there should be any significant performance regressions, but as usual, please let me know if spotting something worthwhile.
1. on the top right there is a button. With click we get a list of recently closed tabs.
2. with right mouse click on the site we can create a QR code from the URL of the currently open site. This will appear immediately at the top. We can photograph it with the smartphone or tablet with a QR code scanning app from the monitor screen. Depending on the settings, the browser then opens there with the site. Nice, so we effectively have sync without Google.
Marmaduke Windows 64 Portable
I use these extentions-
https://chrome.google.com/webstore/detail/webrtc-leak-prevent/eiadekoaikejlgdbkbdfeijglgfdalml
https://chrome.google.com/webstore/detail/webrtc-network-limiter/npeicpdbkakmehahjeeohfdhnlpdklia
https://chromium.googlesource.com/chromium/src/+/043d32542213b601bf5852f6cd5950c949f411fa
This is a really big deal for those who are interested in modern graphic formats. So it's especially sad that Rob had already built the avx version the day before. :(
Collateral Damage for instance, DRM error for no apparent reason. I have Widevine and YouTube Movies and Netflix work great. I'm so confused.
https://tubitv.com/movies/578203/collateral-damage?start=true
In the Windows Firewall (or the firewall of the security program) search for the app "chrome.exe" on the disk and allow it to be private and public.
No! Compile it yourself, then you might appreciate what is involved and how impudent your request is.
mini_installer_avx.exe (ungoogled chromium 89.0.4389.114 - 64-bit AVX)
https://github.com/macchrome/winchrome/releases/download/v89.0.4389.114-r843830-Win64/mini_installer_avx.exe
SHA1 8ABB3E759ACFE9734E0019639A4A85C723B67F70
Adding it to firewall rules doesn't stop Windows 10 from uninstalling chromium.
How you determine I don't appreciate your work :)
I don't see my request to be "impudent", because you already have polly versions.
Thank you for your considiration and reply.
PGO in 91... look there:
https://github.com/macchrome/chromium/releases/
IIRC WebRTC is enabled on all Chromium builds from v68 onwards: the option to disable WebRTC was removed from the Chromium source code. uBlock+ScriptSafe combo was recommended here to minimize leak impact.
Thanks for the new AVX2 ungoogled build.
Also, of note, I did not get SSE3 builds updated. Got sidetracked with other stuff. I probably will just roll new builds there, too.
---------------
Looking a little better IMO:
Forget built time optimizations. I have slammed performance optimizations due greater build box capacity. Now let's hope I working builds in a few hours.
Moving forward I really need to figure out something about AVX2 building. I am not spending serious cash on it, especially since this project is a just a limited hobby for me, so I am thinking perhaps looking for an older Haswell-class server or similar. Maybe later this month. No promises, but I can still build AVX2 on my Windows notebook in the meantime. It just might not be updated as often as the other builds.
Also I'm curious if there are any noticeable performance differences between avx2 and avx/sse3 builds? With the ivy bridge, I can't test it myself. :)
I do not notice a significant enough difference on my Intel Kaby Lake notebook to really matter outside a few benchmark numbers, but again, that too can vary depending upon certain browser tasks, such as intensive rendering and multimedia. For example, I suppose cloud gaming services *might* slightly benefit, but I have not tested any since I am not really into gaming.
Some of the third-party components and similar have SIMD code paths, but many of the core parts of Chromium contain lots of already decently optimized scalar code, so we are leaning heavily on autovectorization to generate hopefully even more performant SIMD code. Again, another YMMV situation.
https://en.wikipedia.org/wiki/Automatic_vectorization
LLVM currently does loop and slp autovectorization, plus Polly can help with loop optimization and "strip mining" prevectorization.
https://llvm.org/docs/Vectorizers.html
VPlan-based vectorization is one of the future goals of LLVM. It has been awhile since I have looked seriously into implementing VPlan locally, but AFAIK, it is still quite a "work in progress" feature.
https://llvm.org/docs/Proposals/VectorizationPlan.html
----------------
I have some other ideas about possibl future performance optimizations, but they are getting into dealing with application profiling locally. Not my idea of fun, especially when Chromium provides regularly updated PGO profiles anyway. For example, there is context-sensitive PGO, but that is adding yet more code instrumentation, profiling, and compilation. It ideally should run the same profiling workload as Chromium uses, too.
Another one is post link optimizations, but both the current options are limited to ELF binaries, meaning I would be targeting only Linux builds here. BOLT is available and can be pulled into LLVM as a tool, though I suspect it will absolutely crawl on my hardware, assuming it does not run into memory limits on 64GB systems. Propeller is another option, but it is in development and currently not synced to a recent LLVM checkout, thus it probably will run into issues building Chromium.
----------------
AOCC is a potentially interesting possibility on on the Linux side, too. Basically it is AMD's version of LLVM with additional proprietary optimizations. AOCC lags LLVM checkouts, but I suppose it might build Chromium with a few tweaks. The biggest downside IMO is several of those proprietary optimizations target LTO, and AFAIK AMD is using FullLTO, which is orders of magnitude slower than ThinLTO for building, especially on my hardware.
----------------
Missing symbol error(s) in Vulkan Validation Layers with my optimizations. I have seen it before, but I did not like my previous workaround. MacOS apparently skips the component altogether due to whatever build issues, so let's try dropping it on Linux and Windows as well. Fingers crossed. Probably will be something else next. Fun stuff. ;)
I am posting this reply with Mozilla Nightly 89.0a1. WebRender is enabled. It is an older AMD Jaguar quad-core notebook running Kubuntu 21.04 (beta), 5.12rc6 kernel, Mesa 21.1.0-devel, amdgpu/radeonsi, *Wayland*, etc.
https://en.wikipedia.org/wiki/Jaguar_(microarchitecture)
I doubt it will win (any?!) benchmarks against my latest Chromium Linux build, but admittedly, it still is performing okay for casual browsing IMO.
-----------
Deformed basic blocks during compilation. o.0 Yeah, IIRC, that is a new one with Chromium. Backing off some optimizations. Annoying, but the changes are not likely to matter much, if at all anyway. Starting again.
🔴 [Edited by Jerry - Apr 8, 2021: Merged comments ;)]
With respect to compiling Chromium Windows AVX/AVX2 builds (on platforms without native AVX/AVX2 support): Linux cross-compile.
https://chromium.googlesource.com/chromium/src/+/master/docs/win_cross.md
eg. build/config/win/BUILD.gn SSE3 AVX ("-msse3") ===>> ("-mavx"), etc.
No need to invest in new hardware.
For subsequent remounts of the Windows (SDK) toolchain, use:
build/ciopfs -o use_ino third_party/depot_tools/win_toolchain/vs_files.ciopfs third_party/depot_tools/win_toolchain/vs_files
To manually switch (or instantiate) Windows toolchain:
...
export DEPOT_TOOLS_WIN_TOOLCHAIN_BASE_URL=/volumes/disk2/stable/chromium
export GYP_MSVS_HASH_20d5f2553f=4a89d2a89c (example)
python build/vs_toolchain.py update --force
=====================
[Recent cross-compilation failure caused by: v8_enable_system_instrumentation = true (v8/BUILD.gn)
https://chromium-review.googlesource.com/c/v8/v8/+/2773792
https://bugs.chromium.org/p/chromium/issues/detail?id=1196278
Problem appears to have been fixed]
Until recently I actually was doing Linux builds under WSL2 on my 32-core Windows box. I have migrated Linux builds onto a 32-core modified Kubuntu box. Both are Opteron Piledriver systems, so AVX native.
I can probably source or toss together an older Haswell or similar AVX2 system for like $200 to $300 to meet my needs. Feeling like dealing with it is something else, though. ;) Took me like 3-4 weeks to get the Linux build box upgraded and deployed. o.0
My comment is for ThinLTO/Polly Ungoogled not regular Chromium, because Marmaduke didn't produce it, like he normally do.
Thank you for your suggestion.
-------------------
Windows 64-bit AVX and SSE3 builds updated. Linux 64-bit AVX and SSE3 builds updated. Think I have settled on an comprehensive optimization setup for awhile. Performance is looking good in my limited testing.
Windows 32-bit SSE3 is building, so maybe later today or tomorrow.
I will try to get to a Windows 64-bit AVX2 update over the weekend or perhaps early next week.
-------------------
Sure enough, JPEG XL is now available. :)
https://en.wikipedia.org/wiki/JPEG_XL
Enable JPEG XL via flags.
chrome://flags/#enable-jxl
Top center image should load in JPEG XL format. Will say otherwise if not.
https://sneyers.info/jxl/
Thank you for the new 64-bit SSE3 build! Highly appreciated!
Cheers! 🍺
--------------------
Quick FYI. My latest Linux builds seemed okay during testing on my Kubuntu 20.10 build box, though I am now getting an audio playback error on my Kubuntu 21.04 beta notebook. Probably is OS related, but anyway, a head's up just in case.
Hi. Thank You for your update 9 April modified all-codecs win64.
Regards ... :)
Chromium v91.0.4467.0-r869045-Win64 runs very well.
Thank you! :)
@RobRich
New version AVX & SSE3 are very fast!
I'm waiting for the 32 bit version :-)
Thanks !!!
Just pushed a Windows 32-bit SSE3 update, too.
Hi, new 32-bit SSE3 for Windows (91.0.4472) is very good !
Thank you :)
🔴 [Edited by Jerry - Apr 11, 2021: Cleaned comments ;)]
After following the instructions listed here #comment-6656 widevine continues to be the problem.
----------------
@aMLU I have not used his Linux build, but AFAIK, you should be able to unarchive and run it. A directory under your user account should be okay. As for the error, is that showing up as "InitializeSandbox()...." issues in chrome://gpu/? GPU sandboxing and Linux is a known issue, so you can generally ignore it if hardware acceleration otherwise is working okay.
It seems that Google introduced manifest V3 in Chrome 80 Canary near november 2019. But yet versions’ 91 or 92 of our favorite builders here are still (thankfully) compatible with manifest V2.
@Hibbiki, @Marmaduke & @RobRich particulary :
Will you continue to compile Chromium when manifest V3 (back door for Google’ ads & spyware) will be the only supported manifest?
Chromium and Edge use actually manifestVersion='1.0' - showing in the head of xml-File xxx.manifest
There is no exact date, but no earlier than 2022.
@RobRich
These days it is nearly impossible to go surf without uBlock.
https://developer.chrome.com/docs/extensions/mv3/intro/
@Daigo Hmmm. ;p
That said, yeah I understand, but I largely just use a limited set of personally curated websites for my routine daily interests and tasks. If a site misbehaves, then I probably will have little reason to continue trying to use it.
Hello,
Lots of crashes with the latest AVX2 92.0.4475.0 version. I can't understand why, too many tabs open, too many apps used ...
Chromium closes and when I restart it by trying to restore the previous configuration, chromium closes immediately ...
I turn around...
I am not sure it is optimization related, so I probably will roll another build in the next day or so to see if it is a revision issue before taking a deeper look.
I would suggest the AVX build in the meantime.
AVX is good and stable.
Thanks Daigo for the date. I also confirm that using a browser without uBlock₀, Pi-hole or a custom host file is just plain dangerous these days!
Chrome 89.0.4389.128 Stable Channel Update (with 2 security fixes)
(You all are probably already aware of that, but just in case ...)
Windows 4-core Core i5: Win64 AVX2
Windows 32-core Opteron: Win64 AVX + Win64 SSE3 + Win32 SSE3
Kubuntu 32-core Opteron: Linux64 AVX + Linux64 SSE3
I have another Opteron 8-core (IIRC) server that could eventually be deployed, too. It has been collecting dust for quite a long time. I might look into building ChromiumOS, Firefox, or something else lower priority (to my interests) on it.
From a techincal perspective, I am not hacking out features you may or may not like. Resolve the issue on your end. AFAIK, there is an extension to block it, or chose a different release if preferred.
Otherwise I can simply quit pushing public releases altogether if that would be preferable. Just let me know.
That is not gonna happen. Ever since Widevine L3 been publicly broken, Google has tighten out security around it and pretty much all resources using Widevine now require VMP on Windows and Mac to be enabled.
The process for VMP certification is to simply generate signature (for Chromium that would be both chrome.exe and chrome.dll) signed with appropriate Widevine-accepted certificate (note this is different from signing binary on Windows and if both are done, VMP must be performed after).
Hi. Thank you for your update ...128
Regards... :)
> I'm not forced into whatever Google wants
This is funny. Chromium is not developed by some other altruists. What Google wants always appears in Chromium. Google develops Chromium then builds his Chrome on top of Chromium with the addition of logos, codecs and telemetry.
@RobRich
Please don't react to some clowns. 😉
Now that may be a new record....
--------------------
About FLOC:
"Google also said that users can opt-out of the FLoC trial by disabling third-party cookies through Google Chrome."
Source: https://blog.malwarebytes.com/cybercrime/privacy/2021/04/millions-of-chrome-users-quietly-added-to-googles-floc-pilot/
I suggest doing that anyway. You can manually add certain sites needing third-party cookie support for whatever reasons if needed.
chrome://settings/cookies
----------------
Now back to usual business.....
An updated Win64 AVX2 build will be pushed in a few minutes. It seems to be stable in my basic testing.
Various other updates are built and pending release. Probably later today as I have other things to do this morning.
I was suspicious at Google for going for a "4 week release" cycle. They already mucked up the industry with "agile rapid release" schedules. This may be another way to make it a little more difficult for downstream companies to keep the Browser up to date, let alone people like yourself who do it for practically nothing but hopefully GOOD COMMENTS!
BTW, usually I do not even mind negative comments if they are actually constructive in some way. ;) Admittedly I have pushed plenty of borked, mislabeled, unstable, etc. builds over the years.
Hi. Two update in two days , thank you very much... Regards :)
Test by EFF I'm Floced from Korben Site ?
https://amifloced.org/?source=korben.info
Thanks for your releases. In 92.0.4475.0 I am seeing a lot of crashes with highlighting a word + right click to use the Search for highlighted word. When it crashes and I try to restore the session it just crashes again.
I mean Google is trying to get rid of 3rd party cookies, which for privacy advocates is a very good thing, and FLoC is a better less targetted technology because it puts you into a group or demographic of people interested in the same things, instead of targetting you as an individual.
At the moment if you dont allow third party cookies in chromes advanced settings, FLoC is also disabled.
Also, the FLoC ID tag is based on your last weeks worth of browsing history .. Use chromes settings to flush out your browsing history every time you close it, and something like Bleachbit every day (for those who really want to be sure all chrome browsing history is wiped) = FLoC has nothing to work with == Nothing to get in a flap about.
I think EFF is making too much of a fuss about this when they should be at least acknowledging googles efforts to get rid of the worst bad practices on the net and coming up with a solution to pay everyones bills which is a lot less of a concern than third party cookies were.
Anyone that worried ought to be throwing their mobile phones in the bin, that's where the real unstoppable tracking is going on right now, anyone with an Android or IOS phone (I think thats just about everyone these days), who sets location tracking to off .. You haven't stopped anything, see this report recently https://www.scss.tcd.ie/doug.leith/apple_google.pdf
This version does not show that "Should Chromium Helper allow incoming data?" pop-up, so I think the last 114 version was off a little. Anyway, resolved it seems.
FloC:
Apparently, the sync versions of Chromium will use FloC. In the "User Data" folder we find the "floc" folder, which contains the Floc fingerprint among other files. The Ungoogled no-sync version of Marmaduke also contains this "floc" folder. But it is empty and does not contain the "manifest.fingerprint" file - so no FloC works. Microsoft Edge Chromium also does not use FloC - it is also "ungoogled". That means "ungoogled" is really un-floc.
Hi. Thank you very much for v90 Ungoogled update. Regards... :)
Hi. Thank You very much for v92 64bit 15 April no AVX modified all-codecs. Best Regards... :)
Thank you for your ungoogled 90.0.4430.72 build release. Appreciate it.
I think overall moving toward federated learning and algorithmic ways to insure privacy is a good step forward whether FLoC works out or not.
I wanted to thank you all for the good work you are putting into this project :)
I have a few questions that I would love for you to answer :)
Regarding macOS builds, is there an option to add an M1/Universal builds? or a notarized build?
Also, what is the difference between @Marmaduke's builds and @Eloston's builds?
Are all of the developers (@Marmaduke, @Eloston, @RobRich, @Hibbiki) collaborating with each other or does each work independently?
Thanks! :)
(i) M1/Universal builds: https://github.com/macchrome/macstable/releases/tag/v90.0.4430.72-r857950-macOS
(ii) I don't remove safe browsing. Safe browsing is disabled by (code) policies: view chrome://safe-browsing/
(iii) Independently, we target different niches.
Thanks for answering my questions! :)
This is the build I have installed but it doesn't show up like it was built as a Universal build (If I click on "Get Info" in the Finder menu it shows up as "Application (Intel)" instead of "Application (Universal)") - It's working alright, but I assume it's under Rosetta instead of natively.
It's also not notarized, so I need to right click (or alt/option click) and open from there to avoid the "This app cannot be checked for malware" error.
Is it possible to change it in future buillds?
And what is the difference between this build (that is labeled "sync" and the older "ungoogled" build)?
Regarding Safe Browsing, I like that it is this way :) It keeps it an option - which I prefer, because while I prefer to avoid google connections and maintain my privacy, for what I understand, Safe Browsing just checks for updates for the safe browsing blocklist - there aren't any IDs or other personal information being submitted so I prefer to keep it active.
Also, if I want to support you - is there a Patreon or other form in which I can do that? :)
Thanks! :)
FLoC apparently puts your ID in Chromium \ User Data \ FLoC \
If I were to do the following, would it cause problems for Chromium (or would it also cause problems for Installing future updates to Chromium) ? :
1. Delete the FLoC folder
2. Make a file called FLoC.txt
3. Rename the file FLoC.txt to just FLoC (no dot extension)
The aim being to make a file which will stop FLoC working, a folder called FLoC can not be made by anything when there is a file called FLoC already exists, so anything put in there by Chromium just dies / goes to null (whatever you want to call it).
Thank'sss
I was doing this trick to stop MS Edge from downloading Flash (before I figured out the proper command line switch for it).
It should work fine for FLoC also.
I just emptied the Floc folder and made it read-only.
No file appeared in it ever since, haha.
I admit this was on Linux, but I guess it should work on Windows as well?
No, I tried this on Windows 64 with a sync version, with the write protection. The browser has the higher rights and fills the folder with the files later again, including the fingerprint for the Cohort.
If nobody will do that for me (and anyone else hoping for such a build), how would I go about learning how to do it myself?
Thank you for all the hard work done so far, and for any and all help/guidance you guys are willing to provide! :)
https://imgur.com/a/RwvA9Dc
Delete contents under the FloC directory. In my case:
C:\Users\RobRich\AppData\Local\Chromium\User Data\Floc
Set permissions for the directory to deny write access for your Windows user account.
Note trying to update the FLoC component in Chromium fails now.
- Anon6761’s trick (Delete Floc folder and create une Floc file without extension)
or
- RobRich’s trick ( deny write access for your Windows user account)
https://imgur.com/a/RwvA9Dc
Boths works…
Google's FLoC is defused by default. Websites will be able to use the FLoC API (only if already present), but will be unable to get a result from it -- uBO causes the API to always fail as if there was no FLoC data available.
If your Chromium-based browser supports the FLoC API, this is the result you should get with uBO when testing with EFF's "Am I FLoCed?" (assuming you did not disable uBO's "uBlock filters -- Privacy" list):
Additionally, uBO causes all websites to opt-out of being part of FLoC calculation by injecting the appropriate response header.
You can opt-in to FLoC by creating the appropriate exception filter.
Hi. Great , thank you very much for your quick update ...95. No–sync is very good as usal ... Regards. :)
"Google Chrome 90.0.4430.85 patches still another zero-day security flaw" followed by a further explanation.
The never-ending story of people exploiting something .... sigh
and causing the Devs here extra work!
Thanks Marmaduke, RobRich, Hibiki, etc. for all of your efforts!
Had to uninstall, recover my user folder from a backup, reinstall previous, then put my user folder back to get the browser to open and to get my tabs back.
Which previous version do you mean? Based on the fact that you had to recover user directory my guess is 89.
I can also not help you if you don't provide basic information such as OS and version you used (sync vs no-sync, x86 vs amd64).
I personally always use my builds (amd64 sync variant) so if there was something horribly wrong I'd expect to either see it myself or get more reports. All my builds are done from common source tree and differ only on args used.
I've been using your builds for quite some time and never have had an issue.
I always use the x64 installer so, sync. I reverted back to v90.0.4430.72 from the current 90.0.4430.85
Win 10 Pro
Here's exactly what happened;
Closed Chromium
Installed 90.0.4430.85
Opened and a tab on twitter.com crashed Aw Snap
Refreshed Aw Snap > Closed tab > Opened new tab > tried again > Aw Snap
Closed browser reopened, same thing.
Reopened and disabled all extensions.
Closed browser reopened, crash to desktop gone. And, that's it.
Uninstalled, installed 90.0.4430.72, went to my previous day's backup, pulled out my profile and copied it back and was able to reopen with my tabs back.
Reinstalled 90.0.4430.85. It worked but then after a few hours sitting idle, it crashed to desktop and wouldn't open again.
Uninstalled 90.0.4430.85, this time keeping my profile information, reinstalled 90.0.4430.72 and it's working fine since. Reluctant to try 90.0.4430.85 again.
It's not a big deal.
Hi. Thank you so much for your Android update. Regards... :)
Does your 92.0.4488.0 (875969) • Friday, 23 Apr 2021 version contain the security fixes Google has released in their latest 90.0.4430.85 version?
Some say there is a certain amount of danger in using the 90.0.4430.72 versions without the patch for the security holes that have been reported.
What is your view on the danger involved? Negligable, or not?
Hi. If possible, can you add in your api the nosync build of Hibbiki. Is for updating Chromium with chrlauncher by henry++. Thank you. Best regards... :)
Thank you very much for the update 92.0.4489.0 for Windows 64 !!!
I am the maintainer of ChromiumForWindows, a Chromium installer and auto updater for Windows, based on the builds of this website. (Link: https://github.com/iklevente/ChromiumForWindows)
I would love to add your Chromium builds to the project, as I did with Hibbiki's and Marmaduke's builds, but there is a slight problem:
My updater searches for the latest verson of a choosen build (eg.: Hibbiki's --> https://github.com/Hibbiki/chromium-win64/releases/latest) and will store the redirected url in a string and work with that in the update process. (eg.: https://github.com/Hibbiki/chromium-win64/releases/latest redirects to: https://github.com/Hibbiki/chromium-win64/releases/tag/v90.0.4430.85-r857950 right now)
The problem is that yours (https://github.com/RobRich999/Chromium_Clang/releases/latest) either redirects to a linux build, or to a win32 build, or to non AVX, etc...
Please, if it is possible, could you draft all your builds (win64, debian, avx, sse3...) in one release? If yes, please keep the logical order of the installer.exe (currently mini_installer.exe) filename, because it could break the updater just like it did with @Marmaduke 's build 2 releases ago. Not just the updater broke, but me mentally after fixing it. 😅
I don't know if other updaters are dependent on your current release method, but I understand if you can not change it for some reason. I could find a way to fix it, just like I did with @Marmaduke 's build, --> regexing the latest version number. But unfortunately it makes the updater not as lightweight and fast as it could be.
🔴 [Edited by Jerry - Apr 26, 2021: Please, check your email box 😉]
I didn't notice that this site has an API that I could use. 😅
Anyways, thank you so much for all the people who made this possible. For the countless efforts of Jerry, Hibbiki, Marmaduke, RobRich and the others for building Chromium binaries and maintaining this website over the years.
Hi. Thank you very much for the quick update 90...93 . Regards.
Welcome to the world of Jerry's API 4!
In my case, I utilize this API for personal use here: https://www.murielfrenchcouture.fr/chromium/
This allows me to update Chromium very quickly for 3 diffenrets OS : my Windows, my Debian and my phone (Android)
This API is very useful for handling all versions of Chromium available here in only one HTTP request!
Thanks Jerry !
Thanks Hibbiki, Marmaduke, RobRich !
The newest beta build by Marmaduke for Windows 64 is V 92.0.4489.0, to download there:
https://github.com/macchrome/chromium/releases
Yes, it's a great API! It could save me dozens of time and gives me the possibility to add the official chome-dev build and maybe and Arm build in the future.
Your site is quite impressive too! Great way of utilizing the API!
The number of security updates done in the past several versions is just amazing!
Hopefully, `Marmaduke can find the time to issue the sync version for Mac.
Many thanks in advance.
-----------------
@iklevente I appreciate your efforts and feedback, but admittedly, that is not possibly right now.
Currently my build are spread across *three* systems, so the different builds are not always the same versions when released. ;)
Trying to keep all the build versions synced would mean constantly branching multiple repositories, actually managing build times on the various systems, etc.
I understand it, any yes you got a point! I got API access from Jerry, which literally solves everything. 😁
Thank you again for your compiling efforts and I'm looking forward to implement your build into the updater asap.
Best regards,
Levente
Sometimes, when closing a tab with video playback, it crashes and falls back to software compositing.
I have to poke at Linux builds, too, as my latest ones had a linking error. Fun.
Going to bed in the meantime. ;)
Thanks for the ungoogled 93 version.
Could you roll out a "sync" version as well? I prefer that version as it is much easier to add extensions.
Thanks!
Hopefully is is just a revision-related issue. I have not changed any optimization options since the last round of builds.
I will try to take a look later today and roll new builds for release.
Hi. Thanks for your update Ungoogled... Best regards. :)
Appears there was at least one LTO breaker in LLVM updates yesterday. Pulling an updated LLVM checkout to see if the Windows build(s) complete. If not, I might have to roll my local LLVM checkout back to whatever revision Chromium is using.
Hi. Thank you for 92.0.4491.0 (876546) • Tuesday, 27 Apr 2021 No AVX 64bit. Regards... :)
Hey. Can you update Android there are new interesting features in bromite. Regards... :)
Hopefully my currently cooking Windows builds will complete successfully in awhile.
One suggestion is to link to the GitHub repos for the builders. So, if I click the label for Hibbiki or Marmaduke, the little popup box would also have a link to their repo. (It's easy to find this already, but it would be a nice convenience to have it here too.)
The reason I mention it is I wanted a slightly older version, so I needed to go to their repos to see what the options were.
Ok, sorry. My apology. Best regards.
Sure enough, I ended up rolling my LLVM checkout back to be in sync with Chromium's own bundled revision.
Hi. Thanks for new 64 bit no avx April 30. Work very well for me. Regards... :)
Thank you for your 90.0.4430.93 (857950) build release.
With kind regards :)
Hi. Thank you very much for your Android update. Regards... :)
Thanks so much for the snappy SSE3 builds!
Working great! :)
Cheers!
My latest builds are showing a slight to moderate uptick in a few benchmarks. My various optimizations and tweaks aside, hopefully it is project wide.
Compiling Chromium on a good PC takes up to 6 hours with your processor stuck at 100% all this time. This is a significant amount of time and power consumption.
So before claiming this or that, try a single compilation yourself and you will understand how rude it is to ask him such things.
On XDA, for example, ETA requests can lead to ban.
You're lucky that Jerry is cool because If I would be the admin of this site, requests like this would be direct blacklisted IP.
Ungrateful that you are!
Any help for this? I try to build chromium for android for personal use with my APIs. I get this error on Chromium build:
Ubuntu 20.04
$ python --version
Python 2.7.18
but I see python3.8 is called..
$ autoninja -C out/Default chrome_public_apk
ninja: Entering directory `out/Default'
[41778/62775] ACTION //v8:run_gen-regexp-special-case(//build/toolchain/linux:clang_x86_v8_arm)
FAILED: clang_x86_v8_arm/gen/v8/src/regexp/special-case.cc
python3 ../../v8/tools/run.py ./clang_x86_v8_arm/gen-regexp-special-case clang_x86_v8_arm/gen/v8/src/regexp/special-case.cc
Traceback (most recent call last):
File "../../v8/tools/run.py", line 14, in <module>
result = subprocess.call(sys.argv[1:])
File "/usr/lib/python3.8/subprocess.py", line 340, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: './clang_x86_v8_arm/gen-regexp-special-case'
[41782/62775] CXX obj/v8/v8_compiler/wasm-compiler.o
ninja: build stopped: subcommand failed.
#browser-crash
Going a step further, you can delete the files under the application (not User Data!) directory, then run the mini_installer.exe again.
For example:
C:\Users\RobRich\AppData\Local\Chromium\Application
----------------
@Haris K. You can have python 2 and 3 installed simultaneously.
sudo apt install python3
You might need to setup alternatives, too.
sudo update-alternatives --list python
Odds are it is going to say something like the follow.
update-alternatives: error: no alternatives for python
Create alternatives:
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 2
Now run:
sudo update-alternatives --list python
Which should show:
/usr/bin/python2
/usr/bin/python3
Set python2 as the primary preference. This will show a text menu to manually select python2:
sudo update-alternatives --config python
Now the "python" command is defaulted systemwide to python2, while python3 should be available if invoked directly with the "python3" command like in your pasted script. Hopefully the build will proceed now.
It appears you do have python3 installed from the script feedback.
The underlying problem is a missing V8 file for the ARM whatever architecture.
I do not deal the ARM cross-build stuff, so others here might have better answers. In the meantime, since it likely will be asked anyway, what are your build arguments?
I have python 2 and python 3 installed and I already have set the 2 alternatives
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2 1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 2
and chose python2 in
$ sudo update-alternatives --config python
So I find it strange why python3 is called. There is no python configuration in .bashrc that could affect python choice.
Since it is a test build, the only arguments I put are:
target_os = "android"
target_cpu = "arm64" #My phone is xperia 5 ii
google_api_key = "my api key"
google_default_client_id = "no"
google_default_client_secret = "no"
What I would like to have at the end is chromium that syncs and has adblock
You have android set in your .gclient file, correct? If so and the build still fails, try adding the following build argument for a temporary workaround:
v8_enable_i18n_support = false
That is not ideal, but it at least it might get you a working build for now.
During
build/install-build-deps-android.sh
there was a message I never read, so I thought the updates were successfully installed, but they were not..
The message was:
The repository 'http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu focal Release' does not have a Release file.
Thanks a lot for replies and sorry my misunderstanding..
(Maybe my posts should be deleted because they unnecessarily flood the topic)
Leave the posts IMO. We can learn from them. Plus you should see some of my rambling posts of the years. lol
I have 2 questions:
1) sync still does not work although I made a developer account, enabled sync API and put the API key in gn, I get message the "This account already exists on your phone"
Here are my arguments:
target_os = "android"
android_channel="stable"
google_api_key = "My API key"
google_default_client_id = "no"
google_default_client_secret = "no"
symbol_level = 0
blink_symbol_level=0
enable_nacl=false
proprietary_codecs = true
ffmpeg_branding="Chrome"
2) I have unstable version 92, how could I build stable 90?