After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755035 - GstMssManifest: inconsistent structure set makes system crash
GstMssManifest: inconsistent structure set makes system crash
Status: RESOLVED DUPLICATE of bug 755033
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.5.90
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-15 07:20 UTC by WeiChungChang
Modified: 2015-09-15 07:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description WeiChungChang 2015-09-15 07:20:22 UTC
I met a system crash when I use smoothstreaming for streaming.

The crash log is as below:

 
0xb5d2cd7e in g_str_hash () from /mtd_apexe/board/lib/gstreamer/libglib-2.0.so.0.4200.2 
0xb5d2b7fa in g_hash_table_lookup_node () from /mtd_apexe/board/lib/gstreamer/libglib-2.0.so.0.4200.2

After doing trace, I found the potential root cause and had fixed it.

The root cause of my platform comes from following line within function =
static GstCaps *
_gst_mss_stream_audio_caps_from_qualitylevel_xml (GstMssStreamQuality * q)

Where the structure set actions =

  if (q->bitrate)
    gst_structure_set (structure, "bitrate", G_TYPE_INT, (int) q->bitrate,
        NULL);

may lead to coredump.

Since q->bitrate is in guint64 so a modification of:

  if (q->bitrate)
    gst_structure_set (structure, "bitrate", G_TYPE_INT64, (int) q->bitrate,
        NULL);

resolved this issue here.

Please correct it if it really counts.

Thanks~
Comment 1 Sebastian Dröge (slomo) 2015-09-15 07:25:34 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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