Bug 157853 – crash of some mpg files

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 157853 - crash of some mpg files


Summary:	crash of some mpg files


Status:	RESOLVED DUPLICATE of bug 159321

Product:	GStreamer
Classification:	Platform
Component:	gst-plugins
Version:	git master
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	NONE
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-11-10 14:33 UTC by Sebastien Bacher
Modified:	2005-08-29 15:43 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Sebastien Bacher 2004-11-10 14:33:52 UTC

This bug has been reported here: https://bugzilla.ubuntu.com/3374

totem-gstreamer (0.99.20 or today's jhbuild) crashes while trying to read some
mpg, one example:
http://www.physics.ubc.ca/~gmarsden/downloads/bball.mpg

I get this in the console:

** (totem:31565): WARNING **: don't know how to handle video/mpeg,
systemstream=(boolean)false, mpegversion=(int)1
ERROR (0x80820c8 - 305582:28:54.731894000)     playbasebin(31565)
gstplaybasebin.c(1111):gst_play_base_bin_change_state:<play> There were no
decoders found to handle the stream in file "file:///home/seb128/bball.mpg", you
might need to install the corresponding plugins

** ERROR **: file gstplaybasebin.c: line 1075 (gst_play_base_bin_change_state):
assertion failed: (group)
aborting...

The backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1090043520 (LWP 31565)]
[New Thread 1095875504 (LWP 31566)]
[Thread debugging using libthread_db enabled]
[New Thread 1090043520 (LWP 31565)]
[New Thread 1095875504 (LWP 31566)]
[Thread debugging using libthread_db enabled]
[New Thread 1090043520 (LWP 31565)]
[New Thread 1095875504 (LWP 31566)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 51802

Thread 1 (Thread 1090043520 (LWP 31565))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 741
#3 <signal handler called>
#4 IA__g_logv
#5 IA__g_log
at gmessages.c line 507
#6 IA__g_assert_warning
at gmessages.c line 542
#7 gst_play_base_bin_change_state
at gstplaybasebin.c line 1055
#8 gst_play_bin_change_state
at gstplaybin.c line 741
#9 gst_element_set_state_func
at gstelement.c line 2796
#10 gst_element_set_state
at gstelement.c line 2739
#11 bacon_video_widget_open
at bacon-video-widget-gst.c line 1099
#12 totem_action_set_mrl
at totem.c line 813
#13 on_eos_event
at totem.c line 2600
#14 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#15 IA__g_closure_invoke
at gclosure.c line 437
#16 signal_emit_unlocked_R
at gsignal.c line 2442
#17 IA__g_signal_emit_valist
at gsignal.c line 2201
#18 IA__g_signal_emit
at gsignal.c line 2245
#19 bacon_video_widget_signal_idler
at bacon-video-widget-gst.c line 625
#20 g_idle_dispatch
at gmain.c line 3821
#21 g_main_dispatch
at gmain.c line 1947
#22 IA__g_main_context_dispatch
at gmain.c line 2497
#23 g_main_context_iterate
at gmain.c line 2578
#24 IA__g_main_loop_run
at gmain.c line 2782
#25 IA__gtk_main
at gtkmain.c line 963
#26 main
at totem.c line 3967
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2004-11-10 14:52:27 UTC

Appears to be a unique stack trace, according to the simple-dup-finder.

Comment 2 Ronald Bultje 2004-11-10 15:29:06 UTC

Ack, introduced (apparently) by scheduler changes in the core CVS of yesterday.
-> GStreamer.

Comment 3 Ronald Bultje 2004-11-10 15:51:44 UTC

I removed the assert, it will just give an error now. Don't yet know why it
fails in the first place, though.

Comment 4 Ronald Bultje 2004-11-11 20:53:10 UTC

It doesn't crash right now, but I get no video either. It seems to be a
video-only file, and well, m1v files are currently slightly problematic.

Comment 5 Ronald Bultje 2004-12-03 19:11:48 UTC

This is fixed now.

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