bazel: Option --starlark_cpu_profile is completely broken on Windows

Description of the problem / feature request:

–starlark_cpu_profile command-line option crashes Bazel server on Windows.

Bugs: what’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

For absolutely any Bazel build on Windows adding --starlark_cpu_profile=pprof.gz to the command line causes immediate server failure: Server terminated abruptly (error code: 2, error message: 'Stream removed', log file: 'c:\_\jjgeprbx\server\jvm.out') jvm.out file mentioned is absolutely empty. I have verified the problem is present on multiple Windows machines, but does not reproduce on Mac and Linux.

What operating system are you running Bazel on?

Windows 10 20H2

What’s the output of bazel info release?

4.1.0, 4.2.0rc1