Page MenuHome

VSE strip modifiers constantly segfaults on a .blend file converted from 2.79 to 2.80x
Closed, ArchivedPublic

Description

In new .blend files created with 2.80x the VSE is not an issue, but in a particular file that I had originally created in Blender 2.79 (then opened+resaved in 2.80.49) the problem exists. Here is a specific list of things that I have noticed causes segfaults:

  • toggling the visibility of a strip modifier
  • adjusting any parameters of a strip modifier

It will not crash literally every time I change a modifier, but there's probably a 50% chance that the next click will crash blender. Whenever blender crashes, it writes an /tmp/intro.crash.txt file. Here is an example of crashing blender by toggling the visibility of a strip modifier (curves, in this case):

# Blender 2.80 (sub 55), Commit date: 2019-04-13 18:58, Hash 14884cda1ff5
bpy.ops.sequencer.meta_toggle()  # Operator
bpy.ops.sequencer.select(extend=False, linked_handle=False, left_right='NONE', linked_time=False)  # Operator
bpy.context.scene.sequence_editor.sequences_all["Adjustment.004"].modifiers["White Balance"].mute = True  # Property

# backtrace
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(BLI_system_backtrace+0x1d) [0x1bcac0d]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender() [0x1160169]
/lib/x86_64-linux-gnu/libc.so.6(+0x37940) [0x7f6564ab0940]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(IMB_anim_open_index+0x1f) [0x1b5e3af]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(IMB_anim_index_get_frame_index+0x8) [0x1b5e418]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender() [0x102db35]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender() [0x19bed4a]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender() [0x19bf5bc]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(BKE_sequencer_give_ibuf+0x48) [0x19bf868]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(sequencer_ibuf_get+0x194) [0x121c1a4]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(sequencer_draw_preview+0x15e) [0x121c32e]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender() [0x1216726]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(ED_region_do_draw+0x851) [0x1468f21]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(wm_draw_update+0x462) [0x1162a12]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(WM_main+0x30) [0x1160b90]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(main+0x311) [0x10c65a1]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f6564a9d09b]
/home/sankey/Downloads/blender-2.80-14884cda1ff5-linux-glibc224-x86_64/blender(_start+0x2a) [0x115ca7a]

I will attach the blend file, but it depends on probably 50 GB of file system assets which I'm not going to attach.

System info:

  • Debian 10 (64 bit)
  • Thinkpad x230

Details

Type
Bug

Event Timeline

Can not reproduce this.

From the backtrace it seems like it crashed when reading data from video file, that would most likely be //footage_scooter\00046.MTS in this case.

Can you try to reproduce this problem with minimum possible assets (should be just file I mentioned), then if possible upload all necessary files to some cloud storage?

Okay, I'll give that a shot within the next few day(s).

Philipp Oeser (lichtwerk) triaged this task as Needs Information from User priority.Apr 15 2019, 9:51 AM
Philipp Oeser (lichtwerk) claimed this task.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.