There have been previous reports of memory increases on small projects that have been solved by changing the Display Method. What are you using?(Menu item Settings → Display Method)
I am using “DirectX (ANGLE)” on Windows 11, if you have a different setting setting, try that. Another one to try is “OpenGL”.
Thanks! I poked around in Regedit and found a few obvious references to Shotcut - some of which were easy to understand and some were incomprehensible numbers. I’ll look through the link you posted tomorrow.
Thanks! My Display Method defaults to DirectX, which is what I’ve always used historically and never seen any particular problem with. My video card has 8GB of memory and can handle DirectX-12 if need be. I tried switching the Display Method to OpenGL a few days ago with no effect. I don’t have any preview scaling enabled at all
A few days ago I upgraded to the latest 22H2 version of Windows 11 and tried the Pixabay file again. Again, no problems at all. I really don’t know what else to suggest.
I looked at the Shotcut settings in the Windows registry and from the variable description given above, I see that the “appdatadir” is set to the Shotcut working folder which (again from the variable description document) means that all the other variables are being set from the INI file there, not from the registry. Not sure this is correct though, because I don’t see the “savePath” variable set anywhere in the INI file, and Shotcut is remembering it and getting it from somewhere… Anyway, here is my Shotcut.ini file, which I don’t see anything wrong with:
All of the variables listed in the description document seem pretty harmless, as far as telling Shotcut to go nuts or something. Most of them aren’t even set in the INI file at all, and I don’t see any variables that would keep track of running output jobs - something that it does keep track of, but where?
Well, I haven’t really thought of anything else to try… I tried turning off the anti-virus again, after removing Spybot S&D completely - but still the same problem.
The only good news is that I’m getting better at all the weird keystrokes needed to do basic editing with Davinci Resolve (DR), which like OpenShot is able to successfully import and process any input source videos that I have. DR has one unusual rendering setting that tells it not to re-render a clip if it “doesn’t need to” (i.e. the output resolution and frame rate is the same as the input’s I presume) - and that saves a bunch of time to create the output file! I created an edited down 12 minute video in just over 4 minutes, while only using about 15% of the CPU resources, instead of the nearly 1:1 ratio with the video’s length that I can often see. Interesting and useful setting!
Anyway, it seems unlikely that any future version of Shotcut will be able to fix my problem, given that it can’t be duplicated by any of you at all. I know everyone probably thinks my system is weird, broken, or running some odd-ball stuff to make Shotcut behave this way, but everything else I run - even stuff like Cygwin, OBS Studio, more games than I can count, web and ftp servers, VirtualBox, and iSpy universally work perfectly. What ever is going on to make Shotcut fall into a black hole, I still have no clue.
Thanks everyone, for your help and good ideas to diagnose and correct this issue!. I’ll be waiting for a miracle to fix this I guess! -
Hey! Guess what? At first test Shotcut version 22.12 seems to fix my memory leak problem under Windows 11! I see that the update notes for it and last month’s version 22.11 mention some memory leaks, so hopefully that was it!
I ran the small “Colours.mp4” test video file through a re-rendering with a slightly different frame rate with no problems - unlike what I’d been seeing using version 22.10.25 (where it got into a loop consuming memory hand over fist). I’ll try to do some more extensive tests with some bigger files in the next few days and report back if I observe any further issues. I hope not!
Wishing everyone a peaceful and relaxing holiday season!