GNOME Bugzilla – Bug 760729
Iceweasel crashes, loading a video
Last modified: 2017-12-19 18:22:10 UTC
Bug ---- Playing a video with Iceweasel, causes Iceweasel to crash. Setup ----- System: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02) x86_64 GNU/Linux Browser: Iceweasel 38.5.0 Graphics card: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] Description ------------ Installing Debian and trying to run a video for example on YouTube with Iceweasel, causes Iceweasel to crash. The cause of this, is the "gstreamer1.0-vaapi" package. Removing it, solves it. So something is broken in that package. Best regards.
Thanks for the bug report. Do you also get crashes with Totem media player, for example? Could you provide a stack trace of the crash made with gdb? (thread apply all bt) Since Firefox/Iceweasel have removed their GStreamer backend, there's probably limited interest to debug this further unless it also happens in other applications.
Totem media player is also not able to play a video. Totem won't crash, but is not able to play the video. Trying to play a video with totem: ----------------------------------- libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so libva info: Found init function __vaDriverInit_0_33 libva info: va_openDriver() returns 0 ** (totem:5499): CRITICAL **: gst_vaapi_mini_object_unref: assertion 'object != NULL' failed ** (totem:5499): CRITICAL **: gst_vaapi_mini_object_unref: assertion 'object != NULL' failed ** (totem:5499): CRITICAL **: gst_vaapi_mini_object_unref: assertion 'object != NULL' failed ** (totem:5499): CRITICAL **: gst_vaapi_mini_object_unref: assertion 'object != NULL' failed ** (totem:5499): CRITICAL **: gst_vaapi_mini_object_unref: assertion 'object != NULL' failed Trying to play a video with Iceweasel: --------------------------------------- (process:5534): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Those error messages, are just out of the terminal.
As you say the problem disappears when removing the vaapi plugin, this is most likely a bug in there (or in the fglrx backend of vaapi). Reassigning it to gstreamer-vaapi. We already heard of more reports like this together with Firefox/iceweasel in the past. To help debugging this, can you set G_DEBUG=fatal_warnings in the environment and get a backtrace with gdb of the first assertion? A debug log with GST_DEBUG=2,*vaapi*:6 might also help.
Yes, as slomo said, please attach a debug log and a backtrace, if it is possible.
Created attachment 319278 [details] backtrace I dont know what "A debug log with GST_DEBUG=2,*vaapi*:6 might also help." means, but I attached the backtrace. As you can see in the file I set G_DEBUG=fatal_warnings and started debugging it with: LC_ALL=C MOZILLA_DISABLE_PLUGINS=1 G_DEBUG=fatal_warnings gdb --args iceweasel -safe-mode I hope it helps. If I can do more for you, just tell me. Best regards.
The backtrace should be with $ MOZILLA_DISABLE_PLUGINS=1 G_DEBUG=fatal-warnings gdb --args iceweasel -safe-mode Notice that it ought be fatal-warnings, not fatal_warnings. For the the debug log is more or less the same: $ MOZILLA_DISABLE_PLUGINS=1 GST_DEBUG="2,*vaapi*:6" iceweasel -safe-mode
Created attachment 319289 [details] Backtrace 2 Would have expected a more detailed (longer) output - but okay, hehe. Hope I did it the right way! - Am I not able to attach two files in one submit?
Created attachment 319290 [details] Debug log
Comment on attachment 319289 [details] Backtrace 2 >(process:8612): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Don't think this one is related to GStreamer (or the problem with gst-vaapi).
Two thinks: 1\ as Tim said, the crash seems to be unrelated with gstreamer or gstreamer-vaapi. 2\ the fglrx backend looks to be unable to generate RGBA buffers. gstreamer-vaapi should deal this issue nicer (without gst_vaapi_mini_object_unref messages).
Moving to Product:GStreamer, Component:gstreamer-vaapi
(In reply to anon21073 from comment #0) > The cause of this, is the "gstreamer1.0-vaapi" package. Removing it, solves > it. Does / did this happen under X11 or under Wayland?
(In reply to André Klapper from comment #12) > Does / did this happen under X11 or under Wayland?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!