Hi there….just so we are all on the same page Safari and Chrome on iOS and Mac OS use Webkit. They are one in the same browser. Safari with iOS 15 has implemented some crazy stuff regarding privacy that can really mess up the ability for any website to run properly. So you will want to test with private relay on and off, and the use of a VPN.
I use 2K, 4K as well as 8K textures without issues on MacOS and iOS 15 using Verge. The problem is the compression and the timing of moving data in and out of memory. Each browser on each device has a limit to how much stuff can be stored. This includes scene files, data, textures, etc, including the browser itself. More recently each browser and device now have a Tab memory limit. So you constantly have to remove things from memory. The problem we are experiencing with Webkit currently is the memory will not release very quickly which causes problems loading anything big and if you have slower speeds like wifi or 4G or lower…the memory dump takes even longer.
For tracking whats been loaded you can use Chromes Developer Console and what the loads and it will provide a way you can debug why its not loading. It will give you a total transfer total to memory and will also provide info when you go over, but you are likely to see that visually as an error first.
If you are making applications for general distribution to the public, including older phones and OS’s you will need to either build specific bundles for each device type or build to the lowest common denominator. When we build for general public use…we set our max memory size to be 50Mb. Yes…modern browsers can hold more but since the iPhone 7 is still the most popular iPhone…we cant ignore that group so we have to play for 3G cell service and 50Mb phones.
Google searches for browser memory limits will get you set for figuring out what to aim for based on your target.
.
