Desktop website freezes

Hello, on the desktop, the WindsportTracker currently keeps freezing for me in the sessions area. Tested on Windows in Chrome and Firefox.

Best regards,

Thomas

What exactly do you mean by freezing?

Does it mean you can’t click anything anymore, can’t open a session or switch menus? Or just can’t scroll?
Have you already tried clearing the browser cache or opening the page in incognito mode?

I can’t click on anything anymore, can’t switch menus, and can’t open another session. I haven’t tried clearing the cache or incognito mode, but I did try a browser where I hadn’t visited the page before. I’ve now also tested incognito in Chrome. I can neither close the new pop-ups with the editing hints nor click on “continue”:

I tested it on my Windows system and nothing freezes there. To narrow down the cause, I need a few details:

  • Which Windows version do you have, and which versions of Chrome and Firefox?
  • Does it only happen on the session pages, or also in the logbook or on other pages?
  • Does it freeze immediately when you open a session, or only after a while?
  • With all sessions or only with long ones?
  • Is a virus scanner or a (web) firewall installed? Since it occurs in both browsers, that would be a possible cause.
  • Do you have another PC you can test it on?

Sorry for all the questions, but this way I can narrow down the problem the fastest.

Hello Matthias,

thank you for the quick response.

  • I use Windows 11, version 22H2 (Build 22621.4317)
  • it only happens on the session pages
  • and there as soon as I open the page. The page appears to load completely, but does not respond to clicks.
  • with all sessions, I also tested it with a session that only lasted 24 minutes.
  • I have Avira Prime installed as antivirus and firewall. With that, the Windsporttracker worked flawlessly before the current update.
  • On a second PC, the page actually works. There, Avira is also installed as antivirus and firewall

Best regards
Thomas

The Chrome version was still missing: Version 153.0.8010.53 (Official Build) (64-bit)
Firefox: Version 156.0.1 (64-bit)

In the meantime, I also tested DuckDuckGo and Edge and cleared my Chrome cache again. There, and after clearing the Chrome cache, I got one step further each time and was able, for example, to open the share preview. After that, the page froze again. On the second device, everything runs smoothly.

PS: I have quite a lot of sessions in the windsport tracker (877 sessions, 1312 hours). Could it possibly be related to that?

It’s not due to the number or length of sessions.
I suspect a combination of Avira and/or graphics drivers.

Could you please perform the following steps and send me the results (support@sunbits.de) (or the report is sufficient, answer the rest here)?

  1. Open Chrome. Do not yet call up a session in WindsportTracker.
  2. Enter chrome://gpu in the address bar and press Enter.
  3. Click on Download Report at the top of the page. Send me the file.
  4. Open this page: Display a map - MapLibre GL JS
  5. Wait about 10 seconds. Does a map appear, or does Chrome freeze as it does with WindsportTracker?
  6. Open Avira and turn off Web Protection and Browser Protection.
  7. Completely close Chrome, including via the Chrome icon in the lower right corner of the taskbar if it’s still running there. Then restart Chrome.
  8. Open a session in WindsportTracker. Does the session work, or does it freeze again?
  9. Turn Web Protection and Browser Protection back on in Avira.
  1. and 2. I have executed and
  2. sent the report to the support email address.
  3. and 5. Card appears, Chrome does not freeze.
  4. Web protection switched off. There is no separate browser protection option:

  1. and 8. executed. Session still freezes.
  2. Web protection switched back on

Best regards

Thomas

Thanks for the info.

I made a change. Can you check if it works now? Preferably in an incognito window, so that no cache is definitely used.

Unfortunately, unchanged. Tested in Incognito window in Chrome as well as in Edge with previously cleared cache.

Topic resolved, as already exchanged via email. Many thanks for the excellent support and assistance in solving the problem!