{"author":"Viktor Szakats","author_email":"commit@vsz.me","author_time":1755505722,"commit_time":1755553616,"committer":"Viktor Szakats","committer_email":"commit@vsz.me","hash":"2388b0e5878da030fac0e9d1ad490bc5447e37e0","message":"processhelp.pm: use `Win32::Process*` perl modules if available\n\n`Win32::Process::List` and `Win32::Process`.\n\nTo replace external calls to `tasklist.exe` and `taskkill.exe`.\n\nThe perl modules are wrappers/binding to Win32 API calls. They avoid\nlaunching external processes with a command shell (including MSYS2),\nthe external tool, and creating command-lines and parsing tool output.\n\nAccording to local tests and the CI, one test session calls\n`tasklist.exe` 350-400 times. `taskkill.exe` is rarely called:\nhttps://github.com/curl/curl/actions/runs/17012376726?pr=18296\n\nIt's hard to predict any possible side-effect of dynamically loading\nthe two necessary, module DLLs into the Perl process. The MSYS2 runtime\nif prone to fail when doing this in fork operations, as seen earlier\nwith the Win32.DLL module. But, is looks like a symptom, not the root\ncause for these failures, because the failures are present with or\nwithout perl.exe loading the Win32.DLL.\nRef: be01b60ce532af6eb18c11fbd565355dbb570a2e #18287\n\nCherry-picked from #18296\nCloses #18308\n","parents":["a559f94321424352c8db702d63119e5be74a1cda"],"tree_hash":"28114c28347e17b4895ace3b89ee8b70bd59d4cf"}