Comment 45 for bug 453931

I just read a trick somewhere for how to force relocation of a dll: load a second copy (with a different name). I'm not sure this would work when linking statically (because of finding the same symbols twice), but it might work when loading it at run-time. If this works then it would allow testing whether dll relocation is what is causing the problem. (I won't get around to trying this until friday at the earliest, so if someone else wants to try this, be my guest.)