Bug 1222324 - green screen when trying to watch html5 videos
Summary: green screen when trying to watch html5 videos
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer1-vaapi
Version: 22
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-17 16:02 UTC by Heiko Adams
Modified: 2015-09-16 15:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-03 11:36:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Heiko Adams 2015-05-17 16:02:25 UTC
Description of problem:
After updating gstreamer1-plugins-bad-freeworld to fix crashing firefox on playback html5 videos I only got a green screen instead of the video - sound seems to work fine.

When launching firefox from terminal the following messages appear:

(firefox:20971): GStreamer-CRITICAL **: gst_memory_unmap: assertion 'mem != NULL' failed

(firefox:20971): GStreamer-CRITICAL **: gst_memory_get_sizes: assertion 'mem != NULL' failed

(firefox:20971): GStreamer-CRITICAL **: gst_mini_object_unlock: assertion 'object != NULL' failed

(firefox:20971): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed

** (firefox:20971): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

** (firefox:20971): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

** (firefox:20971): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

Version-Release number of selected component (if applicable):
$ rpm -qa gstreamer1\*
gstreamer1-libav-1.4.3-1.fc22.x86_64
gstreamer1-vaapi-0.5.10-2.fc22.x86_64
gstreamer1-plugins-good-extras-1.4.5-2.fc22.x86_64
gstreamer1-plugins-good-1.4.5-2.fc22.x86_64
gstreamer1-plugins-base-1.4.5-2.fc22.x86_64
gstreamer1-1.4.5-1.fc22.x86_64
gstreamer1-plugins-bad-free-1.4.5-2.fc22.x86_64
gstreamer1-plugins-bad-freeworld-1.4.5-2.fc22.x86_64
gstreamer1-plugins-bad-free-extras-1.4.5-2.fc22.x86_64

How reproducible:
allways

Steps to Reproduce:
1. Open firefox 
2. navigate to youtube
3. watch a video like https://www.youtube.com/watch?v=HsXE5dfwtUw

Actual results:
No video but a green screen are shown

Expected results:
The video should be played as expected

Additional info:

Comment 1 Heiko Adams 2015-05-18 09:53:25 UTC
Okay, it seems gstreamer1-vaapi causes this problem

Comment 2 Ting-Wei Lan 2015-07-06 16:58:10 UTC
I think it is the same as this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1126956

It seems it is hardware-related. When I said the problem was fixed (https://bugzilla.redhat.com/show_bug.cgi?id=1126956#c15), I used this CPU and GPU:
Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (Intel Sandybridge Mobile)

After Fedora 22 was released, I found I could reproduce the problem (https://bugzilla.redhat.com/show_bug.cgi?id=1126956#c22) with this CPU and GPU:
Intel(R) Core(TM) i5 CPU 650  @ 3.20GHz (Intel Ironlake Desktop)

It not only causes green screen to show but also crashes the entire desktop. I have to kill Xorg to recover from it.

[ 2678.456526] [drm] stuck on render ring
[ 2678.467846] [drm] GPU HANG: ecode 5:0:0x9ffdffff, in totem [7540], reason: Ring hung, action: reset
[ 2678.476927] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2678.486187] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2678.495086] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2678.504799] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 2678.513814] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2678.703637] drm/i915: Resetting chip after gpu hang
[ 2684.459960] [drm] stuck on render ring
[ 2684.468036] [drm] GPU HANG: ecode 5:0:0x9ffdffff, in gnome-shell [3025], reason: Ring hung, action: reset
[ 2684.733709] drm/i915: Resetting chip after gpu hang
[ 2690.467316] [drm] stuck on render ring
[ 2690.474702] [drm] GPU HANG: ecode 5:0:0x9ffdffff, in gnome-shell [3025], reason: Ring hung, action: reset
[ 2690.484416] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[ 2690.742368] drm/i915: Resetting chip after gpu hang
[ 2696.466755] [drm] stuck on render ring
[ 2696.474865] [drm] GPU HANG: ecode 5:0:0x9ffdffff, in totem [7540], reason: Ring hung, action: reset
[ 2696.728714] drm/i915: Resetting chip after gpu hang
[ 2702.474103] [drm] stuck on render ring
[ 2702.484456] [drm] GPU HANG: ecode 5:0:0x9ffdffff, in totem [7540], reason: Ring hung, action: reset
[ 2702.493696] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[ 2702.739085] drm/i915: Resetting chip after gpu hang

Comment 3 Nicolas Chauvet (kwizart) 2015-08-03 11:36:57 UTC
@Ting-Wei Lan
You should report your gpu crash dump to bugzilla at freedesktop.org
https://01.org/linuxgraphics/documentation/how-report-bugs

I'm closing this issue because I think the originaly reported issue is fixed by now

Comment 4 Ting-Wei Lan 2015-08-18 19:09:25 UTC
It was already reported: https://bugs.freedesktop.org/show_bug.cgi?id=91382

Comment 5 Ting-Wei Lan 2015-09-16 15:00:02 UTC
After applying this patch, there is no GPU crash now:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4e5752e2b78243a71766538f62ca0a80488047a7

But I still see green screen in Firefox and black screen in Epiphany.


Note You need to log in before you can comment on or make changes to this bug.