Bug 556850 – [dvdreadsrc] assertion failure: cur_output_size < 1024

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 556850 - [dvdreadsrc] assertion failure: cur_output_size < 1024


Summary:	[dvdreadsrc] assertion failure: cur_output_size < 1024


Status:	RESOLVED OBSOLETE

Product:	GStreamer
Classification:	Platform
Component:	gst-plugins-ugly
Version:	0.10.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	563667 572857 (view as bug list)
Depends on:
Blocks:

Reported:	2008-10-18 16:15 UTC by wsun07
Modified:	2009-07-28 09:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description wsun07 2008-10-18 16:15:50 UTC

Version: 2.22.2

What were you doing when the application crashed?
insert a DVD


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26 #1 SMP PREEMPT Thu Oct 9 23:04:05 CDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 93601792 vsize: 93601792 resident: 35667968 share: 16437248 rss: 35667968 rss_rlim: 4294967295
CPU usage: start_time: 1224346473 rtime: 87 utime: 75 stime: 12 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb683d6d0 (LWP 9711)]
[New Thread 0xb3de4b90 (LWP 9716)]
[New Thread 0xb4a82b90 (LWP 9715)]
0xb7ff9424 in __kernel_vsyscall ()

+ Trace 208350

Thread 2 (Thread 0xb3de4b90 (LWP 9716))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 __kernel_vsyscall
#8 raise
from /lib/i686/cmov/libc.so.6
#9 abort
from /lib/i686/cmov/libc.so.6
#10 IA__g_assertion_message
#11 IA__g_assertion_message_expr
at /tmp/buildd/glib2.0-2.16.6/glib/gtestutils.c line 1229
#12 gst_dvd_read_src_create
at dvdreadsrc.c line 826
#13 gst_push_src_create
at gstpushsrc.c line 117
#14 gst_base_src_get_range
at gstbasesrc.c line 1860
#15 gst_base_src_loop
at gstbasesrc.c line 2100
#16 gst_task_func
at gsttask.c line 192
#17 g_thread_pool_thread_proxy
at /tmp/buildd/glib2.0-2.16.6/glib/gthreadpool.c line 265
#18 g_thread_create_proxy
at /tmp/buildd/glib2.0-2.16.6/glib/gthread.c line 635
#19 start_thread
from /lib/i686/cmov/libpthread.so.0
#20 clone
from /lib/i686/cmov/libc.so.6





----------- .xsession-errors (5680 sec old) ---------------------
 dwFlags:		:0
 dwInitialFrames:		:0
 dwRate:		:25
 dwStart:		:0
 dwSampleSize:		:0
 dwScale:		:1
 dwLength:		:4305
 dwQuality:		:0
 dwSampleSize:		:0
biSize:		:40
biWidth:		:352
biHeight:		:288
biBitCount:		:24
biCompr
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Philip Withnall 2008-10-19 11:58:40 UTC

Looks like a problem in GStreamer.

Comment 2 palfrey 2008-12-08 13:03:37 UTC

*** Bug 563667 has been marked as a duplicate of this bug. ***

Comment 3 Philip Withnall 2009-02-23 16:54:24 UTC

*** Bug 572857 has been marked as a duplicate of this bug. ***

Comment 4 Edward Hervey 2009-03-06 08:39:00 UTC

Do we still keep this open now that we have resindvd ?

Comment 5 Kris Thomsen 2009-07-27 21:25:41 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 6 André Klapper 2009-07-28 09:42:16 UTC

I'd rather call this OBSOLETE as per comment 4. The question in comment 4 was not for the reporter, hence this is not INCOMPLETE.