Currently chrome://conflicts only shows information about the browser process. This enumeration needs to happen in all process types. It also needs to be a continuous process in order to observe modules that are loaded after startup (third party that injects, etc).
Comment 1 by chrisha@chromium.org
, Nov 3 2016