Configuration (config.yaml)
version: '1'
options:
k: Testing@f05b4d6c-4aad-4d37-b47b-92b809841339
s: http://localhost:8080
j: C:\Users\User\openjdk-17.0.2_windows-x64_bin\jdk-17.0.2
processTokens:
- 19696$BT
m3Frequency: 0m45s
Description
Only one process is configured using processTokens (19696$BT).
However, when running m3 on Windows, an additional process ID is also running, even though it is not defined in the configuration file.
This behavior is unexpected and reproducible.
Steps to Reproduce
Configure config.yaml with a single entry under processTokens
Run m3 on Windows
Observe running processes
Expected Behavior
Only the configured process (19696$BT) should be running/monitored.
Actual Behavior
An extra process ID is running along with the configured one.
Additional Notes
Issue appears to be Windows-specific
Configuration (config.yaml)
version: '1'
options:
k: Testing@f05b4d6c-4aad-4d37-b47b-92b809841339
s: http://localhost:8080
j: C:\Users\User\openjdk-17.0.2_windows-x64_bin\jdk-17.0.2
processTokens:
- 19696$BT
m3Frequency: 0m45s
Description
Only one process is configured using processTokens (19696$BT).
However, when running m3 on Windows, an additional process ID is also running, even though it is not defined in the configuration file.
This behavior is unexpected and reproducible.
Steps to Reproduce
Configure config.yaml with a single entry under processTokens
Run m3 on Windows
Observe running processes
Expected Behavior
Only the configured process (19696$BT) should be running/monitored.
Actual Behavior
An extra process ID is running along with the configured one.
Additional Notes
Issue appears to be Windows-specific