[jitsi-dev] Using unstable JVB in production environment


#1

Hello everybody,

I noticed a strange behaviour while using Jitsi Meet with Chrome version 58.0.3029.110.
The browser always crashes few seconds after the start of the conference and I have no errors in JVB logs.

What's confusing about this is that Jitsi Meet used to work properly with Chrome 54.0.2840.100 so maybe it's a compatibility-related problem between Jitsi Meet and Chrome.

I tried to upgrade my JVB to newer version and here's the result :
- JVB 879 (stable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 54 : Works fine.
- JVB 950 (unstable) and Chrome 58 : Works fine, but other audio/video problems were detected.

So my question is, is it fine to use JVB 950 (unstable) for a production server? Should I also update Jicofo and the other components?

any help or suggestion would be greatly appreciated!

Best regards
Hamza


#2

Hi,

Just for the Chrome tab crash. I have the same issue, however i think this is a problem with the chrome version. For me it happens when i connect to the conference with two tabs sharing the webcam.

Regards,
Arthur

···

________________________________
De : dev <dev-bounces@jitsi.org> de la part de KHAIT Hamza - SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE ET MESSAGERIE <hamza.khait@i-carre.net>
Envoyé : mercredi 17 mai 2017 11:39
À : dev@jitsi.org
Objet : [jitsi-dev] Using unstable JVB in production environment

Hello everybody,

I noticed a strange behaviour while using Jitsi Meet with Chrome version
58.0.3029.110.
The browser always crashes few seconds after the start of the conference
and I have no errors in JVB logs.

What's confusing about this is that Jitsi Meet used to work properly
with Chrome 54.0.2840.100 so maybe it's a compatibility-related problem
between Jitsi Meet and Chrome.

I tried to upgrade my JVB to newer version and here's the result :
- JVB 879 (stable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 54 : Works fine.
- JVB 950 (unstable) and Chrome 58 : Works fine, but other audio/video
problems were detected.

So my question is, is it fine to use JVB 950 (unstable) for a production
server? Should I also update Jicofo and the other components?

any help or suggestion would be greatly appreciated!

Best regards
Hamza

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev
dev -- Jitsi Developers - Mailing Lists<http://lists.jitsi.org/mailman/listinfo/dev>
lists.jitsi.org
For discussion of technical implementation details, and is where developers meet and discuss issues, code changes, etc. To see the collection of prior postings to the ...


#3

Hi Arthur,

Yes, same for me :frowning: but it works well on https://meet.jit.si/

Any ideas guys ?

Regards,
Hamza

···

Le 17/05/2017 13:30, > Arthur TOUMASSIAN (par Internet, dépôt dev-bounces@jitsi.org) a écrit :

Hi,

Just for the Chrome tab crash. I have the same issue, however i think
this is a problem with the chrome version. For me it happens when i
connect to the conference with two tabs sharing the webcam.
Regards,
Arthur

-------------------------

DE : dev <dev-bounces@jitsi.org> de la part de KHAIT Hamza -
SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE ET MESSAGERIE
<hamza.khait@i-carre.net>
ENVOYÉ : mercredi 17 mai 2017 11:39
À : dev@jitsi.org
OBJET : [jitsi-dev] Using unstable JVB in production environment

Hello everybody,

I noticed a strange behaviour while using Jitsi Meet with Chrome
version
58.0.3029.110.
The browser always crashes few seconds after the start of the
conference
and I have no errors in JVB logs.

What's confusing about this is that Jitsi Meet used to work properly
with Chrome 54.0.2840.100 so maybe it's a compatibility-related
problem
between Jitsi Meet and Chrome.

I tried to upgrade my JVB to newer version and here's the result :
- JVB 879 (stable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 58 : Crash !
- JVB 881 (unstable) and Chrome 54 : Works fine.
- JVB 950 (unstable) and Chrome 58 : Works fine, but other audio/video

problems were detected.

So my question is, is it fine to use JVB 950 (unstable) for a
production
server? Should I also update Jicofo and the other components?

any help or suggestion would be greatly appreciated!

Best regards
Hamza

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

dev -- Jitsi Developers - Mailing Lists [1]
lists.jitsi.org
For discussion of technical implementation details, and is where
developers meet and discuss issues, code changes, etc. To see the
collection of prior postings to the ...

Links:
------
[1] http://lists.jitsi.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Crashes on chrome 58 is a known issue, we had done some updates in
latest jvb, including the one running on meet.jit.si to avoid some of
them. We will soon update meet.jit.si with the latest bridge.
When you update it is recommended updating all the components
jitsi-meet, jicofo and jvb.

Regards
damencho

···

On Wed, May 17, 2017 at 4:39 AM, KHAIT Hamza - SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE ET MESSAGERIE <hamza.khait@i-carre.net> wrote:

So my question is, is it fine to use JVB 950 (unstable) for a production
server? Should I also update Jicofo and the other components?


#5

Hello Damian,

So my question is, is it fine to use JVB 950 (unstable) for a production
server? Should I also update Jicofo and the other components?

Crashes on chrome 58 is a known issue, we had done some updates in
latest jvb, including the one running on meet.jit.si to avoid some of
them. We will soon update meet.jit.si with the latest bridge.
When you update it is recommended updating all the components
jitsi-meet, jicofo and jvb.

Thanks for the response.
When you say the latest JVB version, do you mean the stable or the testing one?

Regards
Hamza


#6

Hello Damian,
do you know when we can get the next stable Jitsi-Meet version fixing Chrome 58 issues ?

Regards,
Damien Fetis.

----- Mail original -----

···

De: "Damian Minkov" <damencho@jitsi.org>
À: "dev" <dev@jitsi.org>
Envoyé: Mercredi 17 Mai 2017 23:29:05
Objet: Re: [jitsi-dev] Using unstable JVB in production environment

On Wed, May 17, 2017 at 4:39 AM, KHAIT Hamza - SG/SPSSI/CPII/DOSE/ET/PNE ANNUAIRE ET MESSAGERIE <hamza.khait@i-carre.net> wrote:

So my question is, is it fine to use JVB 950 (unstable) for a production
server? Should I also update Jicofo and the other components?

Crashes on chrome 58 is a known issue, we had done some updates in
latest jvb, including the one running on meet.jit.si to avoid some of
them. We will soon update meet.jit.si with the latest bridge.
When you update it is recommended updating all the components
jitsi-meet, jicofo and jvb.

Regards
damencho

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


#7

Just to clarify, it’s Chrome the one which has issues. We added a fix in the JVB which mitigates one of them but there are several. Pretty much every WebRTC application out there using simulcast and statistics is affected.

The WebRTC team at Google has been working on a fix and Chrome Canary (60 at this point) seems to work fine. An update to 58 which fixes these issues is also expected, but they haven’t provided an update on that.

So, at this stage, all we can do is wait until Chrome is fixed, or use Canary in the meantime

Cheers,

···

On May 18, 2017, at 10:28, Damien FETIS <damien.fetis@renater.fr> wrote:

Hello Damian,
do you know when we can get the next stable Jitsi-Meet version fixing Chrome 58 issues ?

--
Saúl


#8

Many thanks for the clarifications. Let's wait for Google to fix it then :slight_smile:

Best regards
Hamza KHAIT

···

Le 18/05/2017 14:06, > Saúl Ibarra Corretgé (par Internet, dépôt dev-bounces@jitsi.org) a écrit :

On May 18, 2017, at 10:28, Damien FETIS <damien.fetis@renater.fr> >> wrote:

Hello Damian,
do you know when we can get the next stable Jitsi-Meet version fixing Chrome 58 issues ?

Just to clarify, it’s Chrome the one which has issues. We added a fix
in the JVB which mitigates one of them but there are several. Pretty
much every WebRTC application out there using simulcast and statistics
is affected.

The WebRTC team at Google has been working on a fix and Chrome Canary
(60 at this point) seems to work fine. An update to 58 which fixes
these issues is also expected, but they haven’t provided an update on
that.

So, at this stage, all we can do is wait until Chrome is fixed, or use
Canary in the meantime

Cheers,

--
Saúl

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


#9

Some webcams are not working with canary version!

Logitech c920 HD webcam
Version 60.0.3102.0 (Official Build) canary (64-bit)

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of Saúl Ibarra Corretgé
Sent: Thursday, May 18, 2017 3:06 PM
To: Jitsi Developers <dev@jitsi.org>
Subject: Re: [jitsi-dev] Using unstable JVB in production environment

On May 18, 2017, at 10:28, Damien FETIS <damien.fetis@renater.fr> wrote:

Hello Damian,
do you know when we can get the next stable Jitsi-Meet version fixing Chrome 58 issues ?

Just to clarify, it’s Chrome the one which has issues. We added a fix in the JVB which mitigates one of them but there are several. Pretty much every WebRTC application out there using simulcast and statistics is affected.

The WebRTC team at Google has been working on a fix and Chrome Canary (60 at this point) seems to work fine. An update to 58 which fixes these issues is also expected, but they haven’t provided an update on that.

So, at this stage, all we can do is wait until Chrome is fixed, or use Canary in the meantime

Cheers,

--
Saúl

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