Sounds like WebGL didn't initialize. Do other WebGL demos work in your browser? If yes, I'd report this issue to the dev.

It works on my Note 3, but not on my S7. The N3 results are about 1.5/3.0 for me. Though wildly varying between runs.

Edit: It works on my windows PCs (even in a qemu KVM instance using the std vga, but of course the emulated GPU is slower). However, it doesn't seem to like any browser on linux.

With regards to Linux (though Android's Chrome has chrome://flags and chrome://gpu as well, so maybe some of this applies as well):

It didn't work for at first, but I got it to show me the "Ah snap! There was no error compiling the test kernel or running it, but the numbers don't check out." message at least. By changing the deviation var to e.g. 0 in the debugger you can also force it show you the results (JS: 0.56, JS&Turbo.js: 1.74), but I don't know if those results mean anything.

Steps to maybe fix:

Does e.g. glxgears work?

On Chrome, check the following two pages:

chrome://flags/ <-- I enabled "Override software rendering list", "Experimental canvas features", "WebGL Draft Extensions" but don't know if all of those are necessary. Better change them back later.

chrome://settings <-- Advanced -> System -> Use hardware acceleration when available

chrome://gpu/ <-- Check if WebGL is enabled, etc. (also check log messages at the bottom)

My graphics hardware is a positively ancient Intel 965GM. (On Windows on a much faster CPU and using Intel HD Graphics 4000, I get JS: 1.28, JS&Turbo.js: 3.82.)

Reading the benchmark script, and the explanation of it at github, I think the deviation is there to account for floating point artifacts. I.e. where JS = 0.01499.. and GPU = 0.01500.., that's fine, but if the numbers (read results from the fractal function) are deviating more, that's an error.

Edit: Actually, "(JS: 0.56, JS&Turbo.js: 1.74)" seems to be a valid result from what I've seen. May just be that the chosen deviation value is an unfortunate edge case.

Was curious, too. It's the archlinux icon/shortcut encoded as base64. (it's a common trick to store binary data in a batchfile)

From what I can gather from the BOW discussion (see my link below), it's a kind of custom arch distro (https://cdn.turbo.run/alwsl/alwsl.sfs). AFAIK WSL is just a rootfs extracted by the lxrun cmdlet. So I guess this replaces Microsoft's rootfs with arch. It seems to be modified to work around some issues in WSL.

Looks like heavy WIP (https://github.com/turbo/alwsl/issues/5). There isn't really anything on the main branch, indicating that it probably shouldn't be used(?) yet(?). Also, this seems to be the backstory: https://github.com/Microsoft/BashOnWindows/issues/8#issuecom...