Closed Bug 1701809 Opened 4 years ago Closed 4 years ago

Firefox maintains v4l device files open after end of video session

Categories

(Core :: WebRTC: Audio/Video, defect, P2)

Firefox 87
All
Linux
defect

Tracking

()

RESOLVED FIXED
89 Branch
Tracking Status
firefox-esr78 --- wontfix
firefox87 --- wontfix
firefox88 --- wontfix
firefox89 --- fixed

People

(Reporter: cJ-mozilla, Assigned: jib, NeedInfo)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

Actual results:

Open file descriptors for /dev/video* files

This is an annoyance as it prevents drivers from being unloaded.

Expected results:

No open file descriptor

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC: Audio/Video' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core

Marking this P3/S3 because of the annoyance factor, but it is possible there is a more serious problem here. jib?

Severity: -- → S3
Flags: needinfo?(jib)
Priority: -- → P3

Hi Jérôme, thanks for reporting! Would you be able to confirm that it worked in Firefox 77?

I suspect this regressed in bug 1637319 here.

This would mean it broke in Firefox 78 and worked fine in Firefox 77. Unfortunately, I don't have a linux box to check with.

Flags: needinfo?(jib) → needinfo?(cJ-mozilla)
Regressed by: 1637319
Has Regression Range: --- → yes
Assignee: nobody → jib
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P3 → P2
OS: Unspecified → Linux
Hardware: Unspecified → All
Pushed by jbruaroey@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/161b72a0ff01 Close dev/video* driver file descriptors after camera access on linux. r=ng

Hi Jan-Ivar,

You're right, I tested by installing a Firefox 77 from FlatPak hub:
$ flatpak update --user --commit=74e086c686d4ef166eb55bbf0eac72735235072b04711c6d350242a07a9190e7 org.mozilla.firefox # 77
and the problem did not appear.

And then when I installed a 78-ish in the same way:
$ flatpak update --user --commit=dd97c9d605553f7ea44726e9c6beb4ee8cc821ee0df7c235e01a587e93a92c49 org.mozilla.firefox # 78.0.1
and the problem was there.

Flags: needinfo?(cJ-mozilla)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch

FYI I just ran Nightly "89.0a1 (2021-04-02) (64-bit)" and the problem is still there; I'm not familiar enough with Firefox's CI to know if it picked up the commit.

My bad. I confirm the problem is fixed. I had another firefox 87 running...

The patch landed in nightly and beta is affected.
:jib, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.

For more information, please visit auto_nag documentation.

Flags: needinfo?(jib)
Flags: needinfo?(jib)
QA Whiteboard: [qa-89b-p2]

I'm trying to reproduce the issue following the mentioned steps but I'm having trouble getting to the described result. Can you please provide more information? On step 4, do I need to run that command in terminal, could you please be more specific?

Flags: needinfo?(cJ-mozilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: