venetium 150.0.7871.226 (v1.3.1.3, experimental)

venetium 150.0.7871.226 (v1.3.1.3, experimental)

another build for the lumias (qualcomm adreno). with v1.3.1.2 the gpu stays on, and testing it on the 735 found two
more problems. this build fixes both. big thanks to aimul for testing these builds on a lumia 735 and sending the
reports, the logs and the switch tests: that is how both of these were found and fixed. i don't have a lumia, so
please keep testing and reporting.

• both builds: scrolling no longer draws old text over the page. when the gpu drew the page, the lumia driver
  mixed old and new parts of it (a tab switch cleaned it up until the next scroll). on the lumias the page is now
  drawn by the cpu and the gpu still puts it on the screen, the same as the --disable-gpu-rasterization switch that
  fixed it in the test, so you don't need that switch anymore.
• both builds: webgl pages that use depth textures draw again. the webgl field sample showed only its blue
  background: these gpus can't read depth textures, but angle still offered them. now pages use their fallback.
• everything from v1.3.1.2 is still in.
• nothing changed on the surface rt / surface 2.

start clean before you test, old flags and switches can hide the fix:

• remove --disable-gpu-rasterization, --disable-gpu and any other switch you added to your shortcut
• open chrome://flags, click Reset all and relaunch
• if you switched to the microsoft basic display driver, switch back to the adreno driver. with the basic driver
  everything runs in software on purpose, that's normal

which file: windows rt 8.1 / 8.0 = win8-8.1-arm32-thumb2 (exe or zip), windows 10 = ...-arm32.exe /
...-win-arm32.zip. close venetium before you run the installer.

what to test

1. chrome://gpu: compositing should say "Hardware accelerated" and "GPU process crash count" should be 0.
   rasterization says "Unavailable" in red: that is the fix (the cpu draws the page), not a problem. click
   Download Report to File and keep the file.
2. scroll long pages up and down, fast and slow: google search, news sites, wikipedia. is any old text or picture left
   on the page?
3. webgl: https://webglsamples.org/field should show the field, not only blue. https://get.webgl.org should show a
   spinning cube. webgl 2 doesn't work on these gpus, that's expected.
4. canvas: a page with a canvas animation or a browser game. do old frames stay on the screen?
5. youtube at 360p, 480p and 720p: is it smooth? right click the video > stats for nerds shows the dropped frames.
6. use it normally for a while, then check chrome://gpu again: is the crash count still 0 and the gpu still on?

report in the issues: your device, windows version, which file, the chrome://gpu report file, and what worked
and what didn't. if something is missing on a page, the report file has the details. if it crashed or the gpu turned
off, add the .dmp files from %LOCALAPPDATA%\Venetium\User Data\Crashpad\reports.

sha256 of every file is in SHA256SUMS.txt.

venetium 150.0.7871.226 (v1.3.1.2, experimental)

another test build for the lumias (qualcomm adreno). thanks to the 735 report by Aimul: v1.3.1.1 fixed the crash at start and
the gpu got further, but 10-20 seconds later the gpu process still shut down, three times, and then everything ran in
software. this build fixes that. i don't have a lumia, so please test it and report back.

