[Switch 2 FW 23.0.1] KaiHEN stuck at Phase 2/4 – Anyone found a fix for the ±192-byte memory allocation issue?

Wait 5 sec.

Hey everyone, I've been trying to get kaiHEN running on my Nintendo Switch 2 (FW 23.0.1) through Civilization VII / CivSwitch, but I consistently get stuck at Phase 2/4 – Acquiring FS memory. I've already tried multiple attempts, including the experimental timing improvements from PR #7, without success. I'm hoping someone here has encountered the same issue or found a reliable workaround. My setup - Nintendo Switch 2 – Firmware 23.0.1 - Civilization VII / CivSwitch - MacBook Air M3 - Node.js 25.6.1 - Wi-Fi connection - 256 GB SanDisk Extreme microSD (FAT32) - kaiHEN 20261114c What's happening? Phase 1 always completes successfully. The payload reaches the console, and the connection works. However, Phase 2 consistently fails with errors such as: Unexpected manager allocation size: 12080 Positive canary verification failed 0 verified marker hits cleanup is unproven or placement is uncertain Interesting finding: ±192-byte fluctuations After analyzing the generated "reserved-gap" JSON files, I found the following memory allocation values across 17 checks: Allocated bytes| Occurrences 12272 (expected)| 12 12080 (-192)| 3 12464 (+192)| 2 It seems the memory accounting occasionally fluctuates by exactly 192 bytes. The code retries unexpected allocations, but eventually fails with "Unexpected manager allocation size: 12080". Already tried PR #7 I also tested the experimental fork from PR #7 with: NS2_WAVE_ATTEMPTS=10 NS2_TRIGGER_SHIFT_NS=-200000 Unfortunately, the result was still: 5 measured / 6 started 2 qualified windows 0 verified marker hits Unexpected manager allocation size: 12080 The console was rebooted between attempts. Relevant GitHub links My detailed bug report (Issue #10): https://github.com/s8n/civ7-fs-kaihen/issues/10 Experimental timing improvements (PR #7): https://github.com/s8n/civ7-fs-kaihen/pull/7 Original project: https://github.com/s8n/civ7-fs-kaihen Questions for the community Has anyone experienced the exact same ±192-byte memory allocation discrepancy? Is this likely a timing/race-condition issue, or could something else be affecting memory accounting? Has anyone successfully passed Phase 2 using a MacBook on firmware 23.0.1? Are there any confirmed fixes or safer debugging approaches? I'm particularly interested in understanding the root cause rather than repeatedly running the exploit. Since the logs report that cleanup cannot be verified, I've stopped further attempts for now to avoid unnecessary risks. Any advice from developers or people who successfully got past Phase 2 would be greatly appreciated. Thanks!   submitted by   /u/Odd-Bet8734 [link]   [comments]