webvm icon indicating copy to clipboard operation
webvm copied to clipboard

[Safari ?] Hangs randomly

Open Parura5726 opened this issue 3 years ago • 6 comments

Basically the title, when I try to use vim or just the terminal, the website hangs, the only way to fix it is reloading. js console shows a debug message of the format Fault addr cb8bb1a4, ip 556ece35, tid 4 followed by Fault from Inode 28281.

Tool Version
Safari 15.4 (16613.1.17.1.13, 16613)
Macos Big Sur 11.6.2
Model M1 Macbook Air 2020

Parura5726 avatar Oct 04 '22 07:10 Parura5726

Can the issue be reproduced with our latest release?

alexp-sssup avatar Oct 07 '22 10:10 alexp-sssup

Unfortunately it still does.

Parura5726 avatar Oct 12 '22 07:10 Parura5726

Could you possibly run the same experiment either with Firefox (non-Incognito) and/or Chrome/Chromium (on the same device)?

carlopi avatar Oct 12 '22 07:10 carlopi

I cannot, the computer has a whitelist of executables its allowed to run, and the only allowed browser is Safari. I doubt that those execute restrictions are the cause of the errors though.

Parura5726 avatar Oct 12 '22 08:10 Parura5726

I believe the problem here is that Safari 15.4 had a couple of stubble WebAssembly bugs (eg https://bugs.webkit.org/show_bug.cgi?id=237180) that you are most probably hitting against.

I did run some test on a IPhone with 15.6, and WebVM seems to work as expected.

Would it be possible for you to give it a try from a different machine and / or have your browser updated?

carlopi avatar Oct 13 '22 14:10 carlopi

Nope, last test was run on 16.0, but i retested it anyways and it still hangs, this time while running a compilation using gcc, not vim.

Parura5726 avatar Oct 13 '22 20:10 Parura5726

Although we could never reproduce it locally we have fixed many bugs over the last few months. Can this problem still be reproduced?

alexp-sssup avatar May 22 '23 14:05 alexp-sssup

Can't seem to reproduce any hanging on Safari 16.1 (18614.2.9.1.12), macOS 13.0 (22A380), M1 Macbook Air 2020.

vim:

Screenshot 2023-06-08 at 00 02 21

gcc took a few minutes to cold start, but worked: Screenshot 2023-06-08 at 00 05 13

(Not sure what's going on with the user and sys time results there, but I'd imagine that's unrelated to this issue?)

bates64 avatar Jun 07 '23 23:06 bates64

Not sure what's going on with the user and sys time

The data structure is simply not populated and then mis-printed by user space, it is not a problem.

Closing this issue, it's likely that whatever problem was there originally has been fixed in the meantime

alexp-sssup avatar Jun 08 '23 06:06 alexp-sssup