Bug 2100658

Can it be https://bugzilla.mozilla.org/show_bug.cgi?id=1659054 ?
I.e. please set media.navigator.mediadatadecoder_vpx_enabled to false, restart browser and try again.
If that helps please attach about:support page.
Thanks.

Please also revert media.navigator.mediadatadecoder_vpx_enabled to true and run Firefox on terminal with:

MOZ_LOG="PlatformDecoderModule:5"

env variable, run the meeting and attach the log here (I need only first ~200 lines).

Thanks.

Hi Martin,

Just to be clear, you only need the logs from the run with media.navigator.mediadatadecoder_vpx_enabled set to true?

I think it's one of the changes between firefox-101.0-1.fc36 and firefox-101.0.1-4.fc36 that brought this on.

Now I need to find someone to talk to…

(In reply to Martin Stransky from comment #1)
> Can it be https://bugzilla.mozilla.org/show_bug.cgi?id=1659054 ?

I forgot to say that's exactly what I am seeing.

(In reply to Alexander Ploumistos from comment #3)
> Hi Martin,
> 
> Just to be clear, you only need the logs from the run with
> media.navigator.mediadatadecoder_vpx_enabled set to true?

Yes.

> I think it's one of the changes between firefox-101.0-1.fc36 and
> firefox-101.0.1-4.fc36 that brought this on.

Yes, firefox-101.0.1-4 has enabled VA-API by default.

Please attach your about:support page and output of terminal command

rpm -qa intel\*

Thanks.

Created attachment 1892426 [details]
Firefox about:support information

Created attachment 1892430 [details]
Log file with media.navigator.mediadatadecoder_vpx_enabled set to true

(In reply to Martin Stransky from comment #1)
> Can it be https://bugzilla.mozilla.org/show_bug.cgi?id=1659054 ?
> I.e. please set media.navigator.mediadatadecoder_vpx_enabled to false,
> restart browser and try again.
> If that helps please attach about:support page.

Yes, it does help.

Unlike what the reporter in the upstream bug mentioned about Chrome, my interlocutor is using Firefox on Ubuntu.

Also this:

# rpm -qa | grep -i intel | sort
intel-gmmlib-22.1.3-1.fc36.x86_64
intel-media-driver-22.3.1-1.fc36.2.x86_64
intel-mediasdk-22.3.0-1.fc36.x86_64
libva-intel-driver-2.4.1-8.fc36.x86_64
xorg-x11-drv-intel-2.99.917-52.20200205.fc36.x86_64

Thanks. I have the same hardware and packages but I can't reproduce it - do you see that with all Google Meet sessions?

I will try to contact people with different system configurations and see if something changes.

Now that I think of it, this also happened in sessions where the other person was using Meet on an iPhone.

(In reply to Alexander Ploumistos from comment #11)
> I will try to contact people with different system configurations and see if
> something changes.

Unless you think this is irrelevant.
(sorry for the number of messages, I'm working on something and it has taken all of my attention)

No issues while talking with someone using the Meet app on Android 12.

Thanks, I'll try to reproduce with different video source.

I do see that on my end too but it's very rare and lasts only few seconds.

I observe this issue as well. But I'd say that it somehow depends on the opposite side. Just yesterday, I was on a meeting with two other people, one stream was perfect all the time, the other had the strange degradation as described here. Maybe I can check next time what is their client.

I have similar problem with firefox and video calls since F35, that is solved if I download firefox from their site and avoid the repo version, but I don´t have an Intel Graphics Card mine is a vega 8 of a Ryzen 2500U, should I add my info to this post or is better to start another?

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Guys, do you still see that?
Thanks.

Yup, I had it happen last on Firefox 112.0.2 a couple of days ago.

This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

It's been fixed for a while now, closing.