Command line switches

Chromium switches have to be appended to a vivaldi shortcut after vivaldi.exe (or your OS format).
Most of them depend on your OS and are just for debugging, (web)developing or modding the browser, while some others are meant to be used only on chrome – they need specific google API/keys to work – so not meant for chromium based browser, like our Vivaldi.
Some command lines can be enabled also by a flag, and it’s what I prefer whenever is possible as the option is directly “stored” by the browser and not loaded via a shortcut.

Now, some useful switch that can be used in Vivaldi.

Enabling some features:

  • –save-page-as-mhtml (provided also as a flag)
  • –show-cert-link (provided also as a flag) Chromium now does it by default
  • –enable-devtools-experiments Style devtool. Should work on chromium64 or newer.
  • –enable-logging –v=3 –vmodule=metrics=2: Windows ONLY. Place a log in vivaldi profile and a debug window at vivaldi startup. v=0/v=1/v=2 will do a huge txt log.
  • –enable-logging –v=3: Same. Vmodule parameter seems to be necessary on win only.
  •  –process-per-site – This will lower RAM usage but it could increase hangs if you use a lot of tabs from the same site – as it will use a process for each site.
  • –args –ignore-certificate-errors – Not meant to be used on your main vivaldi shortcut as it’ll *always* allow any not secure content from *anywhere* – it’s a risky workaround for few sites/platforms, but it will lower your security alot and could expose users/certificates on machine to data theft and to be hacked. You had be warned. Use it wisely. And only for sites you really, really trust.

Bonus tip: Chromium don’t allow anymore to bypass invalid certificates (“proceed anyway” as firefox does).
If you can’t access to your platform/internal site due an old certificate you can try to type
danger
badidea
thisisunsafe
to access the site.
Keep in mind this should be used only on trustworthy sites or you probably get a malicious certificate placed in your operating system (which is bad) and will probably compromise the machine security.

 

Allow inspecting UI and extensions

  • –remote-debugging-port=9222 – Then you can inspect tabs/extension/UI at http://localhost:9222/ page.
  • –debug-packed-apps (provided also as a flag)
  • –silent-debugger-extension-api

 

Cache specific

  • –disk-cache-dir=”D:\Temp\Vivaldi” – Move cache in specific folder. I use it for moving cache outside my SSD drive(C:) while keeping Vivaldi on SSD (for performance reason).
  • –disk-cache-size=1073741824 – Set cache size in bytes (here is ~1GB)

 

Some experiments for gpu workarounds/enhancement. Couldn’t work at all. As chromium often have troubles on several GPU I don’t advise to test them (they seems to be a placebo). 

  • –enable-features=CheckerImaging
  • –enable-native-gpu-memory-buffers
  • –enable-zero-copy  (provided also as a flag)

Lascia un commento