User stay connected to shared activity even when activity is stopped

[llaske]

On recent version of Chrome browser, an user who shared an activity then stopped it, is still connected.

Capture.video.2026-08-06.18.55.25.mp4

This is a big issue since once it happens the connection state of the user is incoherent both on the server and on the client.

The issue concern only web client, it not happens on App (Android, iOS, Windows, MacOS, Linux) or when executed in a browser using file:// syntax.
The issue is only on Chrome - works on Firefox.
The issue is not related to the recent Sugarizer 2.0 version, same issue on Sugarizer 1.9.
The issue occurs not only on local servers but also on try.sugarizer.org and dev.sugarizer.org.

[llaske]

I've spend few hours to understand the issue.
It's related to a new behavior of recent Chrome browser version.
On previous Chrome versions when the web page was reloaded, the web socket connections are automatically closed.
On recent Chrome versions (don't know which one), web sockets connected to the same server attempt to stay open. So during the page refresh the Sugarizer client recreate a connection already live. The Sugarizer server detect the new connection and close the older for this client but do not disconnect shared activities.

I'm testing a fix on Sugarizer Server.

[llaske]

The issue is related to the server part. No fix expected on the app side.
A server issue has been declared here: llaske/sugarizer-server#420
I leave the issue open here until a new server release is deployed.