[jitsi-users] Chrome and Firefox Issues


#1

Hi List,

A few issues we're seeing on our private deployment [running nightly ATM]:

1) Chrome/ium seems to misjudge the available bandwidth.

This has happened for a while (a few stable releases, as well as nightly),
and causes the video quality to alternate between low and high, despite all
participants being connected via gigabit ethernet to the server and having
CPU to spare. iperf says the clients have ~800 mbps between them and the
server.

The bandwidth estimate is always high when using Firefox.

I'm not well versed on how BWE works in Chrome, but this gives some hints:

Is there anything that can be done on the server side to improve BWE in
Chrome?

2) Firefox shows a black/gray screen for video.

I can repro this on beta.meet.jit.si , join two FF clients (I'm using FF
54.0.1 on Linux) . The video or screen share is black/gray. Sometimes
Firefox crashes. The GSM indicator does not indicate P2P.

This may be related to https://github.com/jitsi/jitsi-meet/issues/1754

-David


#2

Hello David,

About the available bandwidth, we’re aware of an issue that is crippling our conferences:

https://bugs.chromium.org/p/webrtc/issues/detail?id=7860

The Chrome devs are preparing a fix, and we’re also working on one, so this is being taken care of.

About the FF issue, maybe Damian or Brian knows more about it. We’ve recently added some code in the client that has broken some things.

Best,
George

···

On Aug 3, 2017, at 3:16 AM, Darren Wilcrest <darrenwilcrest@gmail.com> wrote:

Hi List,

A few issues we're seeing on our private deployment [running nightly ATM]:

1) Chrome/ium seems to misjudge the available bandwidth.

This has happened for a while (a few stable releases, as well as nightly), and causes the video quality to alternate between low and high, despite all participants being connected via gigabit ethernet to the server and having CPU to spare. iperf says the clients have ~800 mbps between them and the server.

The bandwidth estimate is always high when using Firefox.

I'm not well versed on how BWE works in Chrome, but this gives some hints:

http://www.rtcbits.com/2017/01/bandwidth-estimation-in-webrtc-and-new.html

Is there anything that can be done on the server side to improve BWE in Chrome?

2) Firefox shows a black/gray screen for video.

I can repro this on beta.meet.jit.si <http://beta.meet.jit.si/> , join two FF clients (I'm using FF 54.0.1 on Linux) . The video or screen share is black/gray. Sometimes Firefox crashes. The GSM indicator does not indicate P2P.

This may be related to https://github.com/jitsi/jitsi-meet/issues/1754

-David
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Hi Darren,

> Hi List,
>
> A few issues we're seeing on our private deployment [running nightly ATM]:
>
> 1) Chrome/ium seems to misjudge the available bandwidth.
>
> This has happened for a while (a few stable releases, as well as
> nightly), and causes the video quality to alternate between low and
> high, despite all participants being connected via gigabit ethernet to
> the server and having CPU to spare. iperf says the clients have ~800
> mbps between them and the server.
The workaround on our end that George mentioned is now merged[0], and is part of jitsi-videobridge 980. Please let us know if it has fixed the issues that you observe.

Regards,
Boris

[0] https://github.com/jitsi/libjitsi/pull/351

···

On 02/08/2017 20:16, Darren Wilcrest wrote:


#4

I just tried repro'ing the firefox gray screen issue and couldn't (Firefox
54) but this was on mac, so perhaps it's something tied to linux? I don't
have a machine to test that, unfortunately. Do you see any errors in the
console? The local/remote description from about:webrtc could also provide
some helpful information.

-brian

···

On Thu, Aug 3, 2017 at 8:34 AM, George Politis <gp@jitsi.org> wrote:

Hello David,

About the available bandwidth, we’re aware of an issue that is crippling
our conferences:

https://bugs.chromium.org/p/webrtc/issues/detail?id=7860

The Chrome devs are preparing a fix, and we’re also working on one, so
this is being taken care of.

About the FF issue, maybe Damian or Brian knows more about it. We’ve
recently added some code in the client that has broken some things.

Best,
George

On Aug 3, 2017, at 3:16 AM, Darren Wilcrest <darrenwilcrest@gmail.com> > wrote:

Hi List,

A few issues we're seeing on our private deployment [running nightly ATM]:

1) Chrome/ium seems to misjudge the available bandwidth.

This has happened for a while (a few stable releases, as well as nightly),
and causes the video quality to alternate between low and high, despite all
participants being connected via gigabit ethernet to the server and having
CPU to spare. iperf says the clients have ~800 mbps between them and the
server.

The bandwidth estimate is always high when using Firefox.

I'm not well versed on how BWE works in Chrome, but this gives some hints:

http://www.rtcbits.com/2017/01/bandwidth-estimation-in-webrtc-and-new.html

Is there anything that can be done on the server side to improve BWE in
Chrome?

2) Firefox shows a black/gray screen for video.

I can repro this on beta.meet.jit.si , join two FF clients (I'm using FF
54.0.1 on Linux) . The video or screen share is black/gray. Sometimes
Firefox crashes. The GSM indicator does not indicate P2P.

This may be related to https://github.com/jitsi/jitsi-meet/issues/1754

-David
_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

The issues are a bit different with 980, but still present. User 1
estimates bandwidth at ~700/~1500 kbps, and never receives HD video. User 2
estimates bandwidth at ~1500 kbps/~7500 kbps and seems to send and receive
video OK. However during the course of the call both estimates go up and
down, between 2 and 5 GSM bars. Both are Chromium 59 on Linux
(Fedora/Ubuntu).

My black screen then crash on Firefox 54 on Ubuntu 16.04 I can repro pretty
consistently on my local setup -- which sounds like it may be a Firefox
webrtc issue, not Jitsi.

···

On Fri, Aug 4, 2017 at 1:32 PM, Boris Grozev <boris@jitsi.org> wrote:

Hi Darren,

On 02/08/2017 20:16, Darren Wilcrest wrote:
> Hi List,
>
> A few issues we're seeing on our private deployment [running nightly
ATM]:
>
> 1) Chrome/ium seems to misjudge the available bandwidth.
>
> This has happened for a while (a few stable releases, as well as
> nightly), and causes the video quality to alternate between low and
> high, despite all participants being connected via gigabit ethernet to
> the server and having CPU to spare. iperf says the clients have ~800
> mbps between them and the server.
The workaround on our end that George mentioned is now merged[0], and is
part of jitsi-videobridge 980. Please let us know if it has fixed the
issues that you observe.

Regards,
Boris

[0] https://github.com/jitsi/libjitsi/pull/351