Bug 633610 – Crash in greedyh_scanline_C_planar_y

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 633610 - Crash in greedyh_scanline_C_planar_y


Summary:	Crash in greedyh_scanline_C_planar_y


Status:	RESOLVED INCOMPLETE

Product:	GStreamer
Classification:	Platform
Component:	gst-plugins-good
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-10-31 05:52 UTC by prjstone
Modified:	2011-03-15 14:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.31/2.32

Description prjstone 2010-10-31 05:52:07 UTC

Version: 2.32.0

What were you doing when the application crashed?
Running the "photorec" program from the terminal.
I have modified the system by running  "sudo sysctl vm.swappiness=20" prior to beginning photorec. While photorec was running I reviewed an MPG file recovered by photorec.


Distribution: Ubuntu 10.10 (maverick)
Gnome Release: 2.32.0 2010-09-27 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.35-23-generic-pae #36-Ubuntu SMP Tue Oct 26 18:24:15 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler

Memory status: size: 401436672 vsize: 401436672 resident: 229445632 share: 18747392 rss: 229445632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1288503970 rtime: 185 utime: 160 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xaf067b70 (LWP 6296)]
[New Thread 0xaf8f6b70 (LWP 6292)]
[New Thread 0xb16d8b70 (LWP 6286)]
[New Thread 0xb2200b70 (LWP 6278)]
[New Thread 0xb5c17b70 (LWP 6252)]
0xb76e9424 in __kernel_vsyscall ()

+ Trace 224396

Thread 3 (Thread 0xaf8f6b70 (LWP 6292))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
at /build/buildd/glib2.0-2.26.0/glib/gspawn.c line 392
#3 g_spawn_command_line_sync
at /build/buildd/glib2.0-2.26.0/glib/gspawn.c line 706
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomesegvhandler.so
#5 <signal handler called>
#6 greedyh_scanline_C_planar_y
at tvtime/greedyh.c line 525
#7 deinterlace_frame_di_greedyh_planar_plane
at tvtime/greedyh.c line 842
#8 deinterlace_frame_di_greedyh_planar
at tvtime/greedyh.c line 907
#9 gst_deinterlace_method_deinterlace_frame
at gstdeinterlacemethod.c line 202
#10 gst_deinterlace_chain
at gstdeinterlace.c line 1044
#11 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#12 gst_pad_push_data
at gstpad.c line 4405
#13 gst_base_transform_chain
at gstbasetransform.c line 2190
#14 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#15 gst_pad_push_data
at gstpad.c line 4405
#16 gst_proxy_pad_do_chain
at gstghostpad.c line 163
#17 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#18 gst_pad_push_data
at gstpad.c line 4405
#19 gst_proxy_pad_do_chain
at gstghostpad.c line 163
#20 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#21 gst_pad_push_data
at gstpad.c line 4405
#22 gst_selector_pad_chain
at gstinputselector.c line 647
#23 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#24 gst_pad_push_data
at gstpad.c line 4405
#25 gst_proxy_pad_do_chain
at gstghostpad.c line 163
#26 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#27 gst_pad_push_data
at gstpad.c line 4405
#28 gst_proxy_pad_do_chain
at gstghostpad.c line 163
#29 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#30 gst_pad_push_data
at gstpad.c line 4405
#31 ??
from /usr/lib/gstreamer-0.10/libgstffmpeg.so
#32 ??
from /usr/lib/gstreamer-0.10/libgstffmpeg.so
#33 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#34 gst_pad_push_data
at gstpad.c line 4405
#35 gst_type_find_element_chain
at gsttypefindelement.c line 762
#36 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#37 gst_pad_push_data
at gstpad.c line 4405
#38 gst_proxy_pad_do_chain
at gstghostpad.c line 163
#39 gst_pad_chain_data_unchecked
at gstpad.c line 4176
#40 gst_pad_push_data
at gstpad.c line 4405
#41 gst_base_src_loop
at gstbasesrc.c line 2487
#42 gst_task_func
at gsttask.c line 271
#43 default_func
at gsttaskpool.c line 68
#44 g_thread_pool_thread_proxy
at /build/buildd/glib2.0-2.26.0/glib/gthreadpool.c line 319
#45 g_thread_create_proxy
at /build/buildd/glib2.0-2.26.0/glib/gthread.c line 1897
#46 start_thread
from /lib/libpthread.so.0
#47 clone
from /lib/libc.so.6


	Inferior 1 [process 6249] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Output of custom script "/usr/lib/totem/totem/totem-bugreport.py":
gst-typefind-0.10 version 0.10.30
GStreamer 0.10.30
https://launchpad.net/distros/ubuntu/+source/gstreamer0.10
Listened to a "parsed=(boolean)false" file on 2010-10-30T22:46:11

Comment 1 Philip Withnall 2010-10-31 09:38:56 UTC

Looks like a crash in GStreamer's deinterlacing plugin.

Comment 2 Sebastian Dröge (slomo) 2010-10-31 09:57:14 UTC

Which version of gst-plugins-good (gstreamer0.10-plugins-good in Ubuntu) are you using? Is this reproducible somehow?

Comment 3 prjstone 2010-10-31 20:38:21 UTC

gstreamer0.10-plugins-good: 0.10.25-4ubuntu2

I forgot to mention I was running photorec to recover files from a failed hard drive. As a result of the drive failure there was no hard drive system swap partition at the time.

I'll try reproducing the error later this evening

Comment 4 Fabio Durán Verdugo 2010-12-17 06:58:39 UTC

any news for this report?

Comment 5 Fabio Durán Verdugo 2010-12-17 16:26:51 UTC

this comment is in my private mail

I haven't been able to recreate this error. I reviewed the log files at the time and found two other accounts were open with different programs loaded, though idle at the time. Two of these other user programs were browsers running unknown content. They may have had plugins in use. Unfortunately the users didn't know(understand) my questions. 

Any suggestions?

Peter Stone

Comment 6 Tobias Mueller 2011-03-15 13:52:53 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 7 Tim-Philipp Müller 2011-03-15 14:07:26 UTC

In any case, this shouldn't happen any more these days (and if it's just because the default deinterlacing method was changed to something else).