Bug 154579 - [GStreamer] WebProcess from WebKitGtk+ 2.11.90 SIGSEVs on gst_uri_downloader_set_uri
Summary: [GStreamer] WebProcess from WebKitGtk+ 2.11.90 SIGSEVs on gst_uri_downloader_...
Status: RESOLVED DUPLICATE of bug 144040
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-23 02:23 PST by Andres Gomez Garcia
Modified: 2016-04-05 00:23 PDT (History)
5 users (show)

See Also:


Attachments
BT from gdb (107.93 KB, text/plain)
2016-02-23 02:23 PST, Andres Gomez Garcia
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Gomez Garcia 2016-02-23 02:23:43 PST
Created attachment 272005 [details]
BT from gdb

I'm using WebKitGtk+ with my own JHBuild setting:
https://github.com/tanty/jhbuild-epiphany/tree/master

Epiphany 3.18.0, WebKit 2.11.90 and GStreamer 1.4.4

I'm running Epiphany with the dconf key:

"process-model" = "shared-secondary-process"

The compilation was done with CMake args:

'-DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DENABLE_MINIBROWSER=ON -DCMAKE_C_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DNDEBUG -DG_DISABLE_CAST_CHECKS"'

---

Visit http://www.rollingstone.com/music/news/taylor-swift-donates-250-000-to-kesha-after-court-ruling-20160222

The WebProcess SIGSEVs
Comment 1 Andres Gomez Garcia 2016-02-23 02:24:31 PST
This is printed in epiphany's output:

(WebKitWebProcess:12206): GStreamer-CRITICAL **:
Trying to dispose element appsrc1, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(WebKitWebProcess:12206): GStreamer-CRITICAL **:
Trying to dispose element webkitwebsrc0, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.

[New Thread 0x7fff660ae700 (LWP 14348)]

(WebKitWebProcess:12206): GStreamer-CRITICAL **: gst_uri_handler_get_uri: assertion 'GST_IS_URI_HANDLER (handler)' failed

(WebKitWebProcess:12206): GStreamer-CRITICAL **: gst_uri_get_protocol: assertion 'uri != NULL' failed
Comment 2 Carlos Garcia Campos 2016-02-23 02:32:21 PST
I think I've seen this in the debug bot
Comment 3 Philippe Normand 2016-02-23 23:53:14 PST
Please update to GStreamer 1.6.3. This is what the bots use now.
Comment 4 Martin Robinson 2016-02-24 07:55:09 PST
(In reply to comment #3)
> Please update to GStreamer 1.6.3. This is what the bots use now.

But certainly WebKitGTK+ shouldn't crash with older versions?
Comment 5 Philippe Normand 2016-02-24 08:10:00 PST
This is one of the many duplicates reported about adaptive streaming issues with GStreamer 1.4.x :(

I think we should not recommend to our users versions below 1.6.x. We don't have the man power to support more than one stable GStreamer version.
Comment 6 Philippe Normand 2016-04-05 00:23:28 PDT

*** This bug has been marked as a duplicate of bug 144040 ***