Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[screensharing] // Google meet screen share is laggy #1848

Open
rohit-burman opened this issue Sep 15, 2024 · 8 comments
Open

[screensharing] // Google meet screen share is laggy #1848

rohit-burman opened this issue Sep 15, 2024 · 8 comments
Labels
bug Something isn't working upstream bug

Comments

@rohit-burman
Copy link

Google meet screen share is laggy

Description

Google meet screen share is laggy on both Firefox and brave. But when i use other service like jitsi meet ( jitsi.org ) it works smoothly.
Also some time it fails to screenshare after accepting the prompt form the browser.

Steps to Reproduce

  1. Join a google meet
  2. start a screen share

Expected Behavior

A smooth almost realtime screen share

Actual Behavior

On starting screen share it was giving very low fps on the viewers side, the problem is not with the network.

Screenshots

On terminal I got the below errors
240915_22h01m54s_screenshot

Environment

  • ArchLinux
  • Linux archlinux 6.10.9-arch1-2 Symlinks #1 SMP PREEMPT_DYNAMIC Tue, 10 Sep 2024 14:37:32 +0000 x86_64 GNU/Linux
  • Hyprland, built from branch at commit 0f594732b063a90d44df8c5d402d658f27471dfe (props: bump version to 0.43.0).
    Date: Sun Sep 8 16:48:21 2024
    Tag: v0.43.0,
  • On The Main Hardware
  • Nvidia 3050 laptop gpu

Code from the terminal

❯ com.brave.Browser
[2:2:0915/220042.366489:ERROR:interface_endpoint_client.cc(722)] Message 1 rejected by interface blink.mojom.WidgetHost
[54:54:0915/220043.086119:ERROR:gles2_cmd_decoder_passthrough.cc(928)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
[2:2:0915/220045.450839:ERROR:interface_endpoint_client.cc(722)] Message 1 rejected by interface blink.mojom.WidgetHost
[54:54:0915/220046.476334:ERROR:gles2_cmd_decoder_passthrough.cc(928)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
[54:54:0915/220054.743416:ERROR:gles2_cmd_decoder_passthrough.cc(928)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
[2:340:0915/220118.121781:ERROR:egl_dmabuf.cc(608)] Failed to record frame: Error creating EGLImage - EGL_BAD_MATCH
[2:340:0915/220118.121809:ERROR:shared_screencast_stream.cc(951)] Dropping DMA-BUF modifier: 72057594037927944 and trying to renegotiate stream parameters
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
[2:347:0915/220124.071349:ERROR:egl_dmabuf.cc(608)] Failed to record frame: Error creating EGLImage - EGL_BAD_MATCH
[2:347:0915/220124.071376:ERROR:shared_screencast_stream.cc(951)] Dropping DMA-BUF modifier: 72057594037927944 and trying to renegotiate stream parameters
[2:347:0915/220124.105092:ERROR:egl_dmabuf.cc(608)] Failed to record frame: Error creating EGLImage - EGL_BAD_MATCH
[2:347:0915/220124.105127:ERROR:shared_screencast_stream.cc(951)] Dropping DMA-BUF modifier: 72057594037927942 and trying to renegotiate stream parameters
[275:145:0915/220124.805306:ERROR:sdp_offer_answer.cc(3860)] Transceiver not found based on m-line index (INVALID_PARAMETER)
[275:145:0915/220258.417771:ERROR:sdp_offer_answer.cc(3860)] Transceiver not found based on m-line index (INVALID_PARAMETER)
[275:145:0915/220259.221047:ERROR:sdp_offer_answer.cc(3860)] Transceiver not found based on m-line index (INVALID_PARAMETER)
[2:2:0915/220259.334280:ERROR:interface_endpoint_client.cc(722)] Message 1 rejected by interface blink.mojom.WidgetHost
[275:145:0915/220302.520239:ERROR:sdp_offer_answer.cc(3860)] Transceiver not found based on m-line index (INVALID_PARAMETER)
^C
[2 preload-host-spawn-strategy] Dropping 0x3f10001086c0 (3) because of connection closed
[2:36:0915/220419.857546:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.      
[2:127:0915/220419.857801:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
[2:43:0915/220419.857878:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
[0915/220419.857884:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

#1560 has the same issue

@rohit-burman rohit-burman added the bug Something isn't working label Sep 15, 2024
@rohit-burman rohit-burman changed the title [Bug]: Short description of the issue Google meet screen share is laggy Sep 15, 2024
@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 15, 2024

Try to also open this one Upstream in the Hyprland Repo.

Try to run resetxdgportal.sh ?

Check if it improves anything. Screen sharing is a bit buggy on Hyprland.

https://wiki.hyprland.org/Useful-Utilities/Screen-Sharing/

This should help

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 16, 2024

@kRHYME7 kRHYME7 changed the title Google meet screen share is laggy [screensharing] // Google meet screen share is laggy Sep 16, 2024
@rohit-burman
Copy link
Author

Try to also open this one Upstream in the Hyprland Repo.

Try to run resetxdgportal.sh ?

Check if it improves anything. Screen sharing is a bit buggy on Hyprland.

https://wiki.hyprland.org/Useful-Utilities/Screen-Sharing/

This should help

I have gone thought these disscusions.Solutions given here discusses about if the screenshare is not woking completely.
But here the screenshare is working smoothly with other services(jitsi) but not working in google meet and is laggy.

@rishav12s
Copy link
Contributor

rishav12s commented Sep 17, 2024

I tried screensharing on this with thorium with wayland enabled and it works smoothly but on meet its lags like hell and is only 1-2 fps at max

https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/

a last resort solution that works for meet is using a virtual camera to screenshare through obs it works and is better than native meet sharing

@KorigamiK
Copy link

Did anyone figure out a fix or a solution?

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Dec 4, 2024

Make sure your screensharing app is on wayland

@rishav12s
Copy link
Contributor

Make sure your screensharing app is on wayland

does meet work on your end ? on my laptop(non nvidia) its still doesnt at all

@KorigamiK
Copy link

Make sure your screensharing app is on wayland

Firefox is running on wayland! Idk how else to describe this, the framerate is literally 2 fps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream bug
Projects
None yet
Development

No branches or pull requests

4 participants