RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1194692 - HTML5 videos stop working after some jumps to position
Summary: HTML5 videos stop working after some jumps to position
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gstreamer1
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.2
Assignee: Wim Taymans
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-20 14:44 UTC by David Jaša
Modified: 2015-11-19 07:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The HTML 5 video implementation of Firefox relies on a bugfix only available in GStreamer versions 1.2 and higher. Consequence: Versions of GStreamer < 1.2 will cause random seeking problems such as deadlocks and hangs. Fix: Upgrade to a GStreamer version >= 1.2 Result: Seeking behaviour in HTML 5 video in Firefox is reliable.
Clone Of:
Environment:
Last Closed: 2015-11-19 07:05:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backtrace (200.88 KB, text/plain)
2015-02-20 14:54 UTC, David Jaša
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:2221 0 normal SHIPPED_LIVE gstreamer1 bug fix and enhancement update 2015-11-19 08:26:07 UTC

Description David Jaša 2015-02-20 14:44:40 UTC
Description of problem:
HTML5 videos stop working after some use

Version-Release number of selected component (if applicable):
firefox-31.4.0-1.el7_0.x86_64
xulrunner-31.4.0-1.el7_0.x86_64

How reproducible:
always

Steps to Reproduce:
1. start clean Firefox profile
2. play html5 video (on sites like http://vimeo.com/ or http://video.aktualne.cz/ )
3. jump to several positions in the video

Actual results:
* html5 videos stop playing (loading): loading graphic shows forever
* no more html5 videos from any web site can be played (no matter the refreshes)
* firefox process keeps being around after window close, must be terminated manually (I'll attach a backtrace)

Expected results:
no such problem appears:
* videos can be played and jumped indefinitely
* something wrong in one page should be resolved with reload, with no interference to other tabs
* firefox process always exits after window close

Additional info:
tested in fresh profile in safe mode with all plugins disabled

Comment 1 David Jaša 2015-02-20 14:54:43 UTC
Created attachment 993935 [details]
backtrace

Comment 2 Martin Stransky 2015-02-20 15:02:13 UTC
It's played by gstreamer on RHEL7.

Comment 3 Wim Taymans 2015-04-06 13:46:11 UTC
It's a deadlock on one of the mozilla critical sections. I'll have a look if I can see where it is locked.

Comment 4 Wim Taymans 2015-04-06 14:48:13 UTC
The mozilla code relies on clearing the audio and video buffer counters when it sees a FLUSH_STOP event on the appsink sinkpad using a probe.

In 1.0, however there was a bug where the probe would not be emitted for FLUSH_STOP which would then cause:

 - mVideoSinkBufferCount and mAudioSinkBufferCountare not cleared
 - DecodeAudioData() blocks the mGstThreadsMonitor
 - DecodeAudioData() tries to pull a sample from the appsink and blocks
 - meanwhile new samples are pushed into appsinks, which causes NewVideoBuffer()
   and NewAudioBuffer to be called.
 - NewVideoBuffer() and NewAudioBuffer try to lock mGstThreadsMonitor and
   deadlock

543b92a856b81b0a07e99fc27dc4aa6de3c0aeb7 that was released in 1.2 should fix it. Since we rebase to 1.4 in RHEL7.2 this issue should be fixed automatically.

Comment 10 errata-xmlrpc 2015-11-19 07:05:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-2221.html


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