Right, but people are saying it also crashes sometimes on the desktop version (which I haven’t seen). I could boot up my Xbox and watch it crash, I guess, but with no developer tools available on the Xbox, I won’t be able to dig into the code and find out what’s causing it.
I suspect it has something to do with the number of video files on the Raam (9 videos) and Gargos (10 videos) pages. That’s why I’m curious if something like http://ki.infil.net/cbreaker.html (9 videos) or http://ki.infil.net/combo4.html (11 videos) crashes for Edge users. I do extra Javascript magic on the character pages that I don’t do on those, so I need help tracking the problem down.
I assume you may have figured out a potential cause then? I always assumed it was because of too much media on the page or perhaps a specific media or unsupported file type myself.
At 1st glance, the 1st page works fine - I was able to load all of the videos and read the entire combo-breaker page with no issue.
No issue with the 2nd page on combos.
The 3rd page with Raam crashed the app almost immediately - it didn’t even finish loading the page.
The 4th page, also with Raam, also crashed similar to the last 1.
The 5th page crashed faster than any other. NOTHING loaded at all - it crashed on a white screen before I could even see any text!
So, my conclusion is that JS magic (whatever the heck that is) is most definitely the culprit.
Gonna just list off some things on loading with a wired 75Mb down internet connection with a computer that has a i7-4700 and 8GB of DDR5 memory. Of course this is using the Edge App on PC.
Page loads without videos. It takes 10sec for the videos to load, and they all pop up simultaneously.
Same as 1.
Loads fine with no errors, or delayed loading of videos.
I, uh, think you’re thinking of something else, friend (probably Java or Flash, neither of which are related to Javascript).
Okay, one last test. This page has absolutely no content except my “polygraph” visualization, which seems to be the common aspect to all the pages that crash. Does this page crash?
Lol, believe it or not, that Raam Test page crashed for me too. It loaded it, and I saw the greeting, but it crashed about 5 seconds later. (Using Edge app on XOne)
I’ve had trouble getting this visualization to work in IE/Edge before, because Microsoft suuuucks at SVG commands. I think I’m telling it to draw the polygraph in a way some versions of Edge (but not all, of course) don’t like.
I’ll have to try and figure out which of the drawing commands it doesn’t like. But this must be the cause. It’s not the fact that I have tons of video or tons of OTHER javascript on other pages, it’s this particular part of the javascript that’s doing the damage. But okay, at least I know where to concentrate my search now.
Making them static pngs means they aren’t generated dynamically, so a) you don’t get the fun interaction on the characters.html page where you can blend and morph between them, and b) every time I change something I have to manually generate all the pngs again.
It’s much better just to fix the Javascript issue itself than to remove functionality. If I can find it. I have a sneaking suspicion which command is causing it, but I’ll do some research.
Makes sense. Sorry to hear there’s more work, but at least you have a heading rather than going at it blindly.[quote=“Infilament, post:297, topic:250”]
Edge sucks.
[/quote]
This is why I have both Firefox and Chrome, as well as Comodo Dragon.
That’s a good start in my book, instead of looking at a sea of letters, commands and numbers and trying to find the culprit. Sorry, @Infilament, we have probably created more work for you
Well, if half my site crashes on the XB1 browser (and ALL character pages, which is uhhh kind of a big deal), then I should probably try to fix it.
The main problem is… Edge claims they are compliant with a bunch of commands, but then in practice they aren’t, and their browsers crash. The real answer is just for Edge to actually support all the things they say they do. You even see that different versions of Edge do not do the same things (it won’t crash on desktop, for instance). It’s a huge mess and Microsoft browsers have always had these problems. Both Chrome and Firefox have spent years being the leaders in developing standards, and Microsoft is very far behind in adopting them.
I will probably try to fix the problem, then ask you guys to help me debug again. Because I have no access to the developer console on Xbox One, I will basically have to make a series of “guesses” as to where the problem lies, and get you guys to check in between.
