chrome flag

Welcome to fun with chrome flags. In a previous post, I’ve discussed six flags which are used as per the need. Here I’ll explain few settings to enhance the security of the browser with these flags and less use of any extensions. Let’s look at some other flags which might help on the test.

  1. chrome://tracing

this chrome flag allows the developer to trace javascript and rendering, system tracing like audio, benchmark, cache storage, GPU, UI and other options. As per the need user can choose from edit categories.

chrome flags
chrome flags

On the right side, there are disabled by default categories which might crash some functionality of the browser on change. On the left side audio, GPU, Omnibox, shutdown and startup, Netlog and other components that can be traced. The browser might crash after recording and on 100% buffer flow. charts of different threads will be generated with its process id.

2. chrome://profiler

This chrome flag generates the parent and child threads started by the browser, some are browsers main thread, GPU thread, input output thread and the function name by which the thread is started.

chrome flags
chrome flags

 

The source location is also described in the tabular form. some other fields are processed type, execution thread and thread’s queue time.

3. chrome://gcm-internals

chrome flags
chrome flags

Work of this chrome flag is simple, the flag records the connection logs of the website with device information like connection initialized, connection failed, connection reset with network number errors.

4. chrome://flags

This chrome flag contains a lot of experimental features which might crash the browser on the change like password generation, in depth tracing of the browser navigation, extension toolbar design, child account detection, web use etc. Some helpful experimental features are shown autofill predictions – it will predict the values of form, Safe

chrome flags
chrome flags

search URLs reporting – it’ll report back the inappropriate URLs that users have typed. Other one option is TCP fast open which will faster the data send of the browser but this option lies in ‘Unavailable experiments‘. That is all with the flags in this post, Most of the user-friendly flags are covered in the last two post. For more information on chrome flags go to Chrome OS wiki, you’ll get the better insight.

To turn the experimental feature on or off in chrome, Follow these below steps.

  1. First download chrome browser from https://www.google.com/chrome/browser/desktop/index.html
  2. Open a new tab or window in chrome.
  3. Type chrome://flags (or about://flags) in the location bar.
  4. Find the feature or functionality you want to toggle on or off Note that you can use, find in page (control/command + f) to quickly locate a particular feature.
  5. Click on the enable or disable the link.
  6. Click on the relaunch now button at the bottom of the page.

Once your browser has relaunched, the user can start experimenting with whatever feature or a new piece of functionality you just enabled. For a list of other special chrome URLs which expose various functionality and information about Chrome, type chrome://about in your location bar. There are also command line flags chrome offers and the user can find a comprehensive list on this blog and know the explanation of how to use them in the chromium.

1 COMMENT

LEAVE A REPLY

Please enter your comment!
Please enter your name here