My question is: why is this specific to 64-bit, though?
asked myself the very same question, still no answer
may be there's a difference in procedure of loading/unloading DLLs between x32 and x64 modes oO
What I'm getting at is, is there any chance that it's caused by being miscompiled?
not a chance, I can see from the code that some objects are NOT deleted by destructor
===
in fact these bugs are very uncommon
I mean the only chance to face them is to use AVS+ inside ffdshow - then you can load/unload AVS several times in the same process