High memory and CPU utilization on vugu.org home page about vugu

[tomnz]

Wanted to leave a note that this crashes the page outright after ~10s on my Pixel 3 using Chrome. It seems primarily memory related, as afterwards apps (including the home screen) need to "reload" when switching to them, so I suspect they had been shifted out of active memory.

[whtiehack]

Same as stealth mode.

[bradleypeabody]

I suspect this a general issue with Go+WebAssembly (and possibly specifically in Chrome). The main render loop blocks on a channel and while it is of course using some memory over 2GB makes no sense - possibly this is some internal mem-mapped file number from Chrome or something.

I'll see if I can reproduce it and if there is anything in Vugu that might be causing this but there's not much I can easily do about bugs in Go, Chrome or the associated wasm support if that turns out to be the case.

[Hades32]

Seems to be the case in all Chrome forks. Edge seems to handle it quite fine. (All Win10 latest stable)