This is because someone testing manually might want to pass additional keys via the command line to a real Chrome release with the component updater enabled, and it would be surprising if the manually-passed keys were overwritten some time after startup when the component updater runs. For issuers with keys provided through both the command line and TrustTokenKe圜ommitments::Set, the keys provided through the command line take precedence. These keys are available in addition to keys provided by the most recent call to TrustTokenKe圜ommitments::Set. Manually sets additional Trust Tokens key commitments in the network service to the given value, which should be a JSON dictionary satisfying the requirements of TrustTokenKe圜ommitmentParser::ParseMultipleIssuers.
additional-trust-token-key-commitments ⊗ ↪Īdd additional capabilities to the AppContainer sandbox used for XR compositing. ↪Īdd additional capabilities to the AppContainer sandbox on the GPU process. This flag implies -alsa-check-close-timeout=0. Apps cannot start until provided resources. ↪įlag indicating that a resource provider must be set up to provide cast receiver with resources. TODO(rockot): Make it possible for embedders to override this argument on a per-service basis. We reserve 8 to mean "whatever", and this will ultimately lead to processes with /prefetch:8 having inconsistent behavior thus disabling prefetch in practice. process types) of the same executable image so that different types of processes don't trample each others' prefetch behavior. Prefetch arguments are used by the Windows prefetcher to disambiguate different execution modes (i.e. Use profiles 5, 6 and 7 as documented on kPrefetchArgument* in content_. prefetch:# arguments for the browser process launched in background mode and for the watcher process. Note: # must always be in otherwise it is ignored by the Windows prefetcher.
Note that the browser process has no /prefetch:# argument as such all other processes must have one in order to avoid polluting its profile. Because reads depend on the process type, the prefetcher wouldn't be able to observe consistent reads if no /prefetch:# arguments were used. It has been observed that when file reads are consistent for 3 process launches with the same /prefetch:# argument, the Windows prefetcher starts issuing reads in batch at process launch. prefetch:# arguments to use when launching various process types. This page lists the available switches including their conditions and descriptions. Some change behavior of features, others areĭebugging or experimenting. There are lots of command lines which can be used with the Google Chrome browser.
0 kommentar(er)
