Chromium command-line logging flags behave differently when specified in package.json

NW.js version 0.16.1
Windows 10
Software written on Mac OS 10.12.2

I am experiencing different behaviour when using Chromium’s --enable-logging flag as part of a NW.js application. On a Windows 10 machine, specifying the logging flag as part of the package.json "chromium-args": "--enable-logging --v=1" spawns two extra prompt windows in addition to the main window. This behaviour does not occur on Windows 7.

Searching the Chromium documentation suggested adding the --no-sandbox flag would solve this issue. Adding it to the package.json file did not change the behaviour.

However, providing the logging flag through the command line and not in the package.json file yields the desired result.

"App Name.exe" --enable-logging --v=1
The log file is generated as expected and no extra windows are spawned on launch. Why is there a difference when I specify the argument on the command line vs. in the chromium-args section of the package.json file? And secondly, how can I get the desired behaviour by specifying everything in the package?

Same question posted on SO: http://stackoverflow.com/questions/41880316/nw-js-chromium-logging-flags-behave-differently-when-specified-in-package-json

Author: Fantashit

1 thought on “Chromium command-line logging flags behave differently when specified in package.json

  1. Great work!
    Launching from a shortcut with --enable-logging or specifying that switch in package.json’s chromium--args the console windows no longer show up!
    Thank you!

    • NW.js v. 0.25.5 (nightly) (normal build)
    • Windows 10 Prof. (x64)

Comments are closed.