Manjaro ARM (KDE-Plasma) on a RPI-5.
Trying to open flightradar24.com. Tried both chromium and firefox. Chromium shows “no map” and no flight routes or icons. Other parts of the website is visible (menus, buttons, adjustment stuff etc.). But the actual live map is not there.
Tried to open the same website in firefox and the outcome is the same, in addition to that, firefox freezes the system and crashes after a while (when this page is opened).
Hi,
flightradar24.com is one of my favourite website with ventusky.com
I did a test with my odroid c2 (Plasma desktop), no freezes, no crashes but some error message, see below
WebGL 2.0
The WebGL 2.0 specification has recently been released, and implementations of the new API are becoming available.
WebGL 2.0 requires hardware with OpenGL ES 3.0 support or comparable desktop OpenGL
feature support. Not all systems capable of running WebGL 1.0 will be able to run WebGL
2.0. See http://caniuse.com/#feat=webgl2 for availability details.
Hmm. While your browser seems to support WebGL2, it is disabled or unavailable. If
possible, please ensure that you are running the latest drivers for your video card.
For more help, please click this link.
https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration?redirectslug=how-do-i-upgrade-my-graphics-drivers&redirectlocale=en-US
I applied the hardware acceleration, restart the web browser, same issue.
Yeah i also like ventusky. There is also windy (similar)
I tried to change renderer settings in chromium and that is when i got the same error that you got. With angle set to gles, we are supposed to have webgl2 support and this website confirms it actually:
My chromium is green for both v1 and v2.
So this is interesting. All other websites which feature “maps” do work. The only problem is here in flightradar.
Thanks for your feedback, I forgot to test and mention that ventusky.com is working on the Odroid c2 device.
This is wierd.
I am running KDE plasma on an RPI5.
I am running chromium version 131.0.6778.264 (not Flatpak), which is the latest from the repository.
chrome://gpu gives:
Graphics Feature Status
- Canvas: Hardware accelerated
- Canvas out-of-process rasterization: Enabled
- Direct Rendering Display Compositor: Disabled
- Compositing: Hardware accelerated
- Multiple Raster Threads: Enabled
- OpenGL: Enabled
- Rasterization: Hardware accelerated
- Raw Draw: Disabled
- Skia Graphite: Disabled
- Video Decode: Hardware accelerated
- Video Encode: Software only. Hardware acceleration disabled
- Vulkan: Disabled
- WebGL: Hardware accelerated
- WebGL2: Hardware accelerated
- WebGPU: Disabled
- WebNN: Disabled
I then open flightradar24.com in a new tab and get the issues described by @Sam_Fisher above.
I then press the refresh button for flightradar24.com once or twice and then the site functions correctly, showing maps and planes, but responds very slowly.
I then refresh chrome://gpu and get:
Graphics Feature Status
- Canvas: Software only, hardware acceleration unavailable
- Canvas out-of-process rasterization: Disabled
- Direct Rendering Display Compositor: Disabled
- Compositing: Software only. Hardware acceleration disabled
- Multiple Raster Threads: Enabled
- OpenGL: Disabled
- Rasterization: Software only. Hardware acceleration disabled
- Raw Draw: Disabled
- Skia Graphite: Disabled
- Video Decode: Software only. Hardware acceleration disabled
- Video Encode: Software only. Hardware acceleration disabled
- Vulkan: Disabled
- WebGL: Software only, hardware acceleration unavailable
- WebGL2: Software only, hardware acceleration unavailable
- WebGPU: Disabled
- WebNN: Software only, hardware acceleration unavailable
How can a website turn off hardware acceleration?
By crashing some module perhaps. Can you also try firefox? Firefox froze the whole system until it crashed itself once i opened flightradar. The website probably has some bad code. Or maybe x86 machines work with it so they don’t care about it.
I tried refreshing the page like you did and my experience is exactly the same as yours. Rendering engine (probably) crashes and here is the result:
Graphics Feature Status
- Canvas: Software only, hardware acceleration unavailable
- Direct Rendering Display Compositor: Disabled
- Compositing: Software only. Hardware acceleration disabled
- Multiple Raster Threads: Enabled
- OpenGL: Disabled
- Rasterization: Software only. Hardware acceleration disabled
- Raw Draw: Disabled
- Skia Graphite: Disabled
- Video Decode: Software only. Hardware acceleration disabled
- Video Encode: Software only. Hardware acceleration disabled
- Vulkan: Disabled
- WebGL: Software only, hardware acceleration unavailable
- WebGL2: Software only, hardware acceleration unavailable
- WebGPU: Disabled
- WebNN: Software only, hardware acceleration unavailable
Firefox crashes a few seconds after opening flightradar24.com.
Also, I ran firefox from the terminal and got the following error:
GetShaderInfoLog() →
0:2(12): error: extension `GL_EXT_shader_texture_lod’ unsupported in fragment shaderGetShaderSource() →
#extension GL_EXT_shader_texture_lod: require
void main() {}Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=7.03647) [GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0”
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.4649) [GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0”
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.4649) |[C1][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.5049) [GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0”
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.4649) |[C1][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.5049) |[C2][GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0” (t=42.5049) [GFX1-]: Couldn’t sanitize GL_RENDERER “V3D 7.1.7.0”
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Segmentation fault (core dumped)
Hardware acceleration OK after this.
No issue with Firefox on the following devices
Odroid C4
Odroid N2
Odroid M1
Given that, it seems likely it could be a problem with the site.
Here’s the official response response to a similar issue in March;
But nl.smart says that the website works on his odroid machines. I am assuming the operating system is manjaro arm also. So then i think the issue stems out of the “kernel” maybe, in the case that the RPI devices are the only devices having an issue with the particular site.
Or maybe an opengl issue particularly for the RPI devices?
Wow, those things have “mali” gpus 
That is pretty cool. It is not surprising to me that they can open that page without issues. RPI is not strong on the hardware side, but probably makes up for it in terms of software support. But it’d be cool to have a mali chip on that’s for sure.
DNS issues?
It’s not something to rule out entirely.
Well, I can say with authority… 
But you are disregarding the fact that opening that website “breaks” chromium’s rendering engine (it reverts to software rendering) and crashes firefox. If it was a dns issue, that wouldn’t happen right?
BTW, i tried to access the website via “tor network” and the result is the same.
Scrolling back, now I see that, but, nothing comes to mind that ticks all the right boxes.
Or, perhaps one of their CDN’s are offline or otherwise unreachable. It’s anybody’s guess at this point.
I am repeating myself but, if it was a server issue, again, it wouldn’t break browser functionality or cause crashes. My money is on either the kernel or the opengl (mesa) package, which is used by both chromium and firefox to render 3d stuff on web pages, at least when it comes to ARM. The odroid devices work with that page probably because they have a dedicated mali gpu and 3rd party drivers which work better with opengl. Opengl support on RPI devices is rather improvised. We don’t have a dedicated gpu.
In any case, this is no major issue. It is just one website. Here is an alternative that works:
