Meet crashes while in call

Hi,

I have some problems with google meet on firefox the firefox version is Mozilla Firefox 91.9.0esr, but it crashes since I've installed the OS.

System:
  Kernel: 5.18.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=a715693c-beb0-4b88-870f-4885fc8edc10 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: PC Specialist product: Recoil v: Standard
    serial: <superuser required>
  Mobo: Tong Fang model: GK5CP0Z v: Standard serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: N.1.51 date: 04/04/2019
Battery:
  ID-1: BAT0 charge: 38.8 Wh (100.0%) condition: 38.8/46.7 Wh (82.9%)
    volts: 12.9 min: 11.4 model: standard type: Li-ion serial: <filter>
    status: full
CPU:
  Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
    family: 6 model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 52799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630]
    vendor: Tongfang Hongkong driver: i915 v: kernel ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e9b
    class-ID: 0300
  Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile]
    vendor: Tongfang Hongkong driver: nvidia v: 515.48.07
    alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-05) arch: Turing pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: none empty: DP-2,DP-3,HDMI-A-3 bus-ID: 01:00.0
    chip-ID: 10de:1f11 class-ID: 0300
  Device-3: Chicony HD Webcam type: USB driver: uvcvideo bus-ID: 1-13:4
    chip-ID: 04f2:b65a class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x07af built: 2018 res: 1920x1080
    hz: 144 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6")
    diag: 394mm (15.5") ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Tongfang Hongkong
    driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA TU106 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:10f9 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.2-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 16.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Tongfang Hongkong driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  Device-2: Intel Wireless-AC 9260 vendor: Rivet Networks driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 8086:2526 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
    v: 0.8 bus-ID: 1-14:5 chip-ID: 8087:0025 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 232.89 GiB used: 110.63 GiB (47.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDS250G2X0C-00L350 size: 232.89 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 101140WD temp: 37.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 75 GiB size: 75 GiB (100.00%) used: 48.43 GiB (64.6%)
    fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-2: /home raw-size: 157.87 GiB size: 157.87 GiB (100.00%)
    used: 62.2 GiB (39.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /var/log raw-size: 75 GiB size: 75 GiB (100.00%)
    used: 48.43 GiB (64.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /var/tmp raw-size: 75 GiB size: 75 GiB (100.00%)
    used: 48.43 GiB (64.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.48 GiB used: 2.2 MiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.0 C pch: 48.0 C mobo: 48.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 330 Uptime: 16h 11m wakeups: 1 Memory: 15.48 GiB
  used: 4.96 GiB (32.1%) Init: systemd v: 251 tool: systemctl Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1581 lib: 385 Shell: Bash
  v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
  System install date:     2022-04-03
  Last full system update: 2022-06-09
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       <superuser required>
  Snapshots:               Snapper
  Failed units:      

A quick Google search shows quite some info about Google Meet crashing and freezing and some basic solutions that may or may not work. Have you tried some?

3 Likes

Just two gut ideas:

  • Set privacy.resistFingerprinting to false
  • (for screen sharing) disable compositor before
2 Likes

Also consider enabling canvas access.
I now realizes you are not using Firedragon so my post and the first point in above post is irrelevant.
Also what exactly is crashing? Tab? Browser? DE? Entire OS?

1 Like

I would say, use google-chrome / chromium for all Google meets and other Google applications, like drive. It simply works better on Chrome....

Secondly,

I guess the latest version is 101 something. And if your system is fully upgraded, as mentioned in inxi, how can you have Firefox 91? How did you install the Firefox??

3 Likes

It is the ESR (extended support release) version of Firefox and it is normal for ESR to have a lower version.

1 Like

On the web it said that meet and firefox have problems with BTRFS.

the first was already false and it crashes also with no screen sharing

only the tab

I don't remember, but I think I tried on Chromium too, maybe I'll retry.
The version is 91 because is ESR version that should be the safer version, I tried Firefox and gave me problems, so searching on the net they advice to use the ESR version, but nothing changes.

Sources please!!!

I read on the web that the moon was made out of blue cheese, so it must be true. :stuck_out_tongue_winking_eye:

6 Likes

I didn't find again that post, but I tried meet again and it didn't crash, today I had a call and it worked fine, I think that the updates solved the problem. Thank you to all that tried to help me.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.