There’s nothing there about the kind of crashes I have, and the reply there just says what I said - there’s no way to get crash reports without going through some weird loops that nobody seems to know how to do or wants to help with.
So I wonder if they ever even get crash reports lol
I know you are asking for a “crash report”. But would you be willing to upload the “application log”? Maybe there is a hint in there that we can work from. It would be better than nothing, I think.
And ALSO, I found a directory full of “shot cut crash dumps”, whatever that might be.
Would that help? (Usually it just stalls, white-outs, then terminates with no message)
I’m at my wits end trying to figure this out, and shotcut is, as I said, crashing about every 5th time I drag something on the timeline.
EDIT: HERE’S A LOG FROM RIGHT AFTER A CRASH (I didn’t restart shotcut, got the log straight away)
That indicates that a null pointer was dereferenced. So that actually is a small clue.
I would suggest this:
Delete all the files in that directory
Cause a fresh crash
upload the shotcut.exe.dmp and shotcut-log.txt files
Nice. From the log, it looks like the last action was a “lift” on the timeline. and they maybe you started playing again and it crashed? I know it can be hard to remember when you are “in the flow” of editing. But if you can, try to remember exactly the steps that led to the crash.
This is a fairly common operation that is working well for me and many other users. There must be something unique about either your computer or your source clips. If your computer is unique to this problem, it would be hard for me to recreate. If your source clips are unique to this problem, we may be able to narrow it down.
As a test, could you find some clips from a completely different source and try to test your common operations? Does it still crash with files from a different source?
If we think the source files might be unique to the problem, maybe you can make a bare minimum project that demonstrates the problem. For example, make a project file that uses on small source clip and then demonstrate an operation that causes the crash. Zip up the small project and share it with me privately using google drive or some other file sharing service.
I can upload this pretty fast with my new internet but I can’t think of anywhere I can upload 50 gigs worth of project files to.
Would sending the crash dumps be of any use?
Also, I have to add that it never used to be like this. This is as of maybe 4-5 versions of shortcut ago. I never even had a crash before that. Same computer, same everything.
I would not like to revert to older versions if this is at all possible to fix
Definitely not in the middle of a large project.
But after that, well, still, hope it can be isolated and fixed.
Thanks for sending the files. The data indicates that a null pointer exception occurred in the Qt6Core library. That is the library Shotcut uses for the user interface. Unfortunately, it does not provide a trace of what function calls lead to the crash. So this is a dead end.
I think your best options are to use an older version that previously worked for you, or breaky your project down into smaller projects and then combined them when you are done.
Well then…
If I find some way to show the logs to the ppl who make QT6 do you think they could fix it?
I mean, is it something in QT6 or something in the implementation that you guys could fix for the next version of shotcut?
Also, do, er, remember at which version of shotcut you switched to the version of QT6 that causes the crash?
The crash is in the QT library, but that does not mean QT caused the crash. Maybe the crash is caused by some way that Shotcut is using QT. I do not think it would be helpful to report the problem to QT.
That is really tight on RAM. This project is likely asking more of your hardware than it is able to do.
This is a very common problem that is unrelated to the problem in this thread. It can be caused by many things. More information about that specific exit code can be found here:
Just to know, is this being looked at in any way for the next release or is it something that you aren’t intending to look at for now?
Not what nazzar wrote, but the original issue.
Because if you’re looking into it I can share more specific information probably on when it happens or not and help test
I will work on an old version but you know, the new features are great too.
There are no actions we can take right now since the developers do not reproduce it. If you want to keep it moving forward, you could download the SDK and follow Dan’s instructions. The crash log from the SDK might provide more clues.