16.08.2024, 23:45
Thanks for the ideas! Did investigate them but so far unsuccessfully, will try and test some more.
Very much agree but this was what got me through this very same batch the first time, just resetting and retrying until there was no crash
a glitch in the source:
Was able to move around the frame without issues in the preview. Did some more tests with another source and saw that it crashed three times in exactly the same frame (12114) but also with that, no issues playing through the frame and onwards in Vapoursynth preview window. Before this I also happened to have two concecutive succesful finishes for the same clip (but noticed the debug setting had switched off in app restart.)
heat issues:
I was very hopeful with this one when I saw 100C peak CPU temperatures in HWMonitor (CPU at around 50%). Proceeded to set a --threads 2 for the job which lowered the temps to 70C (60C is my idle) but unfortunately it crashed at the first try, only slightly later at frame 12130.
(I have also made an observation that if I start a job but then move window focus to some other app than Hybrid, the x264 encode subjob runs at a very low speed and CPU usage, and only visiting the Hybrid window will put things into full throttle)
some driver issues:
Potentially possible but I also (accidentially) ran Vapoursynth in OpenCL mode with a wrong device ID (the Intel iGPU instead of Nvidia GPU) and it crashed on some runs and finished succesfully on another run, so maybe not that likely?
overclocking of cpu/gpu/ram:
Not overclocked, pretty new Dell Precision 5680 laptop (Core i9-13900H & RTX 3500).
a bug in a filter:
Cannot comment on this, but no issues seen in previews. But anecdotally, the crash/success -ratio seems much lower with the experimental Hybrid build I'm using now vs. the latest stable one I used (without GPU support) to encode the earlier batch.
some antivirus tool (or the os) interfering:
Added the Hybrid folder and the source/output folder to the AV (Withsecure) exceptions. Will still need to try some more with the AV app disabled totally but the first run after disabling it was a successful one, the second a crash.
running out of ram:
I have 32GB of ram and the maximum utilization I have seen in the Task Manager is 14GB (whole system).
I doubt this is at all helpful but here's a bit longer log file, with a couple of crashes and one successful run (and manual stops where I was investigating the CPU temps): https://wormhole.app/nZWAR#yXxOdg2tR91f9T8c9biwqQ
Perhaps I should try the "Prefer FFmpeg" Decoding setting next if you say that the error means that the decoder is crashing?
(16.08.2024, 14:25)Selur Wrote: "Retry CRASHED jobs X times" that sounds like insanity.
Very much agree but this was what got me through this very same batch the first time, just resetting and retrying until there was no crash
(16.08.2024, 14:25)Selur Wrote: But then the decoder crashes " Helper(1) finished with exitCode: -1073741819 and exitStatus: 1"
-1073741819 indicates an access violation in the helper, so somewhere in the Vapoursynth processing.
This is usually caused by one of these things:
- a glitch in the source => check whether you can navigate in the Vapoursynth Preview around frame 55698.
- heat issues
- memory issues
- some driver issues (unlikely since it worked for 55698 frames)
- overclocking of cpu/gpu/ram (yes, even when every other test seems fine; encoding and intense filtering is really sensitive)
- a bug in a filter (unlikely since it worked for 55698 frames)
- some antivirus tool (or the os) interfering (especially mcafee and nortons live scanning stuff can cause problems)
- runnning out of ram (there isn't always an out-of-memory error is memory gets spars)
a glitch in the source:
Was able to move around the frame without issues in the preview. Did some more tests with another source and saw that it crashed three times in exactly the same frame (12114) but also with that, no issues playing through the frame and onwards in Vapoursynth preview window. Before this I also happened to have two concecutive succesful finishes for the same clip (but noticed the debug setting had switched off in app restart.)
heat issues:
I was very hopeful with this one when I saw 100C peak CPU temperatures in HWMonitor (CPU at around 50%). Proceeded to set a --threads 2 for the job which lowered the temps to 70C (60C is my idle) but unfortunately it crashed at the first try, only slightly later at frame 12130.
(I have also made an observation that if I start a job but then move window focus to some other app than Hybrid, the x264 encode subjob runs at a very low speed and CPU usage, and only visiting the Hybrid window will put things into full throttle)
some driver issues:
Potentially possible but I also (accidentially) ran Vapoursynth in OpenCL mode with a wrong device ID (the Intel iGPU instead of Nvidia GPU) and it crashed on some runs and finished succesfully on another run, so maybe not that likely?
overclocking of cpu/gpu/ram:
Not overclocked, pretty new Dell Precision 5680 laptop (Core i9-13900H & RTX 3500).
a bug in a filter:
Cannot comment on this, but no issues seen in previews. But anecdotally, the crash/success -ratio seems much lower with the experimental Hybrid build I'm using now vs. the latest stable one I used (without GPU support) to encode the earlier batch.
some antivirus tool (or the os) interfering:
Added the Hybrid folder and the source/output folder to the AV (Withsecure) exceptions. Will still need to try some more with the AV app disabled totally but the first run after disabling it was a successful one, the second a crash.
running out of ram:
I have 32GB of ram and the maximum utilization I have seen in the Task Manager is 14GB (whole system).
I doubt this is at all helpful but here's a bit longer log file, with a couple of crashes and one successful run (and manual stops where I was investigating the CPU temps): https://wormhole.app/nZWAR#yXxOdg2tR91f9T8c9biwqQ
Perhaps I should try the "Prefer FFmpeg" Decoding setting next if you say that the error means that the decoder is crashing?