2

Steps to reproduce:

  1. Open WebApp that uses the camera (tested with BigBueButton)
  2. Allow camera access.
  3. Close corresponding tab.
  4. MacOS still reports the camera as being used by Orion. The Led in the notch is still on, and the notification dot in the top right of the menu bar is still on.

It seems to only happen with BigBlueButton (also tested JitsiMeet and "webcamtests.com").
With Safari BBB does work as intended.

Expected behavior:
The camera access is dropped (Led in Notch turns off, notification dot in menu bar goes away) after the tab is closed.

Orion, OS version; hardware type:
Orion Version 0.99.122-beta (WebKit 615.1.11.7)
MacOS Ventura 13.0.1
Macbook Pro16-inch, 2021, M1Max

  • Vlad replied to this.

    NIoSaT Was not able to reproduce on webcamtests.com, as soon as tab was closed camera was shut off. Will need better steps to reproduce.

        Sorry for the confusion, maybe my wording was a bit off.

        For me, the bug is reproducible in BigBlueButton.
        And the bug is not reproducible in webcamtests.com and Jitsi.

        Maybe it is an interaction with BigBlueButton.

        • Vlad replied to this.

          NIoSaT It is not clear what BigBlueButton is nor what are the steps to reproduce it.

              Once again sorry for the confusion, BigBlueButton is a web conferencing software similar to zoom, only completely in browser.

              https://demo.bigbluebutton.org allows for testing, one does need a free account.

              Steps to reproduce:

              1. Login to account
              2. Start meeting
              3. Allow access to microphone
              4. Turn on camera and allow access
              5. Close Tab

              Orion then keeps the camera access even after the tab is closed

              • Vlad replied to this.
                6 days later

                NIoSaT Not able to reproduce on macbook air, led turns off when tab is closed.

                    Vlad Thanks for taking the time and checking it! 🙂

                    I guess it must be something on my end then.
                    If I ever find out what is causing this behaviour, I will post an update.

                        No one is typing