Bug 177297

Summary: [GStreamer] WebKitWebProcess crashed with SIGSEGV in _priv_gst_element_state_changed()
Product: WebKit Reporter: Amr Ibrahim <amribrahim1987>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: bugs-noreply, mcatanzaro, pnormand
Priority: P3 Keywords: Gtk
Version: WebKit Nightly Build   
Hardware: PC   
OS: Linux   
See Also: https://launchpad.net/bugs/1718631
Attachments:
Description Flags
Stacktrace none

Amr Ibrahim
Reported 2017-09-21 04:16:27 PDT
Created attachment 321419 [details] Stacktrace It crashed while I was opening a website of an online course on edx.org. The website has a video and JavaScript elements. Downstream bug: https://bugs.launchpad.net/bugs/1718631 DistroRelease: Ubuntu 16.04 Package: libwebkit2gtk-4.0-37 2.16.6-0ubuntu0.16.04.1 StacktraceTop: _priv_gst_element_state_changed (element=element@entry=0x7fc36c10e0d0, oldstate=oldstate@entry=GST_STATE_PAUSED, newstate=newstate@entry=GST_STATE_READY, pending=pending@entry=GST_STATE_VOID_PENDING) at gstelement.c:2279 gst_element_continue_state (element=element@entry=0x7fc36c10e0d0, ret=ret@entry=GST_STATE_CHANGE_SUCCESS) at gstelement.c:2382 gst_element_change_state (element=element@entry=0x7fc36c10e0d0, transition=<optimized out>) at gstelement.c:2687 gst_element_continue_state (element=element@entry=0x7fc36c10e0d0, ret=ret@entry=GST_STATE_CHANGE_SUCCESS) at gstelement.c:2356 gst_element_change_state (element=element@entry=0x7fc36c10e0d0, transition=transition@entry=GST_STATE_CHANGE_PLAYING_TO_PAUSED) at gstelement.c:2687
Attachments
Stacktrace (19.57 KB, text/plain)
2017-09-21 04:16 PDT, Amr Ibrahim
no flags
Philippe Normand
Comment 1 2018-02-09 05:29:46 PST
Which version of GStreamer are you using? Can you please try with 1.12.4 which is the latest stable release?
Philippe Normand
Comment 2 2018-02-09 05:31:46 PST
1.8.3 it seems. So yeah, please try a recent release.
Philippe Normand
Comment 3 2018-02-19 01:01:53 PST
Please re-open if you manage to try again with gst 1.12.x.
Note You need to log in before you can comment on or make changes to this bug.