Maybe it's just from rapidly and reptitively calling the same program (in my case, flac). I wouldn't be surprised of memory leakes there either. Isn't there some flac ddl that can be invoked instead?

Yeah, you're right, at some point the program says it cannot execute, about the point where my Windows Page File is about 1.03 Gigabytes. Guess there's a serous memory leak in the tool.