I am running Shotcut 16.19.01 on OSX 10.11.6. The machine supports GPU processing (using nVidia drivers).
The following is always reproduceable: when working on a project adding a JPEG file makes the application crash. The issue appears also on an empty project as well; clicking “Open file” and selecting any JPEG file, terminates abnormally the application (and the Apple error reporting appears).
I’ve also performed this test using an Arch Linux machine: created a simple project on Shotcut in Arch that contained a JPEG picture. Shotcut on Arch always opens and works fine with this .mlt project. Upon opening the same .mlt file under OSX, Shotcut crashes.
If there is any way that I can get a detailed log file out of the program on OSX, please let me know so that I can post it here and help fixing this error.
might be this pic will help (I also have a crash report, about 800 lines) - I even had those crashes in earlier releases so I deactivated “GPU” - shotcut is still pretty fast
Thank you very much for the suggestion.
Indeed, it was the GPU processing option; I’d never thought of deactivating it after successfully using it for two other projects (with no static pictures).
Just a reminder that GPU processing is still experimental, so one of the first things to do when you’re trying to confirm a bug is to disable it. Thank you @Fossi for resolving this.
In earlier releases I realized that a project saved with GPU-mode could not be opened without GPU-mode but I didn’t examine the XML-data of the project-file for possibilities to switch the project back later.
For me the conclusion is just to ignore GPU-feature as long as it is beta.
Part of Crashreport perhaps usefull for you programmers:
When attempting to load a project saved with GPU processing, but currently turned off, there should be a message saying that the project uses GPU effects. This happens even if you attempt to open the project directly from the file. I’m assuming you get this crash instead of the message.
The crash report says this is in version 16.09.01. If you didn’t receive the message, the crash may have been caused by trying to send it.
Also, sorry for the late reply, I’ve been at a conference the past three days.