mirror of
https://github.com/imputnet/helium.git
synced 2026-11-17 18:59:24 +00:00
[Bug]: Google Meet tab crashes (SIGILL on renderer Media thread) seconds after stopping a screen share #2720
Labels
No labels
approved
approved
approved
bad ux
bot:review
bot:size
bug
bug
bug
can't replicate
can't replicate
can't replicate
confirmed
confirmed
confirmed
external
feat
feat
feat
good first issue
good first issue
good first issue
invalid
invalid
invalid
needs more info
needs more info
needs more info
pending
pending
pending
upstream
upstream
upstream
WAI
WAI
WAI
wontfix
wontfix
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
imputnet/helium#2720
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Version
0.18.1.1 (Chromium 154.0.8037.57), official x86_64 AppImage (run through NixOS
appimageTools)Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dircommand line argument and it could not be reproduced thereDescription
The Google Meet tab's renderer crashes (SIGILL on its
Mediathread) about 5 seconds after stopping a screen share on Wayland, which drops me from the call.How to Reproduce?
It isn't deterministic: stopping a screen share the day before, with the same setup, did not crash.
Actual behavior
Timeline from the system journal (local time):
15:14:13Helium releases its "Native desktop capture" screensaver inhibit (the share has stopped).15:14:18The kernel logstraps: Media[…] trap invalid opcode ip:57fe95cf2bc3 sp:73fdb17fd050 error:0 in helium[73fabc3,57fe919e1000+d561000]. The--type=rendererprocess forhttps://meet.google.comdies with SIGILL (ILL_ILLOPN), i.e. an intentional crash at offset0x73fabc3in theheliumbinary, on the renderer thread namedMedia.15:14:19The GPU process also writes a minidump (itsgpu-url-chunkis ablob:https://meet.google.com/…URL, and the stringsgpu.mojom.GpuChannel/null field 1appear in it). The GPU process keeps running, so this looks like a side effect of the renderer dying.15:14:19Meet's Blink wake lock is released, and the call is gone.Expected behavior
Stopping the screen share returns to the normal Meet view and the call continues.
Additional context
screencopy { force_shm = true; max_fps = 30 }(DMA-BUF negotiation for whole-monitor capture fails on this setup, so capture is SHM-only), PipeWire 1.6.80x46a6), Mesa 26.2.3, ANGLE on OpenGL ES--ozone-platform=wayland --enable-features=UsePortalFileDialog --disable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL(video decode/encode is in software)helium://crashesif that helps.could you upload the crash and reply with the uploaded crash id?