Jump to content

Run command seems to stop at seemingly random intervals

Recommended Posts

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?

Cheap, Fast, Good - Choose any two

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...