log files (only) are linked below in hopes that analysis will result in a crashless shotcut.
http://www.mediafire.com/file/riucszfnmbybc2d/2019-06-10_crashlogs.zip/file
video clips referenced are from two different “DVR” hardwares recording @ 640x480
Thanks for trying to help, but these are not crash logs - merely activity logs - and they do not help me fix a bug. Sorry
1 Like
would love to help. please tell me how to produce something usable.
in the fashion of Seinfeld Season 3, Episode 11, “These pretzels are making me thirsty.”
“These crashes are making me crazy.”
seriously though. i crash, but do not know what to submit. i’m forced to save very often. i want to help with “crash reports”, tell me what to do.
One way is to figure out the steps to reproduce and relay them.
I see you are on Linux. Another way is to run Shotcut with the gdb debugger and produce a backtrace when crash. First, you need to work the portable archive, then:
cd Shotcut/Shotcut.app
source source-me
gdb bin/shotcut
(gdb) run
use shotcut and wait for crash
thread apply all bt
copy the history of your terminal
paste it in a bug report
1 Like
system
Closed
September 8, 2019, 2:16pm
6
This topic was automatically closed after 90 days. New replies are no longer allowed.