Bug 636773 – Segfault/crash on undo/redo after deleting clips

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 636773 - Segfault/crash on undo/redo after deleting clips


Summary:	Segfault/crash on undo/redo after deleting clips


Status:	RESOLVED FIXED

Product:	pitivi
Classification:	Other
Component:	General
Version:	Git
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	0.14
Assigned To:	Pitivi maintainers
QA Contact:	Pitivi maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-12-08 13:39 UTC by Jean-François Fortin Tam
Modified:	2011-05-24 18:58 UTC

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

Attachments
Debug log (557.30 KB, text/x-log) 2010-12-22 01:40 UTC, Jean-Philippe Fleury	Details
Steps to reproduce the bug (719.59 KB, video/ogg) 2010-12-22 01:41 UTC, Jean-Philippe Fleury	Details
The sample file used in the screencast (585.62 KB, video/ogg) 2010-12-22 01:42 UTC, Jean-Philippe Fleury	Details

Description Jean-François Fortin Tam 2010-12-08 13:39:04 UTC

https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/686852

1. Add a video clip to the timeline
2. Select the video clip on the timeline, press Delete to remove it
3. Undo/redo multiple times (some reporters needed only one, I needed 3)

Result:


Program received signal SIGSEGV, Segmentation fault.
0xb668275f in gst_interpolation_control_source_unset (self=0x952a8c0, timestamp=2586000000) at gstinterpolationcontrolsource.c:569
569	gstinterpolationcontrolsource.c: Aucun fichier ou dossier de ce type.
	in gstinterpolationcontrolsource.c
(gdb) bt full

+ Trace 225033

#0 gst_interpolation_control_source_unset
at gstinterpolationcontrolsource.c line 569
#1 gst_controller_unset
at gstcontroller.c line 1149
#2 _wrap_gst_controller_unset
#3 call_function
#4 PyEval_EvalFrameEx
#5 fast_function
#6 call_function
#7 PyEval_EvalFrameEx
#8 fast_function
#9 call_function
#10 PyEval_EvalFrameEx
#11 fast_function
#12 call_function
#13 PyEval_EvalFrameEx
#14 fast_function
#15 call_function
#16 PyEval_EvalFrameEx
#17 fast_function
#18 call_function
#19 PyEval_EvalFrameEx
#20 fast_function
#21 call_function
#22 PyEval_EvalFrameEx
#23 fast_function
#24 call_function
#25 PyEval_EvalFrameEx
#26 fast_function
#27 call_function
#28 PyEval_EvalFrameEx
#29 fast_function
#30 call_function
#31 PyEval_EvalFrameEx
#32 PyEval_EvalCodeEx
#33 function_call
#34 PyObject_Call
#35 instancemethod_call
#36 PyObject_Call
#37 PyEval_CallObjectWithKeywords
#38 PyObject_CallObject
#39 pyg_closure_marshal
at /build/buildd/pygobject-2.21.5/gobject/pygtype.c line 1152
#40 g_closure_invoke
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 766
#41 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3252
#42 g_signal_emit_valist
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 2983
#43 g_signal_emit
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3040
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib/libgtk-x11-2.0.so.0
#47 g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.26.0/gobject/gmarshal.c line 79
#48 g_closure_invoke
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 766
#49 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3252
#50 g_signal_emit_valist
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 2983
#51 g_signal_emit
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3040
#52 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#53 ??
from /usr/lib/libgtk-x11-2.0.so.0
#54 g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.26.0/gobject/gmarshal.c line 79
#55 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 877
#56 g_closure_invoke
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 766
#57 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3182
#58 g_signal_emit_valist
#59 g_signal_emit
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3040
#60 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#61 ??
from /usr/lib/libgtk-x11-2.0.so.0
#62 ??
from /usr/lib/libgtk-x11-2.0.so.0
#63 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 877
#64 g_closure_invoke
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 766
#65 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3290
#66 g_signal_emit_valist
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 2993
#67 g_signal_emit
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3040
#68 ??
from /usr/lib/libgtk-x11-2.0.so.0
#69 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#70 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#71 ??
from /usr/lib/libgdk-x11-2.0.so.0
#72 g_main_dispatch
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2149
#73 g_main_context_dispatch
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2702
#74 g_main_context_iterate
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2780
#75 g_main_loop_run
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2988
#76 _wrap_g_main_loop_run
at /build/buildd/pygobject-2.21.5/glib/pygmainloop.c line 325
#77 call_function
#78 PyEval_EvalFrameEx
#79 fast_function
#80 call_function
#81 PyEval_EvalFrameEx
#82 fast_function
#83 call_function
#84 PyEval_EvalFrameEx
#85 fast_function
#86 call_function
#87 PyEval_EvalFrameEx
#88 PyEval_EvalCodeEx
#89 PyEval_EvalCode
#90 run_mod
#91 PyRun_FileExFlags
#92 PyRun_SimpleFileExFlags
at ../Python/pythonrun.c line 941
#93 Py_Main
at ../Modules/main.c line 577
#94 main
at ../Modules/python.c line 23

(gdb)

Comment 1 Jean-Philippe Fleury 2010-12-22 01:40:04 UTC

Created attachment 176877 [details]
Debug log

I have this bug too. I'll attach 3 files:

1) A debug log obtained with the following command:

$ PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1
Erreur de segmentation
$

2) A screencast showing the steps to reproduce the bug.

3) The sample file used in the screencast.

Comment 2 Jean-Philippe Fleury 2010-12-22 01:41:17 UTC

Created attachment 176878 [details]
Steps to reproduce the bug

Comment 3 Jean-Philippe Fleury 2010-12-22 01:42:27 UTC

Created attachment 176879 [details]
The sample file used in the screencast

Comment 4 Thibault Saunier 2011-05-24 18:58:13 UTC

commit 64dca7f9ec4e536687199498eb9bfd4a08317a06
Author: Thibault Saunier <thibault.saunier@collabora.co.uk>
Date:   Tue May 24 12:42:10 2011 -0400

    track: Do no add start and end keyframe to our controlled keyframe list  in interpollator
    
    Fixes: 636773