Joining a call and not closing the tab results in strange audio driver behaviour #388
Labels
T-Defect
Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems
X-Needs-Investigation
For entirely unknown reasons, when either participating or previously participating in a call and leaving the tab open other audio issues start to happen. The ones I've noticed are:
Closing the element-call tab fixes both issues.
It feels like element-call is getting an exclusive lock on the audio output device which prevents other things (like youtube's player and Jitsi's webrtc stuff) from getting a similar playback lock. If this is the case, element-call could probably get a less dramatic lock and still work.
Steps to reproduce:
Device: Windows 10, Chrome
It is unclear if the audio issues would persist across browsers, or if it's localized to the browser that ran Element Call.
The text was updated successfully, but these errors were encountered: