Creating default thread pool step is making launching pipeline very slow

[valleema]

Bug report

Expected behavior and actual behavior

When launching a pipeline with run command, actual start is very late (hangs 2 times few minutes at one specific step).

Program output

Launched at 08h47 (top of .nextflow.log):

janv.-27 08:47:32.130 [main] DEBUG nextflow.cli.Launcher - Setting http proxy: ProxyConfig[protocol=http; host=XXXX; port=NNNN]
janv.-27 08:47:32.287 [main] DEBUG nextflow.cli.Launcher - Setting https proxy: ProxyConfig[protocol=https; host=XXXX; port=NNNN]
[...]
janv.-27 08:49:19.846 [main] DEBUG nextflow.util.CustomThreadPool - Creating default thread pool > poolSize: 11; maxThreads: 1000
janv.-27 08:52:03.678 [main] DEBUG nextflow.Session - Session start invoked
janv.-27 08:52:39.739 [main] DEBUG nextflow.script.ScriptRunner - > Launching execution
janv.-27 08:52:39.755 [main] INFO  nextflow.Nextflow -
janv.-27 08:52:39.772 [main] DEBUG nextflow.util.CustomThreadPool - Creating default thread pool > poolSize: 11; maxThreads: 1000
janv.-27 08:59:59.905 [main] DEBUG nextflow.script.ProcessConfig - Config settings `withName:FASTQC` matches process FASTQC
janv.-27 08:59:59.912 [main] DEBUG nextflow.executor.ExecutorFactory - << taskConfig executor: local
janv.-27 08:59:59.912 [main] DEBUG nextflow.executor.ExecutorFactory - >> processorType: 'local'
[...]

The 2 steps nextflow.util.CustomThreadPool - Creating default thread pool > poolSize: 11; maxThreads: 1000 take 3 then 5 minutes.

Environment

• Nextflow version: nextflow-21.10.6-all
• Java version: openjdk 11.0.14 2022-01-18
• Operating system: Linux
• Bash version: GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)