[1.0.6.1] Job queue becomes stuck if additional jobs queued during downloading about nijiedownloader HOT 4 CLOSED

I think this may caused by the ManualResetEvent initial state is not properly set, will check.

from nijiedownloader.

I just had this happen after processing a ~2300image Tag Search job; I added a smaller Tag Search and gallery download while it was processing. The log is just as boring as the other I posted. This time I hit stop so I could delete the job gracefully, but it has been stuck Cancelling for an hour now. After deleting that, the status at the top still says cancelling and I can't start, stop or pause the queued download.

from nijiedownloader.

This issue that @Akio-kun brought up still seems to be one of the few outstanding problems as of version 1.0.7.7. I haven't experienced any serious freezing as mentioned in the previous post; just the non-continuous batch issue mentioned in the first post. Queue 10 artists, browse and add 10 more while that batch is going, and the job list inevitably halts after the initially queued 10.

One difference might be that I experience a "clean" stalling: either nothing happens after completion, the new jobs remain in a queued state and can be started by Pause/Resume. Have never seen the endless "running" or cancellation freezing. No corrupted images that I've seen, nor any jobs where only the folder image was downloaded before stalling.

I suppose this is the same behavior that PixivUtil is programmed with...you run a download job, and when it's done you can do more. But the interface is slick enough that it encourages this kind of multitasking, work-while-you-download capability, so I suppose the ideal behavior would be for the running queue to incorporate new jobs. Failing that, getting the "jobs finished" popup that normally appears at the true completion of all queued jobs would be a good alternative, so you would at least know to nudge the start button.

EDIT: The "all jobs completed" popup box seems to appear when most jobs are done, or when you've restarted the queue several times (but contrary to what I thought, can appear with newly-queued jobs still in the queue). I am unsure of its pattern as yet.

from nijiedownloader.

Haven't noticed the critical errors in quite a while (been using 1.0.7.7), I guess my post above was different behavior that seemed potentially related.

I've made a new issue (#41) for that, so I think this can safely be closed ^^

from nijiedownloader.