search

umageddon / namDHC

Windows frontend for CHDMAN - written in Autohotkey
GNU General Public License v3.0
340 stars 13 forks source link

There seems to be something up with the queue management. #20

Closed TomTurbine closed 1 year ago

TomTurbine commented 1 year ago

Hello again, I had already finished converting my stuff to CHD before so I didn't try it for that this time but instead tried to use namDHC to verify CHDs.

I typically cancelled making CHDs when it started giving errors but this went fast enough that I let it finish, and I think that might be part of the issues for all of them.

When it would give an error, a bunch more errors on future processes after that happened no matter what. And when I let them finish, the queue numbers wouldn't add up.

I let one go with 24 files, it started giving errors around fill number 19, then it ended with 23 of 24 processed with 5 failed and the queue clear. Like it messed up and deleted a job before it did it or something. Maybe something with the queue management might be causing the issues for the other stuff as well.

One I break the jobs up into a smaller amount of files, I get zero errors but when I go above 20 files it can happen every so often and if I go above 50 files it almost guaranteed to happen.

TomTurbine commented 1 year ago

Notice it is showing a job timed out as well.

TomTurbine commented 1 year ago

Slight update. I dropped the number of instances running at a time from 3 down to only running 1 and it ran through over a thousand CHD files verifying them all zero errors or warning.