Attaching another set of similar stack traces, from rendering a
different project.

Note that this does work for me in majority of cases. So far I've had two 
segfaulting projects.
Unfortunately their input size is on the order of a gigabyte, so I cannot 
attach them here.
Although if you want to reproduce this, I can make them available somewhere.

** Attachment added: "gdb1.txt"
   
https://bugs.launchpad.net/openshot/+bug/1085727/+attachment/3450330/+files/gdb1.txt

-- 
You received this bug notification because you are a member of OpenShot
Bugs, which is subscribed to OpenShot Video Editor.
https://bugs.launchpad.net/bugs/1085727

Title:
  segfault when rendering

Status in OpenShot Video Editor:
  New

Bug description:
  This is from openshot-render, but openshot also segfaults like this:

  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/bin/python /usr/bin/openshot-render -v -f mp4 -C 
libx264 -R 15 Mb/s -c ac3'.
  Program terminated with signal 11, Segmentation fault.
  #0  mlt_deque_allocate (self=self@entry=0x0) at mlt_deque.c:92

  Stack traces for all threads attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openshot/+bug/1085727/+subscriptions

-- 
Mailing list: https://launchpad.net/~openshot.bugs
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openshot.bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to