[Alloy] Non-browser process crash with --enable-logging

[ndesktop]

127.0.6533.89 (modified), but I did not touch that area, so I assume it will repro also in stock cefclient.
Launching cefclient as cefclient --enable-logging=stderr --v=1 --disable-chrome-runtime will crash any non-browser process.
I am noticing the command line for all cefclient processes command line do not contain --enable-logging at all (but strangely, --v=1 is present).
This will let the default initialization for Logging dest = LoggingDest::kFile; and since there is no kLogFile specified, a check crash follows.
I remember --enable-logging=stderr worked not so long ago (branch 6132 surely worked), so I wonder if was something changed in Chrome that affects this.

I know Alloy is on its way out, but for those (like me) who will still need to handle Alloy for some time, I'm asking if someone else encounters this nuisance (and if so, maybe to check what happened and adjust alloy_main_delegate.cc accordingly).

From what I quickly checked it is probably related to Remove log-file rule for sandboxed processes on Windows.