xstable
commented
8 years ago Even if the Video seems to be broken, flowblade shouldn't crash, but give a notice for this.
Closed xstable closed 8 years ago
xstable
commented
8 years ago Even if the Video seems to be broken, flowblade shouldn't crash, but give a notice for this.
jliljebl
commented
8 years ago Video file is indeed broken, neither Gnome Video or VLC open it.
Flowblade does not crash on my system however, I get the "Can't open non-valid media" dialog just like I should here for broken video.
I'm closing this as invalid since the described behavior is not observed on development system, and the reasons for it occurring on other systems are very likely not related to Flowblade source code.
Celelibi
commented
6 years ago For what it's worth, I get the very same crash with a file flowblade doesn't want to read (althought it should be perfectly valid). And I found the reason why it crash.
The following line should be surrounded by Gdk.thread_enter() and Gdk.thread_leave().
https://github.com/jliljebl/flowblade/blob/71d72ac9c3b23796b33176dc3c66e1b2121c64d5/flowblade-trunk/Flowblade/projectaction.py#L224
Since it's related to thread synchronization, having fewer CPU cores might hide the bug by forcing some actions to be serialized.
If I add a file named : rico_monitorarm.mp4, flowblade crash.
The Video-File could be downloded here: WeTransfer-File
Other Files in the same Directory works well. Here are the output on the cli, if I add the file rico_monitorarm.mp4 :
And here the Full Log, since startup of Floblade: