can’t access property “disable”, Me.touchPitch is undefined
Hi there!
Since today in the evening I always get this error message when I am trying to open the Kurviger web site on my computer. I am running Firefox on Linux, 64bit.
I tried the following:
deleted browser cache, including “website data”, etc.
update Firefox to latest version (154.0.1)
start Firefox in troubleshooting mode (all extensions disabled)
start Firefox with a newly created, fresh profile
installed Chromium (Version 151.0.7922.173) and tried with this
All these measures did not change the behaviour!
I am able to open the Kurviger web site normally and open and save routes with my wife’s computer, Firefox 134.0.1, Linux 64bit.
I am very confused …
Please help; I have to plan several tours next week.
Thank you!
Best regards, Johannes
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:154.0) Gecko/20100101 Firefox/154.0
Cookies Enabled: true
Screen: 1600 x 900 px - 1dppx
can’t access property “disable”, Me.touchPitch is undefined
(Debug information, this helps us helping you, you can remove this if you don’t want to share this data, it should not contain any personal or sensitive information)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:154.0) Gecko/20100101 Firefox/154.0
Cookies Enabled: true
Screen: 1680 x 1050 px - 1dppx
Thanks for reporting this issue. We were able to reproduce this issue with rather old hardware. I am guessing you might be running older devices?
That said, we just released a hoftfix, that should hopefully resolve the issue. Can you verify that everything is working as expected now @Johanneshau@Peter_Czurda ? You might need to reload the website or maybe even using Ctrl+Shift+R to get the latest version immediately.
It opens but no map is visible. (when trying with Chromium it says WebGL could not be loaded)
When I try to select a different map Firefox crashes
I am able to log in to my account
When logged in my preferred map (open Germany something) is visble
I am able to navigate to saved routes (Cloud / …)
When selecting a route and clicking “load” Firefox crashes
Chromium shows the following error message:
Message: Uncaught TypeError: Cannot read properties of null (reading ‘__styleInstallers’) - URL: undefined -Line: 2 - Column: undefined -Error object: {}
(Debug information, this helps us helping you, you can remove this if you don’t want to share this data, it should not contain any personal or sensitive information)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
Cookies Enabled: true
Screen: 1600 x 900 px - 1dppx
My computer is indeed an older model: HP8440p Elitebook, I guess ca 12 - 15 years old.
Very interesting. Ok, so it sounds like there is an issue with your GPU. Could you verify that you have installed a proper GPU driver and that settings like hardware acceleration are active? You can check some things for Chrome here (just copy this into your browser navbar):
thanks for attaching the report — it shows the cause quite clearly, and it’s not a Kurviger problem.
Under Problems Detected there is this entry:
GPU process was unable to boot: GPU access is disabled due to frequent crashes. Disabled Features: all
Your Chromium’s GPU process crashed repeatedly on startup, so the browser disabled hardware acceleration completely, including WebGL. Since the Kurviger map is rendered with WebGL, it can’t load in this state.
I also asked the AI and got some troubleshooting steps, maybe this helps?
The report also shows the GPU as VENDOR=0x0000, DEVICE=0x0000 with empty GL_VENDOR / GL_RENDERER fields, meaning Chromium couldn’t initialize any graphics device at all. This usually points to missing or broken OpenGL (Mesa) drivers on the system, a VM/remote session without 3D acceleration, or an outdated Mesa version that doesn’t get along with the very recent Chromium 151.
What you can try
Test OpenGL outside the browser: run glxinfo -B (package mesa-utils / mesa-demos). If this fails, the graphics driver itself is broken — fix that first, nothing in Chromium will help until then.
Clear the GPU cache: close Chromium completely, then delete ~/.cache/chromium/Default/GPUCache and restart.
Check the setting: make sure “Use hardware acceleration when available” is enabled in Chromium’s settings.
If this is a virtual machine: enable 3D acceleration in the VM settings.
Last resort: start Chromium with --enable-unsafe-swiftshader to force software-rendered WebGL. The map will be slow, but it should work.
Once chrome://gpu shows WebGL as Hardware accelerated, the Kurviger map will work again.
user@machine:~$ glxinfo -B
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics (ILK) (0x46)
Version: 21.3.5
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (ILK)
OpenGL version string: 2.1 Mesa 21.3.5
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.3.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
I am not an expert, but it looks OK to me (no line saying “error” or similar).
I did not have a “GPUCache” subdirectory in the ~/.cache/chromium/Default directory
I deleted the whole “chromium” directory - no change
“Use hardware acceleration when available” was enabled
It is not a virtual machine
start Chromium with --enable-unsafe-swiftshader works (as mentioned), but it renders slowly (as mentioned). Nevertheless this great - I can use Kurviger again!
Some more questions though:
Is there a similar setting or cmdline option for Firefox as well?
Kurviger did work on my computer with Firefox perfectly until Thu Aug 27 in the morning. In the evening of that day it did not work anymore. Was there any update done on the Kurviger software / website? (I am sure there was) This might give a clue which API causes the Problems.
I do not want to offend you (rather I am happy that it works again although with restrictions) but “it’s not a Kurviger problem” seems a little easy to me. My setup did work (with Kurviger, too) and still works with https://get.webgl.org/.
For Firefox, the equivalent is: open about:config and set webgl.forbid-software to false, then restart Firefox. If the map still doesn’t load, start Firefox from a terminal with LIBGL_ALWAYS_SOFTWARE=1 firefox — this forces Mesa’s software renderer (llvmpipe), which supports everything the map needs. Please avoid webgl.force-enabled — that would use the old Intel driver directly and is likely what caused the crashes you saw. Software rendering will be noticeably slower than the old map, unfortunately — that’s inherent to running the GPU work on the CPU.
Yes, we updated our map library, which now render maps in your browser, instead of downloading prerendered images. This technique is commonplace in most mapping software nowadays and where actually kind of late to adopt this.
Maybe I misunderstood your reply. so you see the spinning cube even without the special startup parameters for chrome? Then there might be something else on our end. But we do require webgl for the use of Kurviger now and will require webgl2 in a few months. Both technologies are widely available and supported almost all devices nowadays.
so you see the spinning cube even without the special startup parameters for chrome?
What I mean is: running Firefox 154.0.1 with the same setting as I always had and open https://get.webgl.org/ I can see the spinning cube.
Settings / Tabs and Browsing / Performance: “Use recommended performance settings” is enabled.
No cmdline parameters.
I did not use Chromium (or Goolge Chrome), I only installed it in order to test whether the Kurviger web site would work with this when it stopped working with Firefox (which I have been using and intend to continue to use..).
There is no error message; the Firefox window just closes and the crash reporter opens.
I attached a crash report.
It happens often (always?) when (re)loading the map, e.g. when entering a track point or loading a previously saved route. Maybe when drawing the route on the map?
I am sorry to hear that. Unfortunately I am not sure how we can help you with this, if Firefox itself crashes.
I don’t know if this crash is coming from our map library or your hardware / driver, but something seems to be not compatible with each other.
If it worked better with Chrome (or some Chromium) that might be an alternative. Or you could look into your GPU driver, if there is a newer driver available etc. Unfortunately, I don’t see a fix on our end right now as well.
Apparently when Firefox crashes and Chromium does not there is a problem within Firefox. Nevertheless there still might be an uncleanliness in your code you might be interested to fix or make your code more robust against such shortcomings in any browser.
I can live with creating my motorcycle tours with Chromium or on a different computer although this adds inconvenience.
(when trying with Chromium it says WebGL could not be loaded)