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 466393 - Crash in gst_caps_set_simple with ogg video
Crash in gst_caps_set_simple with ogg video
Status: RESOLVED DUPLICATE of bug 529018
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.x
Other All
: High critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 473032 564451 564452 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-13 22:05 UTC by jabbathewocket
Modified: 2009-04-08 12:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jabbathewocket 2007-08-13 22:05:51 UTC
Version: 2.18.1

What were you doing when the application crashed?
trying to play a damn movie arrg		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 17:33:05 EDT 2007 ppc64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 81829888 vsize: 81829888 resident: 32641024 share: 20955136 rss: 32641024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187049484 rtime: 205 utime: 179 stime: 26 cutime:15 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -138349760 (LWP 2865)]
[New Thread -167119712 (LWP 2871)]
[New Thread -150780768 (LWP 2867)]
(no debugging symbols found)
0xf7e5d324 in poll () from /lib/libc.so.6

Thread 2 (Thread -167119712 (LWP 2871))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gst_structure_set_valist
    from /usr/lib/libgstreamer-0.10.so.0
  • #4 gst_caps_set_simple
    from /usr/lib/libgstreamer-0.10.so.0
  • #5 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #6 g_key_file_get_boolean
    from /usr/lib/libgstreamer-0.10.so.0
  • #7 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #8 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #9 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #10 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #11 ??
    from /usr/lib/gstreamer-0.10/libgstogg.so
  • #12 g_key_file_get_boolean
    from /usr/lib/libgstreamer-0.10.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6


----------- .xsession-errors (9 sec old) ---------------------
gstalsasink.c(621): gst_alsasink_open (): /autoaudiosink0-actual-sink-alsa:
Device 'default' is busy
(totem:2865): GStreamer-CRITICAL **: gst_value_set_fraction: assertion `denominator != 0' failed
(totem:2865): GLib-GObject-WARNING **: gtype.c:3339: type id `0' is invalid
(totem:2865): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
(totem:2865): GLib-GObject-WARNING **: gvalue.c:96: cannot initialize GValue with type `(null)', this type has no GTypeValueTable implementation
(totem:2865): GLib-GObject-WARNING **: gtype.c:3339: type id `0' is invalid
(totem:2865): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
--------------------------------------------------
Comment 1 Philip Withnall 2007-08-14 10:48:32 UTC
Looks like a bug in GStreamer.

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://www.gnome.org/projects/totem/#bugs for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Baptiste Mille-Mathias 2007-09-03 20:13:05 UTC
*** Bug 473032 has been marked as a duplicate of this bug. ***
Comment 3 Baptiste Mille-Mathias 2007-09-03 20:15:22 UTC
Hello,

If one of the reporters could provided a stack trace with debug symbols, it would be really great; look at comment #1 for details.
Comment 4 Tim-Philipp Müller 2007-10-28 13:22:32 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Philip Withnall 2008-12-14 10:55:27 UTC
*** Bug 564451 has been marked as a duplicate of this bug. ***
Comment 6 Philip Withnall 2008-12-14 10:56:24 UTC
Bug #564451 has a much better stacktrace. Looks like an empty GValue's being passed in.
Comment 7 Cosimo Cecchi 2008-12-14 13:41:57 UTC
*** Bug 564452 has been marked as a duplicate of this bug. ***
Comment 8 Tim-Philipp Müller 2009-04-08 12:12:02 UTC
I think this was fixed by this commit:

  2008-04-20  Sebastian Dröge  <slomo@circular-chaos.org>

        * ext/ogg/gstogmparse.c: (gst_ogm_parse_stream_header):
        GST_TYPE_FRACTION contains gints so correctly cast gint64 arguments to
        vaargs functions to gint. Otherwise the fractions will get 0 set
        instead of the correct value on big endian systems. Fixes bug #529018.

According to the stack trace in the other bug it crashes in g_str_hash(), but since we pass constant strings as fields, the only possibility is that we're passing an argument of the wrong width somewhere. And it's not the width/height arguments, because those are gint32 variables which will automatically be promoted to int if sizeof(gint32)<sizeof(int).


Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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