GitLab

I am running Windows XP with Service Pack 2 and the Vorbis 1.0.1 Tools.

When I was trying to run a large batch query converting standard WAV files (14 
GB in 255 Files (21 CDs) in a single directory) to Vorbis using OggDropXP 
(Quality: 6, no special options), the whole system reproducibly froze (3x) after 
approximately 1 GB of source data had been processed.

Suspecting OggDrop, I generated a batch file that individually called oggenc for 
each one of the remaining 200 files. Running the batch file in turn reproducibly 
led (4x) to a blue screen (IRQL_NOT_LESS_OR_EQUAL variety). The crash once again 
occured after about 1 GB of source data.

I have just finished encoding all files by dropping the remaining 100 files into 
OggDrop *one CD at a time* without incident. 

I do not think that the actual file content has anything to do with the problem, 
as the files affected by crashes were all handled without problems when I 
subsequently resumed encoding with the exact same file. 

My system is stable and I think I can rule out completely unrelated causes for 
the crashes, which occurred exactly, and only, when I used OggDrop/OggEnc. I had 
extensively used OggDrop before without any problems, but only for one CD at a 
time. 

Of course, it is possible or even probable that the actual fault does not lie 
with OggEnc/OggDrop, but the Windows Kernel/Explorer and was merely triggered 
through the interaction with OggEnc. Still, I find my system's behavior quite 
bizarre. While I could at least in principle imagine how a large number of files 
could crash OggDrop, I have no idea why OggEnc should be affected by being run 
50 times in a row.

I know this bug report is only partially helpful - if I can reproduce the blue 
screen one more time, I will add the detailed information (especially which 
module caused it).