bevy-website icon indicating copy to clipboard operation
bevy-website copied to clipboard

Published 20 hours ago • verified publisher icon bevyengine

Example showcase: loading bar gets stuck on meta file

Open rparrett opened this issue 1 year ago • 5 comments
trafficstars

Testing with Chrome 122.0.6261.129, Firefox 123.0.1 on macOS 14.2.1.

This seems to occasionally affect examples that load assets. I haven't been able to totally nail down the conditions that result in this behavior.

image

The issue seems to resolve itself after refreshing the page, but clearing the browser cache or restarting the browser don't seem to reintroduce the issue.

rparrett avatar Mar 16 '24 17:03 rparrett

Should be fixed by #840, but I think you have to clean the cache of all examples you already loaded

mockersf avatar Mar 16 '24 18:03 mockersf

Should be fixed by #840, but I think you have to clean the cache of all examples you already loaded

~~Fresh cache (deleted bevyengine.org site data from firefox) and I don't think I used the site, or at least this example, before that was even merged.~~

~~Image deleted~~

Edit: Nevermind; you have to manually clean the cache of every single page, can't blanket do the whole site. This is fixed. (Ctrl + F5 in my case to clean the cache per page).

TrialDragon avatar Mar 16 '24 20:03 TrialDragon

Ah, that explains some things.

Is it possible that we need to purge the cloudflare cache for the js files or something?

edit: Well, "need to" is strong language. But I had the same experience of nuking my browser cache and not seeing the new JS.

rparrett avatar Mar 16 '24 20:03 rparrett

Hmm, correction on my earlier statement; it wasn't cleaning the cache, it was refreshing the page (that happens alongside Ctrl + F5) like you already mentioned that solved it. But this doesn't happen on fresh browser install, so it is fixed for anyone who has never visited the site before. I wonder if you need to do a full nuke and delete entire browser history, cache, et cetera to fix this on a browser that did visit.

TrialDragon avatar Mar 16 '24 21:03 TrialDragon

3 weeks later, I just saw this again on the same sprite example.

I wonder if you need to do a full nuke and delete entire browser history, cache, et cetera to fix this on a browser that did visit.

If that is the case, and there's some workaround we can do on our end, we probably should.

But it feels like there might be something intermittent or racey going on here.

rparrett avatar Apr 06 '24 13:04 rparrett