Thing is, I have several instances of ffmpeg running in the same server (configured as a system service, and thus the systemd journal logs), and can't find which one is triggering the errors. All I have is that memory address form the encoder/decoder.
So, I come to this mailing list to ask this question: does anybody knows a simple way to match that memory address with the current system proccess using it?
Daniel Cantarin via ffmpeg-user (12020-06-10):
> So, I come to this mailing list to ask this question: does anybody
> knows a simple way to match that memory address with the current
> system proccess using it?
No, the address will not help you to that. Most likely it is randomized,
and even if it was not it is not reproducible.
Arrange for your logs to arrive to different places or with proper
tagging. If your several instances of ffmpeg are started by systemd, it
is probably already the case, and you just need to read journalctl's doc
to get the information you need.