Menu

#121 segfault opening compositor effect

stable-svn
closed
Salsaman
lives-exe (67)
5
2012-09-15
2009-12-28
exvagabond
No

I opened multitrack mode with 2 clips, added a video track to the rear,
then dragged one of the clips onto the audio, then layer 0. I then
selected layer 0 and layer 3. After selecting the entire video
duration, I selected the compositor effect. The following crash occurred.
This seems to be reproducible, as following these steps caused the
crash two times in a row. This code is from the stable branch,
revision r340. Both of the clips had audio and video.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb74bd700 (LWP 12949)]
_weed_leaf_get (plant=0x302f30, key=0x818c011 "pixel_data", idx=0, value=0x0)
at weed-gslice.c:186
186 if (!weed_strcmp((char )leaf->key,(char )key)) return leaf;
(gdb) bt

0 _weed_leaf_get (plant=0x302f30, key=0x818c011 "pixel_data", idx=0,

value=0x0) at weed-gslice.c:186

1 0x0818a747 in weed_plant_has_leaf (plant=0x302f30,

key=0x818c011 "pixel_data") at weed-utils.c:70

2 0x0818b843 in weed_get_voidptr_value (plant=0x302f30,

key=0x818c011 "pixel_data", error=0xbfd61414) at weed-utils.c:183

3 0x08078377 in weed_apply_instance (inst=0x9760718, init_event=0x975e018,

layers=0x992b9f0, opwidth=0, opheight=0, tc=0) at effects-weed.c:1083

4 0x0807addf in weed_apply_effects (layers=0x992b9f0, filter_map=0x975d2a8,

tc=0, opwidth=320, opheight=240, pchains=0x88e3ea0) at effects-weed.c:2014

5 0x0805667d in load_frame_image (frame=0, last_frame=0) at main.c:2905

6 0x080fa591 in process_events (next_event=0x94dabc0, curr_tc=0)

at events.c:2846

7 0x08157212 in mt_show_current_frame (mt=0x96b5840) at multitrack.c:1786

8 0x08160dac in polymorph (mt=0x96b5840, poly=3) at multitrack.c:8247

9 0x0816289e in add_effect_inner (mt=0x96b5840,

num_in_tracks=<value optimized out>, in_tracks=0x9792fd0, 
num_out_tracks=1, out_tracks=0x9792fd0, start_event=0x94dabc0, 
end_event=0x991fd90) at multitrack.c:10582

10 0x0816c9c9 in mt_add_region_effect (menuitem=0x959c0f8,

user_data=0x96b5840) at multitrack.c:10652

11 0xb78fd3d4 in g_cclosure_marshal_VOID__VOID ()

from /usr/lib/libgobject-2.0.so.0

12 0xb78efc4b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

13 0xb7906095 in ?? () from /usr/lib/libgobject-2.0.so.0

14 0xb79077ac in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0

15 0xb7907c26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0

16 0xb7ed2477 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0

17 0xb7dc4f70 in gtk_menu_shell_activate_item ()

from /usr/lib/libgtk-x11-2.0.so.0

18 0xb7dc6b4d in ?? () from /usr/lib/libgtk-x11-2.0.so.0

19 0xb7dbd4fb in ?? () from /usr/lib/libgtk-x11-2.0.so.0

20 0xb7db7036 in ?? () from /usr/lib/libgtk-x11-2.0.so.0

21 0xb78ee3c9 in ?? () from /usr/lib/libgobject-2.0.so.0

22 0xb78efc4b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

23 0xb7905d3d in ?? () from /usr/lib/libgobject-2.0.so.0

24 0xb790762b in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0

25 0xb7907c26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0

26 0xb7ecc33e in ?? () from /usr/lib/libgtk-x11-2.0.so.0

27 0xb7dafb4c in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0

28 0xb7db0ef7 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0

29 0xb7c4750a in ?? () from /usr/lib/libgdk-x11-2.0.so.0

30 0xb776e718 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0

31 0xb7771dc3 in ?? () from /usr/lib/libglib-2.0.so.0

32 0xb77722e2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0

33 0xb7db13a9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0

34 0x08060e68 in main (argc=1, argv=0xbfd62834) at main.c:1829

Discussion

  • exvagabond

    exvagabond - 2009-12-28

    Upon further thinking, I think the problem is this: The compositor effect modifies the higher video layer (layer with the larger index) and places it on the lower video layer (layer with the lower index). In my example the higher layer was blank. So, maybe the software tried to start a compositor effect on a null layer. For someone who knows how to use the software, this situation probably would not happen. However, for someone learning the software, maybe an error should pop up when this happens?

     
  • Salsaman

    Salsaman - 2009-12-29

    Fixed in 1.1.8;

     

Log in to post a comment.