WebSupport
Active member
So here's another possibility. Your hosting guys can limit the number of concurrent image requests by the same client (ie browser), which would also explain it especially since it's always at the end of the 360 image loading (94-97%) and it doesn't happen after most of the images are cached on further retries. And we do load them concurrently... to speed things up. I guess this is the most likely cause. Please try reducing the number of images to 30-2x and retry and if this helps you can go back to GoDaddy and see if they can help with the limitation.
Here's a post closer to the bottom (second from the bottom as of right now) that talks about the same issue due to concurrent request limitation on Apache / Linux .
http://serverfault.com/questions/237419 ... g-requests
Here's a post closer to the bottom (second from the bottom as of right now) that talks about the same issue due to concurrent request limitation on Apache / Linux .
http://serverfault.com/questions/237419 ... g-requests