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

chromium: illegal instruction crash when trying to screen share on wayland+pipewire system #390975

Open
3 tasks done
thenhnn opened this issue Mar 18, 2025 · 5 comments
Open
3 tasks done
Labels
0.kind: bug Something is broken

Comments

@thenhnn
Copy link
Contributor

thenhnn commented Mar 18, 2025

Nixpkgs version

  • Unstable (25.05)

Describe the bug

Trying to screen share on Wayland leads to illegal instruction inside Chromium binary.

Illegal instruction occurs in 0x000000010a131dd5 in webrtc::SharedScreenCastStreamPrivate::StartScreenCastStream(unsigned int, int, unsigned int, unsigned int, bool, webrtc::DesktopCapturer::Callback*) ().

Disassembly:

(gdb) x/i $pc
=> 0x10a131dd5 <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+805>:	ud1    0x2(%eax),%eax
(gdb) disassemble $pc-10, $pc+10
Dump of assembler code from 0x10a131dcb to 0x10a131ddf:
   0x000000010a131dcb <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+795>:	shlb   $0x83,0x48(%rcx,%riz,2)
   0x000000010a131dd0 <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+800>:	js     0x10a131dda <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+810>
   0x000000010a131dd2 <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+802>:	add    %dh,0x67(%rdx,%rbx,2)
   0x000000010a131dd6 <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+806>:	ud1    0x2(%rax),%eax
   0x000000010a131dda <_ZN6webrtc29SharedScreenCastStreamPrivate21StartScreenCastStreamEjijjbPNS_15DesktopCapturer8CallbackE+810>:	movq   $0x0,(%rsp)

Steps to reproduce

  1. chromium --user-data-dir=/tmp/chromium-screen-share-crash 'https://mozilla.github.io/webrtc-landing/gum_test.html'
  2. click share screen
  3. select target using portal ui
  4. expect crash

Expected behaviour

Screen sharing works

Screenshots

No response

Relevant log output

Additional context

System metadata

  • system: "x86_64-linux"
  • host os: Linux 6.12.17-hardened1, NixOS, 25.05 (Warbler), 25.05.20250314.bd9298a
  • multi-user?: no
  • sandbox: yes
  • version: nix-env (Lix, like Nix) 2.93.0-dev-pre20250316-29732f1

Notify maintainers

@networkException @emilylange


Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

Is this issue important to you?

Add a 👍 reaction to issues you find important.

@thenhnn thenhnn added the 0.kind: bug Something is broken label Mar 18, 2025
@s0me1newithhand7s
Copy link
Contributor

s0me1newithhand7s commented Mar 18, 2025

reproducible; on both chromuim and ungoogled-chromuim, but not on google-chrome;

@eclairevoyant
Copy link
Contributor

Which compositor? "Wayland" is too vague.

@thenhnn
Copy link
Contributor Author

thenhnn commented Mar 19, 2025

Which compositor? "Wayland" is too vague.

I think, it doesn't matter as the issue is in chromium+pipewire communication. (My guess is that crash happens somewhere there: wayland/shared_screencast_stream.cc)

@s0me1newithhand7s reproduced it on Hyprland, I am using niri.

Screen sharing works on aarch64 with niri. Chromium binary contains invalid machine code only on x86_64.

@s0me1newithhand7s
Copy link
Contributor

@s0me1newithhand7s reproduced it on Hyprland, I am using niri.

hyprland and river, since my laptop and my PC have different WMs; and yes - same problem

@s0me1newithhand7s
Copy link
Contributor

hyprland and river, since my laptop and my PC have different WMs; and yes - same problem

UPD:
sway, swayfx, wayfire - same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

No branches or pull requests

3 participants