Run command seems to stop at seemingly random intervals

[kristo]

I'm running ffprobe to get ID3 tags in a loop. This works well enough at the beginning, but then stops after a couple of hundred files
when suddenly the command returns no result anymore. I can even start other programs in this loop when encountering the
problem, just to see wether the issue is related to ffprobe at all, but it isn't.

Sometimes run stops working after 50 cycles, sometimes after 300 and sometimes after 10. Does anyone know of a memory leak
or any other bug here?

[Jos]

Maybe showing some code would help?

Jos