Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-daemon
  • Issues
  • #376
Closed
Open
Created Dec 23, 2020 by Andreas Traczyk@atraczykOwner

Conference: participant info takes a few seconds to update when a participant is removed

The body of the video mixer's source-info-update-callback gets queued into the main job queue behind some call destruction tasks and induces incorrect conference participant metadata in the interim.

  • Why is call destruction so long?
  • Dirty fix: use a thread pool?
Edited Dec 23, 2020 by Andreas Traczyk
Assignee
Assign to
Time tracking