Entire Linux system freezes

[Bryce Tham]

Hi all,

I'm a developer for the Webex Meetings Web App (which uses WebRTC). Recently, we've had a customer complaining that their entire Linux system freezes when using our web app on Chrome (as well as Firefox). I'm trying to help them resolve the issue, but I'm not a Linux expert, so I have no idea how to go about figuring out the root cause.

They say it happens on the latest versions of RHEL 7 and 8, on the latest version of Chrome and Firefox. They say it usually happens when there is video in the meeting, but sometimes the system freezes even when there is no video. At one point they said that only X-server freezes, but looks like it has started freezing the entire system again.

Anyone have any idea how to get any useful logs that might tell me the root cause? Hope this is the right place to ask, since it might be a WebRTC issue.

Thanks,

Bryce

[shakeeb nazmus]

Hi Bryce,

You can check CPU usages using top or htop command. If the CPU is high find out which process is taking the CPU.

Then using strace command find out what the process is doing. 

This normally happens when some process is consuming more resources sometimes because of a busy loop( because of bug, should not happen here ).

You can also see the output of dmesg command at that time to get an idea about what the system was doing at the time.

Thanks,

Shakeeb

[Philipp Hancke]

https://bugzilla.mozilla.org/show_bug.cgi?id=1558475 has some information. Happens too often sadly.

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/d0bdee80-b945-4594-a485-68b0d28fd24en%40googlegroups.com.

[guest271314]

The Firefox bug can and does freeze the entire system. Has occurred to me several times across different versions of Firefox and Nightly. The Chrome bug version can also freeze the browser. There is also the issue of memory usage for the UI when getDisplayMedia() is executed https://bugs.chromium.org/p/chromium/issues/detail?id=1074318.

[Bryce Tham]

Thanks for the feedback, y'all. I will forward this information to the customer.

Regarding CPU usage, their machine is pretty powerful, so I don't expect CPU to be the problem. But who knows, I'll ask them to check it out. Thanks!