• both builds: skia stops using its tessellation path renderer at feature level 9_3. its stroke shader needs 467
  instructions and these gpus allow 256 (error X5615 in chrome://gpu), so lines and shapes are now drawn the same
  way as on the surface rt.
• both builds: angle no longer forces a shader that is too big through to the gpu. that is what shut the gpu
  process down. now only that one drawing fails and the gpu stays on, also on webgl pages with big shaders.
• everything from v1.3.1.1 is still in.
• nothing changed on the surface rt / surface 2.

start clean before you test, old flags and switches can hide the fix:

• remove --disable-gpu and any other switch you added to your shortcut
• open chrome://flags, click Reset all and relaunch
• if you switched to the microsoft basic display driver, switch back to the adreno driver. with the basic driver
  everything runs in software on purpose, that's normal

which file: windows rt 8.1 / 8.0 = win8-8.1-arm32-thumb2 (exe or zip), windows 10 = ...-arm32.exe /
...-win-arm32.zip. close venetium before you run the installer.

what to test

1. chrome://gpu: compositing and rasterization should say "Hardware accelerated" and "GPU process crash count"
   should be 0. click Download Report to File and keep the file.
2. browse for a few minutes, with pages that have lines and shapes too: maps, charts, svg icons, loading spinners. look
   for missing lines or outlines, missing text, black or garbled parts.
3. youtube at 360p, 480p and 720p: is it smooth? right click the video > stats for nerds shows the dropped frames.
4. webgl: https://get.webgl.org should show a spinning cube. webgl 2 doesn't work on these gpus, that's expected.
5. use it normally for a while, then check chrome://gpu again: is the crash count still 0 and the gpu still on?

report in the issues: your device, windows version, which file, the chrome://gpu report file, and what worked
and what didn't. if something is missing on a page, the report file has the details. if it crashed or the gpu turned
off, add the .dmp files from %LOCALAPPDATA%\Venetium\User Data\Crashpad\reports.

sha256 of every file is in SHA256SUMS.txt.

venetium 150.0.7871.226 (v1.3.1.1, experimental)

a test build for the lumias (qualcomm adreno). on the lumia 735 the gpu process crashed right after start, and after
three crashes everything ran in software. this build fixes what made it crash. i don't have a lumia, so please test
it and report back.

• both builds: no gpu timer queries on the lumia gpus. the old qualcomm driver crashed on them on the first frame.
• both builds: angle's d3d11 at feature level 9_3 stops asking the gpu for things it can't do. text drawing
  failed there before ("Error allocating BlendState" in chrome://gpu).
• both builds: gpu rasterization on every lumia gpu. the gpu ids come from the lumia driver files in
  WOA-Project/Lumia-Drivers.
• nothing changed on the surface rt / surface 2.

start clean before you test, old flags and switches can hide the fix:

• remove --disable-gpu and any other switch you added to your shortcut
• open chrome://flags, click Reset all and relaunch
• or use a fresh profile: close venetium and rename %LOCALAPPDATA%\Venetium\User Data to User Data.old (your old
  profile stays in there)

which file: windows rt 8.1 / 8.0 = win8-8.1-arm32-thumb2 (exe or zip), windows 10 = ...-arm32.exe /
...-win-arm32.zip. close venetium before you run the installer.

what to test

1. chrome://gpu: compositing and rasterization should say "Hardware accelerated" and "GPU process crash count"
   should be 0. click Download Report to File and keep the file.
2. browse for a few minutes: text heavy pages, scrolling, images. look for missing text or black / garbled parts.
3. youtube at 360p, 480p and 720p: is it smooth? right click the video > stats for nerds shows the dropped frames.
4. webgl: https://get.webgl.org should show a spinning cube. webgl 2 doesn't work on these gpus, that's expected.
5. use it normally for a while, then check chrome://gpu again: did the gpu stay on?

report in the issues: your device, windows version, which file, the chrome://gpu report file, and what worked
and what didn't. if it crashed or the gpu turned off, add the .dmp files from
%LOCALAPPDATA%\Venetium\User Data\Crashpad\reports.

sha256 of every file is in SHA256SUMS.txt.

venetium 150.0.7871.226 (v1.3.1, experimental)

venetium 150.0.7871.226 (v1.3.1, experimental)

a test build for the lumia 2520, lumia 735 and other qualcomm devices. i don't have them, so please test it and
report back.

• thumb2 build: fixed the crash at start on qualcomm cpus. it used one instruction that the tegra runs and
  qualcomm chips refuse.
• both builds: fixes for the gpu on adreno (angle's d3d11 at feature level 9_3), from the
  venetium-w10m fork. thanks ilya vysotsky.
• both builds: sites get h.264 at every resolution now, so more video plays on the hardware decoder. if a video
  stops playing, start venetium with --disable-features=VenetiumArm32CodecSteering and tell me the site.

which file: windows rt 8.1 / 8.0 = the win8-8.1-arm32-thumb2 exe or zip, windows 10 15035 = ...-arm32.exe /
...-win-arm32.zip. on the surface, v1.3 is still the tested one.

report in the issues: your device, windows version, which file, what happened, and a screenshot of chrome://gpu.
if it crashed, add the .dmp files from %LOCALAPPDATA%\Venetium\User Data\Crashpad\reports.

sha256 of every file is in SHA256SUMS.txt.

venetium 150.0.7871.226 (v1.3)

venetium 150.0.7871.226 (v1.3)

two arm32 builds this time, same chromium 150:

• arm32: the normal one, for windows 10 build 15035 on the surface rt / surface 2. now pgo + thinlto.
• arm32-thumb2 (new, experimental): for the original windows rt 8.0 / 8.1. v8 is ported to thumb-2, so it
  runs there with the jit on.

faster

• pgo + thinlto build, the profile recorded on my surface 2. speedometer went from about 1.20 to 1.79 on the
  tegra 4, about 50% faster.

windows rt 8.x (the thumb2 build)

• windows rt 8.x only runs thumb-2 code, and v8 makes arm (a32) code, so no chromium could run there with its jit. i
  ported v8's arm32 jit to thumb-2: all tiers work (sparkplug, maglev, turbofan, liftoff, wasm).
• the windows 8 api gaps are handled in the browser itself, no extra dll.
• tested on my surface rt (tegra 3) with windows rt 8.1: pages, scrolling, video, sandbox on, speedometer 1.18.
• windows rt 8.0: not tested on a device yet (i checked it against 8.0's system dlls). 8.0 has no d3d shader compiler,
  so it draws in software there.
• like any unsigned desktop app, it needs a jailbroken rt (unsigned apps allowed).
• the v8 port has its own repo: https://github.com/hamed7ir/v8-thumb2-rt

fixed

• Math.pow gave 0 for very small results (like Math.pow(10, -310)), in both builds. the cause was the pow of
  microsoft's arm32 c runtime; v8 now uses its own.

which file

• arm32 (...-arm32.exe / ...-win-arm32.zip): windows 10 15035. the fast one there.
• arm32-thumb2 (...-win8-8.1-arm32-thumb2.exe / .zip): windows rt 8.0 / 8.1. on rt 8.1 i tested
  the zip; the installer should work there too but i haven't tried it yet. it should also run on 15035 (not tested).
• installer: per-user, no admin, shortcuts and uninstall. both installers use the same folder and profile, so pick
  one. portable: unzip and run venetium.exe (keep the venetium_filters folder).

sha256 of every file is in SHA256SUMS.txt. the files are not signed, so smartscreen may warn: "more info" ->
"run anyway". ad-block lists: easylist / easyprivacy (https://easylist.to/), gplv3 / cc by-sa 3.0.

venetium 150.0.7871.226 (v1.2)

chromium 150 for old windows arm tablets: surface rt (tegra 3) and surface 2 (tegra 4) on windows 10 build 15035.
same chromium as v1.0, now an official (release) build with a round of speed work and every fix since v1.0.
just replace v1.0 with it.

faster

on my surface 2 (tegra 4), speedometer is 10-15% higher.

• built-in ad and tracker blocker, on by default (easylist + easyprivacy). allow a site from the "ads blocked"
  icon in the address bar, or turn it off in chrome://settings/content/ads.
• tuned for 2 gb tablets: memory pressure, javascript heap, caches, and memory saver sleeps idle tabs sooner.
• video: youtube is steered to hardware h.264 at 720p+; software decoding uses up to 4 cores.
• smaller wins: faster string handling on arm32, faster image/video decoding, no swap-chain rebuilds on the
  tegra gpu, page preconnect hints work again, less background work.

fixed / new since v1.0

• webcam works (winrt camera, about 30 fps) and the microphone works.
• extensions install from the web store again.
• no more tab crashes on recaptcha, telegram web, css animations and some extensions.
• gpu rasterization on the surface rt (tegra 3) too.
• lumia / adreno: the d3d11 path is really in the build now; please try it without --disable-gpu and report back.
• sandbox fully on (status row in chrome://version), plus smaller fixes.

which file

• installer (Venetium-Setup-...-arm32.exe): per-user, no admin, shortcuts and uninstall.
• portable (venetium-...-win-arm32.zip): unzip and run venetium.exe (keep the venetium_filters folder).

sha256 of every file is in SHA256SUMS.txt. the files are not signed, so smartscreen may warn: "more info" ->
"run anyway". ad-block lists: easylist / easyprivacy (https://easylist.to/), gplv3 / cc by-sa 3.0.

venetium 150.0.7871.226

venetium is chromium 150 for old windows arm tablets. this build runs on the surface rt (tegra 3) and surface 2
(tegra 4) on windows 10 build 15035, and there is an x86 build for old 32-bit windows too.

what works

• hardware h.264 video decode on the gpu over d3d9, so 720p plays smooth on youtube and aparat
• gpu acceleration through angle on d3d9 (these chips have no d3d11)
• the chrome renderer sandbox is on
• h.264 / aac and the other codecs are built in
• vp9 / av1 play in software (the tegra has no hardware for them)

what not works

• Extensions from chrome store, will be fixed next release. But unpacked extension installs.
  Tested on v3 extension and it works well.
• lumia devices should run it with - - disable-gpu for now
  You tell me

which file do i want

pick your cpu:

• arm32 - surface rt / surface 2 and other windows rt / arm32 tablets
• x86 - old 32-bit x86 windows

pick your style:

• installer (Venetium-Setup-...-<cpu>.exe) - installs per-user, no admin needed, makes shortcuts and an
  uninstall entry. it has a "check requirements" button that tells you if your windows is missing anything venetium
  uses (like media foundation, for video) - it only warns, it never blocks the install.
• portable (venetium-...-win-<cpu>.zip) - just unzip it anywhere and run venetium.exe.

the sha256 of every file is in SHA256SUMS.txt.

notes

• the files are not signed, so windows smartscreen may warn - that is normal, click "more info" -> "run anyway".
• windows 8 / 8.1 (rt) support, running jitless, is what i want to add next.