On my phone and using photos to report this error. We were at an in-person hackathon this past weekend and we found this problem (or two very similar problems) when using the replica with dfx 0.15.0.
Either on dfx deploy or on replica startup, it’s hard to tell or remember, these errors would be reported. It would then be impossible to actually finish a dfx deploy:
thread 'MR Batch Processor' panicked at 'MmapPageAllocator failed to mmap 765952 bytes to memory file #33 at offset 0 for deserialization: ENOEXEC: Exec format error'
And then I believe the true blockers on deploy were these:
tcp connect error, Connection Refused
Machine specs I could gather:
AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 Ghz, 8 GiB of RAM, Matebook D 15, Windows 10 Home 22H2, using WSL
This does seem similar to Errors creating a canister with 'dfx deploy'