Difference between revisions of "Useful Chrome Flags"
m |
|||
| Line 40: | Line 40: | ||
== Disable JavaScript function inlining == | == Disable JavaScript function inlining == | ||
<code>google-chrome --js-flags="--max-inlined-bytecode-size=0"</code> | <code>google-chrome --js-flags="--max-inlined-bytecode-size=0 --no-maglev-inlining --no-turbo-inlining"</code> | ||
Latest revision as of 12:16, 19 December 2024
See this page to find out how to specify these flags.
Disable WebGL (both WebGL 1.0 and WebGL 2.0)
Run Chrome with this flag to test that your app response properly to missing WebGL capabilities on the user device.
google-chrome --disable-webgl
Disable WebGL 2.0
Specify this flag to simulate running your app on older devices with missing WebGL 2.0 support.
google-chrome --disable-webgl2
Disable 60 FPS limit
By default, web browsers limit rendering framerate for WebGL apps. Specify the following flags to disable such limit:
google-chrome --disable-gpu-vsync --disable-frame-rate-limit
Disable GPU hacks
google-chrome --disable-gpu-driver-bug-workarounds
Enable WebGPU on Linux
google-chrome --enable-unsafe-webgpu --enable-features=Vulkan
Disable restrictions on accessing local files
Allows to run Verge3D apps by clicking on local HTML files (without using any server). The app and corresponding assets will be opened via special file://PATH links.
google-chrome --allow-file-access-from-files
Trace function optimizations/deoptimizations
google-chrome --js-flags="--trace-opt --trace-deopt"
Disable JavaScript function inlining
google-chrome --js-flags="--max-inlined-bytecode-size=0 --no-maglev-inlining --no-turbo-inlining"
