Not rendering on Raspberry Pi 3B

[olexs]

I'm trying to get this module to work on my mirror that runs on a Raspi 3B. Setup is default using up-to-date MM v2.18.0 and supplied Electron browser, all running on Raspbian 10 Buster with all packages up-to-date.

When testing the config on the desktop PC with an identical config.js and all versions, all works perfectly. However, on the mirror when I try to activate the module the following happens:

• The frontend starts up and freezes a couple seconds in, Chromium becomes unresponsive (the clock module stops updating seconds)
• Couple seconds later, Chromium reloads from black and renders all modules
• MMM-TomTomTrafficIncidents is placed and correctly sized, the copyright box is visible on the bottom right, but the actual map box is black and has a "frowny face" on top left - I think the Chromium process rendering the iFrame crashes.

All this accompanied by the following red-colored errors in pm2 logs:

0|MagicMirror  | [8201:0220/200959.163491:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMirror  | [8238:0220/200959.516610:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
... some "green" output from various frontend modules doing their thing ...
0|MagicMirror  | [8238:0220/201006.076728:ERROR:gl_utils.cc(318)] [.WebGL-0x4dc15500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
0|MagicMirror  | [8206:0220/201006.667530:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
0|MagicMirror  | [8163:0220/201009.324221:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=135

After this the mirror continues running, the iFrame remains broken. Googling the errors isn't of much help.

If I deactivate the MMM-TomTomTrafficIndicents module in the config, these errors don't appear and the mirror and all modules boot up smoothly, with no freezing up. So I'm pretty sure the errors are to do with the module and the embedded TomTom map / Mapbox.

Things I tried:

• changing the GPU memory allocation from the default 64MB to 128MB: no visible effect.
• switching to the "G2 GL driver with fake KMS" as described in Black screen  #4 (comment): Chromium appears to render stuff faster (didn't measure anything), but no effect on the error and the iFrame crashing.

What hardware and software have people gotten this to run on? I assume a Pi 4 would help, having a bunch more GPU power and proper drivers, but they are a bit unobtainium right now. Could upgrading to the latest Raspbian (based on Debian 11 Bullseye instead of 10 Buster) possibly help as well?

[Travelbacon]

Hmmm. Thanks for finding this out. It could be that API from TomTom is too extensive for a RPi 3B or a earlier. I see that TomTom uses quite a lot of rendering in their options. There are a lot of layers you can use and dynamically adjust.

I've developed the code on a I5 laptop with Debian and deployed and tested it on a RPi4. I have a RPi3B as well, but it is running as server for home-automation tasks without X.

Did you (or can you) try to ask this question on the TomTom forum itself please? This module uses the Maps SDK with out any extravagant options. It is very basic. I think the developers of TT would like to hear from this as well. I could ask this, it is that I don't have a RPi3B available and can't interact or test feedback. If you could do that, that would be very appreciated.

[Travelbacon]

Does the example HTML run on your RPI3B in a Chromium browser?
https://github.com/Travelbacon/MMM-TomTomTrafficIncidents/blob/master/tomtomv6.html

[susl192]

I have the same problem. The example file does not run on my RPI3B in Chromium browser. Same problem, it only loads the marker but no map.

[Travelbacon]

Just to be sure, the example loads on a deskop pc or computer?

I am a bit afraid that this module can't run on the Pi3B...

[susl192]

Same result by loading the example file on computer...only the marker is shown.

[Travelbacon]

Please add your API-key on line 18 and see if it works.
key: 'your key', //add here your key with 's around them.
E,g,
key: 'gwsaUGCZfUcdASD3das2ugm1lQsdfadsT8RAyasdGGI', (fictional key)

I this doesn't work. Can you give me the output of the conse in your browser? (F12 and reload the page.)

[susl192]

With the API-key the example file does load on the computer and shows the map.

[susl192]

Now I tested the example file with the api-key on the raspi and it works now. It loads the map in chromium.

But not as module within the MM.

[olexs]

Ah, that is interesting. So it may be an issue with Electron-bundled Chromium specifically. I'll test my setup with a standalone MM server and default Chromium tomorrow to try and reproduce, if it works that may be a way to run this on a 3B.

[Travelbacon]

I am very curious what the outcome will be.
On the developer site of TomTom I get a feeling that WebGL can be an issue with the Electron.

Maps and services libraries support most of the modern browsers like Google Chrome (64+), Mozilla Firefox (60+), Safari (11+) and Edge (41+), however depending on the browser version and used hardware, certain features or future improvements may not be available. Especially in case of Maps library which is based on WebGL technology, you may want to manually assure support by visiting Check browser support example .
We recommend to always use the newest version of a browser for the best experience.

Pre-requisites from TomTom dev site

[olexs]

Oh this is interesting. Indeed, with "normal" Chromium (92, slightly out-of-date version) it works just fine on the Pi 3B - running MagicMirror via npm run server and then opening http://localhost:8080 in the browser, all is well.

Well, when I say "just fine", it's extremely slow :D but it works, just takes a while to render initially.

I'll see if something can be done with Electron settings or similar to replicate. If not, I'll have to come up with a pm2 script to run the setup with npm run server and Chromium in kiosk mode in separate processes. Either way, there's a solution, hooray.

[Travelbacon]

Nice work! And thank you so much for doing this research.

I think I will place a warning that a Pi4 has the best performance.

There are some more exchange money by using this WEB kit of TomTom. For instance. I have a script that makes all the icons visible in the zoom layer of choice. But it has a scope issue when using it under MagicMirror module.

[Travelbacon]

I think I might have found the issue. There is long and old issue with WebGL and Raspberry PI3 and older.
Test if you have enabled openGL driver set in raspi-config. The Wiki of MM for Raspberry has more details.

[olexs]

Unfortunately, that doesn't solve the issue. I tried both the "fake KMS" and "full KMS" drivers, both of them result in the map working in standalone Chromium, but not in Electron. It seems to be that the Electron-bundled Chromium binary doesn't properly support the somewhat weird OpenGL implementation as well as the "proper" Chromium port included in Raspbian packages. Still working on it though, not giving up quite yet :)