fix: reduce _waitForActiveHandles poll from 10ms to 100ms, add extensive IPC tracing. PI loads but main() stuck.

Author: NathanFlurry

native/v8-runtime/src/host_call.rs

@@ -204,6 +204,7 @@ impl BridgeCallContext {
     /// blocks on read() for the BridgeResponse, and returns the result.
     /// Error responses from the host are returned as Err.
     pub fn sync_call(&self, method: &str, args: Vec<u8>) -> Result<Option<Vec<u8>>, String> {
+        eprintln!("[v8-ipc] sync_call: {} session={}", method, self.session_id);
         let call_id = self.next_call_id.fetch_add(1, Ordering::Relaxed);
 
         // Register call_id in pending set (reject duplicates)

packages/nodejs/src/bridge-handlers.ts

@@ -3281,8 +3281,13 @@ export function buildModuleLoadingBridgeHandlers(
 	// The V8 runtime binary only registers a fixed set of bridge globals.
 	// Newer handlers (crypto, net sockets, etc.) are dispatched through
 	// _loadPolyfill with a "__bd:" prefix.
+	let _loadPolyfillCount = 0;
 	handlers[K.loadPolyfill] = async (moduleName: unknown): Promise<string | null> => {
 		const nameStr = String(moduleName);
+		_loadPolyfillCount++;
+		if (_loadPolyfillCount <= 20 || _loadPolyfillCount % 500 === 0) {
+			console.error(`[loadPolyfill] #${_loadPolyfillCount}: ${nameStr.slice(0, 80)}`);
+		}
 
 		// Bridge dispatch: "__bd:methodName:base64args"
 		if (nameStr.startsWith("__bd:") && dispatchHandlers) {

packages/nodejs/src/bridge/active-handles.ts

@@ -118,9 +118,9 @@ export function _waitForActiveHandles(): Promise<void> {
 						complete();
 						return;
 					}
-					setTimeout(poll, 10);
+					setTimeout(poll, 100);
 				};
-				setTimeout(poll, 10);
+				setTimeout(poll, 100);
 			}),
 		);
 	}