Jitsi freezing

Hi all.

So we’ve been testing at https://meet.jit.si/ and have experienced freezing of the video streams when we have more than two participants.

From what I can gather, this is related to issues with Firefox. Not necessarily wanting to, or being able to switch all of our users to Chrome, what is the next best way to achieve video conferences without freezing video streams?

I found the jitsi electron app here - https://github.com/jitsi/jitsi-meet-electron/releases/tag/v1.1.1 - but is this something to use? It seems like the last release was a while ago. It seems there are multiple versions of desktop apps, and possibly none are recommended. What are potential issues from using the electron meet app?

If we have to use Chrome, then we might be able to make it work, but any suggestions on this would be greatly appreciated.

Thanks,
Tristan

1 Like

Hi Tristan, did you manage to find a way arounf it or maybe fix it? We’re having the same issue but in Chrome!! Our app doesn’t even run in Firefox… Did a switch to Chrome work for you?

Any advice on this will be much appreciated! :slight_smile:

Hi @Surikat. I did some more research, and basically more work needs to be done to Firefox and possibly Jitsi for complete Firefox compatibility. It seems there is work towards this, and the latest version of Firefox has improvements but I think it’s not quite there yet.

My recommendation if you don’t want to use Chrome is to use the Jitsi electron app. When I first looked it seemed like development had stalled for some time, but it looks like it’s quite actively developed now.

Check it out here - https://github.com/jitsi/jitsi-meet-electron

You can also see the more info about Firefox compatibility here:

https://github.com/jitsi/jitsi-meet/issues/4758

Hope this helps.

Also this link has info on tracking bugs in Firefox related to Jitsi Meet here:

https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&status_whiteboard=jitsi-meet

@creamelectricart Thanks for such quick response! :grinning: We’re actually having this issue in Chrome so I’m not too sure it’s browser specific. Glad that you found a way to lift the issue though, will definitely look into Firefox possibilities! :bowing_woman: