Files getting reprocessed after SA crash

[AndyS]

Running 0.5.6.22 with latest SA on XPSP2 with SageTV on remote files via UNC.

I've been getting regular crashes of SA, and sometimes I have to kill an active SA that gets 'hung' in some way and sucks up all the CPU and/or memory.

After a process crash/kill it seems as though DM2 gets confused and re-queues the file associated with the crash at the top of the queue. This results in the same file being processed more than once. I've also seen a number of instances where even though the file is being processed twice in the active process window, a third instance of the file is added at the top of the queue.

As you can imagine, running SA more than once concurrently on the same file causes all sorts of problems (high memory/cpu, jobs never finish etc.).

Can you make a tweak to DM2 to ensure that the same file doesn't exist more than once for the same job in both the active and queued job lists?

Andy.

[AndyS]

FYI, it's not just after a crash.

I stopped DM2, stopped all SA sessions, cleaned up any .TXT files that were being written to, and restarted DM2.

At first everything looked fine, but about 1 hour later I looked at my CPU usage and it was 100% with one SA uusing over 200MB of memory. A look at DM2 shows the same show being processed twice, and additionally that same show is at the top of the queued jobs list.

This really appears to be a problem Jere (at least for me - ymmv!!).

Andy.

[AndyS]

I have a rule in SA to not process a file if its category includes 'Children'. The link to the Sage Webserver is working fine and this rule does appear to get followed.

The file that I mentioned above IS a show with 'Children' in the category.

I did a check and the file still exists within Sage, and exists on the filesystem. There does not appear to be a .TXT file for this MPG.

Andy.

EDIT: The file is a 5-minute show (around 160MB) if you need it.

[AndyS]

I stopped DM2 and when I killed the first SA session two others completed immediately. I believe that these were both children's programs. As soon as I killed the first SA the .TXT file for the show mentioned earlier did get created.

So the SAs are indeed interfering with each other somehow.

Andy.

[Jere_Jones]

Ok. I'm tracking now. I think I know what the problem may be. Good troubleshooting!

Jere