A bug developer won't fix


Good luck getting a response.
I’ve basically just been told I should be helping diagnose the issue and not complaining and after asking what they need I’ve heard nothing back.
So my title remains an accurate depiction of the results I’ve seen thus far, as the developer allows people to be condescending to those frustrated by events while continuing to ignore the original issue at hand.


Well, I did give you a suggestion of what to do. i.e. clone the source and add some debugs. Alternatively, as you’re running Windows, I’d pretty sure gdb works in Windows (I’ve only used on Linux):

Run the shotcut executable via gdb and when it barfs you’ll have copious amounts of information to send to the developers.


Just ignore DRM - like his nick suggests, it seems he’s only here to justify his presence and only hurt genuine people.

As for the developer, he genuinely seems to care, but free software being free, he likely can’t justify spending too much time on it or the forum (because he needs to do other things that pay his bills) and so things are bound to be missed.

If multithreading is involved in the crash, then it’s going to be VERY hard to pinpoint the issue, depending on how multithreading is implemented. It needs to be implemented very carefully, and very very sparingly, only for crucial places where it will obviously help, like rendering a video in the background. And the crash may only appear on certain operating systems.

Probably helps to say Windows 10, version 1809. When I saw you wrote “Windows 1809” I thought for sure that was a typo, until I searched it just now to make sure. Perhaps others may have gotten confused too.

If bryanb’s suggestion will give debugging output, that will be very helpful for the developers. It will tell them what parts of the program were involved in the crash and help them reproduce it, and try and fix the problem. It’s the next best thing to do, I think. But it probably requires some technical experience to set up, and will probably require time that you can’t justify unless you want to help the project, which is understandable.


What is needed more than anything else is “steps to reproduce”. And I don’t mean vague general steps. I mean excruciating detail steps that result in a problem. If the steps are provided in an ordered list, that is even better. It is OK if the steps don’t reproduce the problem every time. If I have to follow the steps 10 times to get the error, I can still work with that.

It is impossible for a developer to fix a problem if he can not reproduce the problem on his own computer. When I use Shotcut to edit videos, I don’t experience random crashes. So there are two possible explanations for that:

  1. You are using Shotcut in a way that I don’t use it.
  2. There is something different about your environment that Shotcut has trouble with

Also, there is a great thread here with some good advice for requesting help:


I think what he’s getting at is he can’t reproduce it. For example, I recently switched away from Ubuntu to MX Linux, because every now and again, perhaps a few times per day, some days not at all, the whole computer would freeze and do the repeated sound thing. It was completely random. I could be working on a video. I could be reading a web page. In fact, I could be doing absolutely nothing, filing my nails, listening to music and suddenly it does it again. During which the computer is completely unresponsive. It looks like a hard crash, but each time, if I just leave it for 10 seconds or so, it unlocks and continues as normal. There are no steps to reproduce. I was even considering leaving a camera on a tripod recording over my shoulder and clip together the times it’s crashed, just to prove it’s completely random. But then I found out about MX Linux and haven’t looked back.

If the guy says he’s been experiencing it for years and still doesn’t know what triggers it, then the only choices left is for him to detail exactly the operating system version, and his hardware, also the debugger option you suggested, and also - some personal testing; re-install Windows 10 with minimal programs and see if it still does it, to try and narrow down what might be conflicting with it.