4 ms·
Do you really mean segfault (i.e., SIGSEGV), or do you just mean that the program crashes in general? Either way, you might consider bringing this to the atten
by DoofusOfDeath 7y ago
Do you really mean segfault (i.e., SIGSEGV), or do you just mean that the program crashes in general?
Either way, you might consider bringing this to the attention of the ffmpeg developers [0]. If they don't have a fix already, that may appreciate your help in root-causing the bug.
[0] https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/ https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/
- ComputerGuru 7y agoYes, a literal SIGSEGV but the dump doesn't indicate anything amiss. It's not an ffmpeg issue because other long-running software also crashes when run alongside an encode job (e.g. I've had rav1e crash) some hours in, too. I prefer not to send software developers goose hunting unless I have some sort of valid repro case, which I don't, not really.
- DoofusOfDeath 7y agoAny chance you're running out of memory? Sometimes C/C++ code fails to properly handle failed memory allocations in those situations, leading to a misguided attempt to dereference a null pointer.