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 506854 - Crash in libgstavi.so (with pitfdll)
Crash in libgstavi.so (with pitfdll)
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other All
: High critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-02 13:51 UTC by Mitchell Cannon
Modified: 2008-04-06 19:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Mitchell Cannon 2008-01-02 13:51:50 UTC
Version: 2.20.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23 #1 SMP Sat Nov 17 01:45:19 MST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 80244736 vsize: 80244736 resident: 27164672 share: 14430208 rss: 27164672 rss_rlim: 4294967295
CPU usage: start_time: 1199281814 rtime: 64 utime: 57 stime: 7 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d656b0 (LWP 11912)]
[New Thread 0xb40e4b90 (LWP 11918)]
[New Thread 0xb491db90 (LWP 11917)]
[New Thread 0xb5cadb90 (LWP 11916)]
[New Thread 0xb6819b90 (LWP 11914)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 4 (Thread 0xb5cadb90 (LWP 11916))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/gstreamer-0.10/libgstavi.so
  • #7 ??
  • #8 ??
  • #9 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #10 ??
    from /usr/lib/gstreamer-0.10/libgstavi.so
  • #11 ??
  • #12 ??
  • #13 ??


----------- .xsession-errors ---------------------
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
DMO dll supports VO Optimizations 0 1
DMO dll might use previous sample when requested
Total Unfree 60 bytes cnt 1 [(nil),0]
DMO dll supports VO Optimizations 0 1
DMO dll might use previous sample when requested
Total Unfree 60 bytes cnt 1 [(nil),0]
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-03 11:11:31 UTC
Looks like a GStreamer bug.

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://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tim-Philipp Müller 2008-01-03 11:20:59 UTC
Please do

 sudo apt-get install libgstreamer0.10-0-dbg gstreamer0.10-plugins-base-dbg gstreamer0.10-plugins-good-dbg gstreamer0.10-plugins-ugly-dbg gstreamer0.10-plugins-bad-dbg

and try to reproduce the crash, to get a strack trace with debugging symbols.

I'd also suggest you uninstall pitfdll (gstreamer0.10-pitfdll or gstreamer0.10-plugins-pitfdll), as it is highly unstable.
Comment 3 Tim-Philipp Müller 2008-04-06 19:48:14 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!