This message was deleted.

They are also getting this:

is this an issue that appeared only recently or has this always been a problem in your application? is it possible for you to update livekit-client to the latest version and test with it? • for the most part you can ignore “silence detected” as a warning, wondering if the silence-check itself is what freezes chrome. Which chrome version does the error manifest on? • “ping timeout triggered” doesn’t sound good. are you using livekit cloud or self hosted? in case of self hosted, which server version?

@polite-kilobyte-67570 I have already upgraded

livekit-client

to 1.9.2

thanks! does this also happen to you on meet.livekit.io or only in your custom app?

I have not tested on http://meet.livekit.io/ with multiple peers and also I am using

client-sdk-js

in vue3/quasar.js app

meet.livekit.io is also using client-sdk-js under the hood. If it was an issue with the client-sdk-js, you should be seeing the same issue there! In case you want to test closer to the original client-sdk-js, you can also try with

yarn sample

in the client-sdk-js repo and try to reproduce the error there.

So it might be issue of wrong configuration in my custom app, correct?

if you cannot reproduce it in one of our sample apps, then it sounds more likely that it’s a bug in your application, yes! If you can provide a MRE, that showcases the issue, I’m happy to take a look whether the issue is in fact on the livekit side!

Okay, thanks for helping and guiding, I will create one sample example to reproduce the example.

I guess the fact that you’re using qasar might be the actual problem. Just from experience with how many things @eager-raincoat-52616 had to patch for react-native to work properly, I guess it’s likely that something doesn’t work quite right with quasar and webrtc. but that’s just a wild guess.

yeah, I will take care of it and we are developing web based app.

thanks! could you enable debug logs for this by calling

setLogLevel('debug')

from livekit-client and post all logs (unfiltered) as a txt file? that helps us debugging the issue.

Sure will do