TypeError Chrome

Troels Arvin 21 days ago

In Traccar's web-interface, immediately after logging in, I get the following error instead of Traccar's web interface. This is the latest version of Traccar, but it has also been seen in an older version. I only see it in Google Chrome (154.0.8037.17), not in Firefox.

Is this an error in Traccar, or in Chrome?

TypeError: Cannot read properties of undefined (reading '0')
    at mp (https://FOOBAR/assets/index-BcjufgMa.js:41:46625)
    at e.screenPointToMercatorCoordinateAtZ (https://FOOBAR/assets/index-BcjufgMa.js:839:20759)
...
    at https://FOOBAR/assets/MapScale-DbEeeVK0.js:1:263
Anton Tananaev 21 days ago

I believe it's already fixed on master.

Anton Tananaev 21 days ago

Please try the preview:

https://www.traccar.org/preview/

Troels Arvin 21 days ago

With the Traccar preview, my Chrome simply displays a spinning circle forever, instead of displaying the error message.
I run my Chrome in a remoted desktop, maybe that has to do with it, because its console states:

Uncaught GPUInitializationError: WebGL2 is required to display this map. We are sorry, but it seems that your browser does not support WebGL2, a technology for rendering 3D graphics on the web. Read more on https://wiki.openstreetmap.org/wiki/This_map_requires_WebGL
    at vU._setupPainter (index-DXy9311i.js:853:176517)
    at new vU (index-DXy9311i.js:853:150823)
    at index-DXy9311i.js:853:240730

When testing in another Chrome version (not through remote desktop), there is no problem with either version of Traccar. And in Edge it works fine.

So it seems my normal Chrome is simply an odd version, exacerbated by it running in a remote desktop session. It's probably not worth chasing this any longer.

Anton Tananaev 21 days ago

Can you open chrome://gpu in your remote Chrome and provide details.

Troels Arvin 21 days ago
Anton Tananaev 20 days ago

Your GPU report shows Chrome is using Mesa’s llvmpipe software renderer, which Chrome explicitly blocklists on Linux. This prevents Traccar from creating the map.

Could you completely close Chrome, then launch it with:

google-chrome-beta --ozone-platform=x11 --ignore-gpu-blocklist

Please check whether Traccar works afterward. This is a test to confirm the blocklist is the cause.

Troels Arvin 13 days ago

When I start Chrome with "--ozone-platform=x11 --ignore-gpu-blocklist", then I get the web UI in the same way as I do in Firefox. So my odd workstation environment using remote desktop is the culprit.