I have a sizeable export that is failing right at the very end of the job. I can sit and watch it with Task Manager running so it’s not CPU, GPU or memory related and I don’t think it’s disk space (almost 1TB free). My question is how can I see the log? When the export fails the whole PC crashes and shuts down. Is the log saved somewhere that I can see it when the PC (Windows) is restarted?
Good grief! If the operating system is doing its job, an application should not be able to cause a computer crash. Does it always crash the computer? Or does it sometimes show “failed” in the export panel?
Is it possible that the export was actually successful? After the failure, I suggest that you go find the exported file and see if it works for you.
The export log is saved in a temp directory on your computer. If the computer is crashing, it is probably being cleaned up.
Thanks, Brian, I’ve tried this about three times now with different export profiles (it’s a 7-hour export so I leave it running overnight) and it always crashes. I once was there when it said 99% and 4 minutes to go when it crashed!
(It’s a cloud PC with spec - AMD EPYC 7543P 32-Core Processor 2.80 GHz; 28GB RAM and NVIDIA RTX AQ4500 with 20GB RAM)
The mp4 file looks to be about the right size but when I try to open it, however the player states it’s corrupt.
I thought as much.
I’m thinking I might split the project and try three or four separate exports and then join the resultant .mp4s…
That’s a good idea.
One theory I could offer is that as the export proceeds, the render process (Melt) incrementally takes more and more memory. You seemed confident that the memory is not being consumed. If that is the case, maybe there is one bit of bad memory and as the usage ticks up it eventually stumbles upon a bad section. A way to test that would be to run MemTest86 on the machine to ensure there are no spurious bad memory spots.
How have you solved it?
I also had a complete reboot of my ubuntu linux if the memory was full. I increased the swap file and this solved the problem.
Perhaps you can also increase the swap file in windows. This is much easier than in Linux 
Yes and no. I split the project up into 3 separate exports and then joined the resultant 3 mp4 files outside of Shotcut.
It has happened once more since, and I did the same again - this time, it was smaller, so I just had to split it into two.
I’ll have a look at increasing the swap file, though, for the next big file.
I rent an online virtual PC ( not sure if that is the correct terminology ), and I’m slightly restricted on what I can change, and the storage space is a separate cost… I do it for the CPU and GPU power.
Thanks for your suggestion.
I’m still investigating, but it might be that my issue is not Shotcut related at all!
I’ve discovered on Reddit some other users of the same online PC are experiencing similar problems with inconvenient shutdowns (or crashes, as I thought), and it turns out that Shadow shutdown the PC after periods of inactivity and that they count inactivity as no mouse clicks or keyboard presses so my lengthy video processing wouldn’t count.
So, I’ve now bought myself a mouse jiggler to see if that will stop the shutdowns. Until today, I did not even know a mouse jiggler was a thing, but there are dozens of them on Amazon!
I had a similar issue before, where the export would fail towards the end, and it turned out to be related to file corruption during the export process. While splitting the project, as Brian suggested, is a good workaround, you might also want to check the export settings and try exporting with a different codec to see if that helps.
I’ve also had file corruption problems in the past, but those were usually found at the proxy creation stage. For info, I’ve also always had 100% success in repairing those files with Wondershare’s RepairIT.
1 Like
This topic was automatically closed after 90 days. New replies are no longer allowed.