RESOLVED FIXED 284718
Playing voice messages on WhatsApp freezes the system
https://bugs.webkit.org/show_bug.cgi?id=284718
Summary Playing voice messages on WhatsApp freezes the system
Angelo Schirinzi
Reported 2024-12-15 13:49:58 PST
This is an issue that in the past only caused the browser or web page to freeze, but recently it has ended up causing the entire system to freeze. The peculiarity of this issue is that it occurs if you use the Epiphany rpm (Fedora Workstation) package but not if you use the flatpak version (tested the TP version on GNOME OS). To reproduce it, you just need to be on a Fedora system, have the plugins for all multimedia formats installed (including those available via RPM Fusion) and run WhatsApp from the Epiphany web browser (rpm package).
Attachments
Partial log file 1 (722.97 KB, text/plain)
2024-12-16 13:20 PST, Angelo Schirinzi
no flags
Philippe Normand
Comment 1 2024-12-16 02:43:59 PST
Angelo Schirinzi
Comment 2 2024-12-16 13:19:16 PST
(In reply to Philippe Normand from comment #1) > Can you share logs please? > https://docs.webkit.org/Ports/WebKitGTK%20and%20WPE%20WebKit/Multimedia.html Since the log file produced is 20 GB in size, I am attaching just a piece of it (I believe it corresponds to the first 37 seconds; if so, then it must contain traces of what happened), which I hope contains valuable information.
Angelo Schirinzi
Comment 3 2024-12-16 13:20:37 PST
Created attachment 473577 [details] Partial log file 1
Philippe Normand
Comment 4 2024-12-17 02:54:14 PST
20 GB? How many hours did you leave this on? The file shouldn't be that big. I don't see nothing out of the ordinary in the one shared above. I can't reproduce this issue here, and memory usage remains stable when playing audios. The fact that it happens only in the rpm version suggests some issue that was fixed in flatpak version but not yet in the distro.
Angelo Schirinzi
Comment 5 2024-12-17 03:16:10 PST
(In reply to Philippe Normand from comment #4) > 20 GB? How many hours did you leave this on? The file shouldn't be that big. > > I don't see nothing out of the ordinary in the one shared above. > I can't reproduce this issue here, and memory usage remains stable when > playing audios. > > The fact that it happens only in the rpm version suggests some issue that > was fixed in flatpak version but not yet in the distro. It stayed active until I was able to unlock and shut down the computer. I think about forty minutes in all. I don't see what might not have been updated in the distro since GStreamer is updated to the latest version (as is WebKit). I don't know what else to do... Can you try Fedora in VM (if so, I remind you that I use all the plugins installable with `sudo dnf install Multimedia --allowerasing`, including those of RPM Fusion)? Or suggest me what else to do...
Angelo Schirinzi
Comment 6 2024-12-17 03:37:45 PST
Sorry in F41 it's `sudo dnf group install multimedia --allowerasing`
Michael Catanzaro
Comment 7 2024-12-17 07:27:10 PST
(In reply to Philippe Normand from comment #4) > The fact that it happens only in the rpm version suggests some issue that > was fixed in flatpak version but not yet in the distro. Unless we have some particular reason to believe otherwise, I fear the opposite is more likely. Stable Fedora is generally ahead of stable freedesktop-sdk, the bug could be coming soon to a Flatpak runtime near you. Or there could just be some sort of other behavior difference.
Michael Catanzaro
Comment 8 2024-12-17 07:28:33 PST
(In reply to Michael Catanzaro from comment #7) > Or there could just be some sort of other behavior difference. (Notably, the Epiphany flatpak has a much more limited set of GStreamer plugins available than Fedora + RPM Fusion.)
Angelo Schirinzi
Comment 9 2024-12-18 08:02:54 PST
Since playing Opus audio files on other websites works great, could we assume that the problem is in how WebKit interacts with WhatsApp's media player? Maybe GStreamer has nothing to do with it after all... If that's the case I could edit the title and reconsider the problem from a different point of view...
Radar WebKit Bug Importer
Comment 10 2024-12-22 13:50:14 PST
Angelo Schirinzi
Comment 11 2025-02-12 13:14:30 PST
Today I tried to do some tests and everything was working fine, until I tried to turn up the volume while listening to the voice message and I fell into the usual bug (the system froze). I don't know if this can suggest anything.
Angelo Schirinzi
Comment 12 2025-02-12 13:35:17 PST
Here some pipewire tracks from journalctl (nothing else of relevance): pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) graph xrun not-triggered (3 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) xrun state:0x7fd143598008 pending:8/1 s:14466475642718 a:14466475713175 f:14466475723336 waiting:70457 process:10161 status:triggered pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) graph xrun not-triggered (2 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) xrun state:0x7fd143598008 pending:8/2 s:14474158030047 a:14474158081091 f:14474158091330 waiting:51044 process:10239 status:triggered pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) graph xrun not-triggered (6 suppressed) pw.node: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__Speaker__sink-52) xrun state:0x7fd143598008 pending:8/1 s:14486067763385 a:14486067767554 f:14486067784365 waiting:4169 process:16811 status:triggered
Angelo Schirinzi
Comment 13 2025-02-13 01:45:33 PST
And these: gnome-shell[2466]: Value -9223372036854775808 cannot be safely stored in a JS Number and may be rounded gnome-shell[2466]: Sink callback failure
Angelo Schirinzi
Comment 14 2025-04-12 07:32:58 PDT
On Epiphany 47.4 and WebKitGTK 2.48.1 I no longer reproduce the issue (GStreamer 1.24.11). Probably the new major release of WebKit has unintentionally patched it. Maybe (in the meantime the new version of Pipewire has also shipped). Anyway, since no other user has reported the same issue, I think it can be closed.
Note You need to log in before you can comment on or make changes to this bug.