You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using your demo app: https://record.a.video/
Add stream > Add screencast + rounded webcam
Delete cam stream (using the trash button)
The light of the camera continues being on and shouldn't.
I also tried after removing the stream stop the streams manually from outside:
getTracks().forEach((track) => track.stop());
But it still keeps the camera open.
It is only released when calling destroy() function.
Expected result
In my opinion the stream lifecicle should be managed from outside of the component, so:
When a stream is removed from the component it should completely release all the resources, even before the destroy.
Actual result
Currently the camera light continues being turned on until destroy the component
Additional context
No response
Relevant logs output
No response
The text was updated successfully, but these errors were encountered:
Version
0.2.2
Environment that reproduces the issue
Device: intel laptop
OS: Windows 11
Chrome 111.0.5563.65 (Build oficial) (64 bits)
Is it reproducible in the example application?
Yes
Reproduction steps
Using your demo app: https://record.a.video/
Add stream > Add screencast + rounded webcam
Delete cam stream (using the trash button)
The light of the camera continues being on and shouldn't.
I also tried after removing the stream stop the streams manually from outside:
getTracks().forEach((track) => track.stop());
But it still keeps the camera open.
It is only released when calling destroy() function.
Expected result
In my opinion the stream lifecicle should be managed from outside of the component, so:
When a stream is removed from the component it should completely release all the resources, even before the destroy.
Actual result
Currently the camera light continues being turned on until destroy the component
Additional context
No response
Relevant logs output
No response
The text was updated successfully, but these errors were encountered: