Description of problem: Whenever opening a page with HTML5 video, Firefox immediately crashes. Version-Release number of selected component (if applicable): firefox-30.0-4.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1.Visit any page with HTML5 video, e.g., http://camendesign.com/code/video_for_everybody/test.html Actual results: Firefox immediately crashes. Expected results: Firefox should not crash, and show the video. Additional info: - This was not happening until the last update of the firefox package on Fedora 20 in `updates` repository. - Flash videos are working properly. - From lspci: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] (prog-if 00 [VGA controller]) (Kernel modules: radeon)
Can you please attach a backtrace of the crash? See: http://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_crash There's also some troubleshooting tips: https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Standard_troubleshooting_steps
I tried to follow the instructions, but I can’t get Firefox started with gdb. I get: Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace … Program received signal SIGSEGV, Segmentation fault. 0x00007fffea119008 in ?? () (Also, using -safe-mode and the other tips doesn’t help.)
I see. Firefox sometimes fail under gdb. Please try attach gdb to already running firefox instance: 1) run firefox 2) $gdb --pid=XXXX (where XXXX is a firefox process PID) 3) (gdb) continue and then navigate FF to the HTML5 video.
Created attachment 910297 [details] Crash report
That seemed to work.
I don't see any crash in the backtrace, it looks like firefox is just stopped. Can you try again? You need to launch firefox after attaching gdb by the "continue" gdb command and then navigate firefox to the html video. You should see the "Program received signal SIGSEGV, Segmentation fault." in gdb which indicates that firefox crashed.
I launched firefox, attached gdb, used the "continue" command, visited a page with HTML5 video, and I did see a SIGSEV in gdb before recording the crash report, although that could be what I was seeing before (when launching firefox from gdb), and not the real crash, because Firefox was indeed stopped, and only after quitting gdb, it immediately crashed. I will try again and send what I get.
Well, I must be doing something wrong. In any case the SIGSEV is: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fadb99ff700 (LWP 15001)] 0x00007fadab1e8a96 in get_default_device_path (display=0x7fadd1f030a0) at gstvaapidisplay_drm.c:73 73 if (strcmp (udev_device_get_subsystem (parent), "pci") != 0) { And the crash report I sent before is what I get when using the `thread apply all bt full` command. If I use the `continue` command again after Firefox stops (and blanks), I make it close, and gdb tells me there is no process to debug, so there is no report.
Ahh, I see. It's a dupe of Bug 1105890. You need to disable gstreamer. *** This bug has been marked as a duplicate of bug 1105890 ***
Ah, OK. Thank you.