Fix Piper memory pressure on iOS

2026-10-17 16:38:16 +02:00
parent b956527c72
commit c9b14e0726
6 changed files with 64 additions and 6 deletions
@@ -7,6 +7,23 @@ export function createOnnxWasmPaths(origin) {

 export function configureOnnxRuntime(onnxRuntime) {
  if (!onnxRuntime?.env?.wasm) throw new TypeError('ONNX Runtime WebAssembly settings are unavailable.');
+  // Piper 1.0.3 overwrites this value in TtsSession.init() with
+  // navigator.hardwareConcurrency. Override that source as well, otherwise an
+  // iPad may start a large WASM worker pool despite this setting.
+  const navigatorObject = globalThis.navigator;
+  if (navigatorObject && navigatorObject.hardwareConcurrency !== 1) {
+    try {
+      Object.defineProperty(navigatorObject, 'hardwareConcurrency', {
+        configurable: true,
+        value: 1,
+      });
+    } catch (_) {
+      // The check below converts an unsupported override into a clear error.
+    }
+  }
+  if (navigatorObject && navigatorObject.hardwareConcurrency !== 1) {
+    throw new Error('Piper could not be restricted to one processor thread.');
+  }
  // Piper already runs in a worker. Avoid a second worker pool on mobile Safari.
  onnxRuntime.env.wasm.numThreads = 1;
  onnxRuntime.env.wasm.initTimeout = 60000;