Clearkey plugin crashed
Description:
Playing videos on pw.live produces an error named the clearkey plugin has crashed on native firefox package on Arch Linux.
Additional info:
I tested the same in openSUSE, on the native firefox, I got no errors there.
I also tested the flatpak version of firefox on Arch Linux, it was fine as well.
Screenshot
-
package version(s): 132.0.1-1
-
config and/or log files: https://crash-stats.mozilla.org/report/index/3ca8ddde-5595-4223-ae59-bb6890241112
-
link to upstream bug report, if any:
Steps to reproduce:
- Open firefox
- Login to https://pw.live
- Play any video
Activity
added priority3-normal severity4-low statusunconfirmed labels
assigned to @freswa, @toolybird, and @gromit
Hey, thanks for the report. But it works fine here i.e. cannot repro. Even though you mention it works fine in those other scenarios, there is no actual evidence of an Arch packaging issue here. But yeah, it does appear that Mozilla have recorded a recent handful of similar crashes from Arch systems.
BTW, that error appears all over the web from all sorts of distros over the past few years. Here is a Recent forum thread. It could even be a bad interaction with an extension you have installed. This example works fine for me.
Labeling as a question so the PM sees it.. but I doubt there is much we can do about it.. so we are probably heading for closure resolution as as "cant-reproduce" or "upstream".
BTW, that error appears all over the web from all sorts of distros over the past few years. Here is a Recent forum thread. It could even be a bad interaction with an extension you have installed. This example works fine for me.
This example works fine.
I don't use any extensions except ublock but it is the same without it.
Thanks for the thread post. Ig I should change the browser for a while or use the flatpak.
Labeling as a question so the PM sees it.. but I doubt there is much we can do about it.. so we are probably heading for closure resolution as as "cant-reproduce" or "upstream".
Actually I saw this bug report on bugzilla as well, as well as on fedora forums (although I cannot confirm if it is still there). I reported because it worked in the other ways I explained earlier.
Perhaps it is a ff bug
added scopequestion statusconfirmed labels and removed statusunconfirmed label
assigned to @heftig and unassigned @freswa, @toolybird, and @gromit
https://reference.dashif.org/dash.js/latest/samples/drm/clearkey.html works fine for me.
https://crash-stats.mozilla.org/report/index/3ca8ddde-5595-4223-ae59-bb6890241112
This one? I uploaded before.
...
On November 13, 2024 12:56:24 PM GMT+05:30, "Jan Alexander Steffens (heftig) (@heftig)" gitlab@archlinux.org wrote:
Jan Alexander Steffens (heftig) commented: #12 (comment 222436)
Did you upload any crash reports? Those get linked in about:crashes.
-- Reply to this email directly or view it on GitLab: #12 (comment 222436) You're receiving this email because of your account on gitlab.archlinux.org.
journal of the entire crash happening, if this might help.
Nov 13 19:49:52 archlinux systemd[1]: Started Process Core Dump (PID 25795/UID 0). Nov 13 19:49:52 archlinux systemd-coredump[25796]: [🡕] Process 25776 (MainThread) of user 1000 dumped core. Stack trace of thread 25776: #0 0x0000635476f06780 mozalloc_abort (firefox + 0x97780) #1 0x0000635476f067a1 abort (firefox + 0x977a1) #2 0x000077e1250d3af0 _ZSt21__glibcxx_assert_failPKciS0_S0_ (libstdc++.so.6 + 0xd3af0) #3 0x000077e1215c5a7c n/a (libclearkey.so + 0x6a7c) #4 0x000077e11c0fc80e n/a (libxul.so + 0x5afc80e) #5 0x000077e11c1367ab n/a (libxul.so + 0x5b367ab) #6 0x000077e11c13ba79 n/a (libxul.so + 0x5b3ba79) #7 0x000077e118fb2fed n/a (libxul.so + 0x29b2fed) #8 0x000077e118fb06a9 n/a (libxul.so + 0x29b06a9) #9 0x000077e118fa6525 n/a (libxul.so + 0x29a6525) #10 0x000077e118fadec4 n/a (libxul.so + 0x29adec4) #11 0x000077e118fadc2e n/a (libxul.so + 0x29adc2e) #12 0x000077e118fada6e n/a (libxul.so + 0x29ada6e) #13 0x000077e118fad9ce n/a (libxul.so + 0x29ad9ce) #14 0x000077e118f02622 n/a (libxul.so + 0x2902622) #15 0x0000635476eaae61 n/a (firefox + 0x3be61) #16 0x000077e124e34e08 n/a (libc.so.6 + 0x25e08) #17 0x000077e124e34ecc __libc_start_main (libc.so.6 + 0x25ecc) #18 0x0000635476f05005 _start (firefox + 0x96005) Stack trace of thread 25781: #0 0x000077e124e9fa19 n/a (libc.so.6 + 0x90a19) #1 0x000077e124ea2479 pthread_cond_wait (libc.so.6 + 0x93479) #2 0x0000635476ee615b _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox + 0x7715b) #3 0x000077e118fa62b2 n/a (libxul.so + 0x29a62b2) #4 0x000077e118fa55d1 n/a (libxul.so + 0x29a55d1) #5 0x000077e118fa4f56 n/a (libxul.so + 0x29a4f56) #6 0x000077e1252eb68f n/a (libnspr4.so + 0x2a68f) #7 0x0000635476ec06d3 n/a (firefox + 0x516d3) #8 0x000077e124ea339d n/a (libc.so.6 + 0x9439d) #9 0x000077e124f282a4 __clone (libc.so.6 + 0x1192a4) Stack trace of thread 25780: #0 0x000077e124f261fd syscall (libc.so.6 + 0x1171fd) #1 0x000077e118f0cc92 n/a (libxul.so + 0x290cc92) #2 0x000077e118f07a7f n/a (libxul.so + 0x2907a7f) #3 0x000077e118f0b25b n/a (libxul.so + 0x290b25b) #4 0x0000635476ec06d3 n/a (firefox + 0x516d3) #5 0x000077e124ea339d n/a (libc.so.6 + 0x9439d) #6 0x000077e124f2849c n/a (libc.so.6 + 0x11949c) Stack trace of thread 25779: #0 0x000077e124f1ac5a read (libc.so.6 + 0x10bc5a) #1 0x000077e118f0120a n/a (libxul.so + 0x290120a) #2 0x0000635476ec06d3 n/a (firefox + 0x516d3) #3 0x000077e124ea339d n/a (libc.so.6 + 0x9439d) #4 0x000077e124f2849c n/a (libc.so.6 + 0x11949c) ELF object binary architecture: AMD x86-64 Nov 13 19:49:52 archlinux systemd[1]: systemd-coredump@5-25795-0.service: Deactivated successfully. q^C⏎Some of the testing I did on Arch Linux + distrobox
1.Firefox package from
fedora containeron distrobox- The crash occurred there as well.
2.Firefox package from
opensuse containeron distroboxHere is a screenrecording of the testing done on opensuse container.
btw I know this info will not help, but just putting it here, I was a long time firefox user, but one day after updating firefox (I do not remember the exact date or the version, it was long ago, may be a year or so) it started crashing the website. Since then I am using two browsers. I was a bit busy back then and now that I got some time, I thought to report. Sorry for the late report.
Edited by Riveeks Smooth@heftig I have some info that might help. I have been since then trying different browsers on arch, and I came across a firefox fork named waterfox which is, in its native package, playing the video finely well w/ or w/o DRM plugin. It is available on the AUR. I installed the AUR package.
Edited by Riveeks Smooth
-
As per the comments above:
- the root cause is understood i.e.
-D_GLIBCXX_ASSERTIONS - it also reproduces on Fedora
Therefore: not an Arch packaging issue. Please refer to this comment for why
-D_GLIBCXX_ASSERTIONSis used to identify buggy upstream code.Link to upstream issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1908682
- the root cause is understood i.e.
added resolutionupstream label
