I am pretty sure v86 allocates all of the memory ahead of time, using one big array buffer. It’d probably be easy to find the code. However, that doesn’t mean

I am pretty sure v86 allocates all of the memory ahead of time, using one big array buffer. It’d probably be easy to find the code. However, that doesn’t mean that Chrome is actually allocating it all at once. It could very well be paging it in on demand. I have no idea. In that case, to measure the overhead, you’d need to fill the guest memory. I didn’t bother looking into it that deeply because I don’t really think it’s that interesting; an Electron x86 emulator is pretty impractical no matter how you shake it. It’s still pretty funny, though.