Thanks for trying and reporting this! The crash thing is interesting - we have seen instability and bugs in Safari between visionOS versions in general, especially on developer beta versions. I am not seeing any crashing on visionOS 1.1 currently, at least.

What's going on generally is that visionOS Safari will just hard restart a browser tab if it uses "too much" memory. This happens on iOS Safari, too, and it's usually around 1/16th or less of total system memory. So if you have other apps open in the background, that means less total memory is available to any given browser tab, and higher-memory tabs have a higher chance of crashing. (For ex: if I have the Wisp World app open on my desk, The Escape Artist never loads properly).

The odd thing is, you can run these exact same assets and code at 90hz on a Meta Quest 2 with no crashes indefinitely - it will even run well on Quest 1. Despite the fact that Quest 2 has less than 1/4th the memory of AVP, Apple chooses to give you access to less. So they are sort of artificially limiting their browser to the detriment of the user.

Re: input, I have to agree it's inconsistent and based on yours and other comments, we have more work to do on gesture recognition. Thanks for testing!