Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call member count decreases automatically after some time #3005

Open
bblacher opened this issue Feb 13, 2025 · 4 comments
Open

Call member count decreases automatically after some time #3005

bblacher opened this issue Feb 13, 2025 · 4 comments
Assignees
Labels
T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems

Comments

@bblacher
Copy link

Steps to reproduce

  1. Start a new element call / join an existing one from element web/desktop
  2. Stay in the call for a long time (3+ hours)
  3. Watch the call member count go down after some time

Outcome

What did you expect?

The call member count should only go down after someone leaves the call

What happened instead?

The call member count decreased while noone left the call

Operating system

Arch Linux / Windows 11

Browser information

Element Desktop v1.11.92

URL for webapp

call.element.io / call.element.dev

Will you send logs?

No

@bblacher bblacher added the T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems label Feb 13, 2025
@bblacher
Copy link
Author

Something to add here:
When changing to call.element.dev, the members that don't contribute to the call count don't show tiles.
While reading #2972, I noticed that this might be the same issue, if that's the case, please close this one. :)

@bblacher
Copy link
Author

bblacher commented Feb 17, 2025

Update: This happens exactly 4 hours after joining.

  • Alice joins at 9:16 --> Members: 1
  • Bob joins at 9:32 --> Members: 2
  • Alice has been a member of the call for 4 hours at 13:16 --> Members: 1
  • Bob has been a member of the call for 4 hours at 13:32 --> Members: 0

MSC4140 isn't enabled on my server, enabling it doesn't change this behavior.

@robintown
Copy link
Member

4 hours is exactly the duration we set for the expires field of the call membership state events. So I suppose we have a regression here where the membership manager is just not refreshing the state events.

@robintown
Copy link
Member

robintown commented Feb 17, 2025

@toger5 is on that issue with the implementation of the new MatrixRTC membership manager in matrix-js-sdk which is being tracked by #2972

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Defect Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems
Projects
None yet
Development

No branches or pull requests

3 participants