Fabian

It's technically possible, but would be quite a bit of work. I would gladly provide some pointers or review a pull request, but I don't have time to work on...

Sure! - [This](https://github.com/copy/v86/blob/e7f574f4d8ab577ef9095de0809eb5de7a30459f/src/rust/cpu/cpu.rs#L706) is the entry point for legacy system calls (int 0x80), and page faults, general protection error, etc. The latter you'll need to turn into signals. [Here](https://github.com/copy/v86/blob/e7f574f4d8ab577ef9095de0809eb5de7a30459f/src/rust/cpu/instructions_0f.rs#L1327) is...

Can confirm this, unfortunately bringing up a keyboard and capturing keyup and keydown events is quite tricky across mobile browsers.

Interesting idea, will probably do it just for the fun of it. That said, the [websockproxy](https://github.com/benjamincburns/websockproxy) is intentionally rate-limited, so most payloads will take too long to load. You can,...

Anything in the browser console? Can you check that the computer type is "Standard PC" in device manager?

I don't know what's going on in the 98 image. In the 2000 image you'll need to change the PC type to "Standard PC".

I can reproduce this. I also reverted to an older version of v86 (from January this year) and it had the same issue. When the crash happens chromium writes to...

Setting [`MAX_PAGES`](https://github.com/copy/v86/blob/d155439329875109a1b00bfbb557f32c550aade7/src/rust/jit.rs#L327) to 1 seems to fix the issue, so it's probably related to some of the existing issues chromium has with big wasm modules.

For reference, here's the corresponding issue on the chromium bugtracker: https://bugs.chromium.org/p/v8/issues/detail?id=11020

I did get Android working once (I believe android-x86-1.6-r2.iso), but it was so slow (taking one hour to boot) that I didn't bother pursuing this further. Still would be worth...