fix to a bug where sometimes threadpool could be configured to 0 workers

Mateusz Kopciński · Mateusz Kopciński · commit f90d74a8f760 · 2025-10-28T17:05:46.000+01:00
diff --git a/packages/react-native-executorch/common/rnexecutorch/threads/GlobalThreadPool.h b/packages/react-native-executorch/common/rnexecutorch/threads/GlobalThreadPool.h
@@ -33,6 +33,7 @@ class GlobalThreadPool {
             ::executorch::extension::cpuinfo::get_num_performant_cores();
       }
 
+      numThreads = std::max(numThreads.value(), 2u);
       log(rnexecutorch::LOG_LEVEL::Info, "Initializing global thread pool with",
           numThreads, "threads");
       instance = std::make_unique<HighPerformanceThreadPool>(numThreads.value(),

Original file line number	Diff line number	Diff line change
`@@ -33,6 +33,7 @@ class GlobalThreadPool {`
`33`	`33`	`::executorch::extension::cpuinfo::get_num_performant_cores();`
`34`	`34`	`}`
`35`	`35`
	`36`	`+ numThreads = std::max(numThreads.value(), 2u);`
`36`	`37`	`log(rnexecutorch::LOG_LEVEL::Info, "Initializing global thread pool with",`
`37`	`38`	`numThreads, "threads");`
`38`	`39`	`instance = std::make_unique<HighPerformanceThreadPool>(numThreads.value(),`