That would be quite an essential piece of information. Can you try without the D3D9 client to see if you can reproduce the crashes? If it is reproducible, can you post a scenario?
Also, what makes you think that the problem is down to a memory leak? Do you crash due to running out of 32-bit address space? (which has been observed before, though this happens without memory leak, but because of over-enthusiastic application of memory-greedy render settings).
Ok, I have tried some things again now, I have created three scenariofiles and tested them. I have uploaded this files here:
> Eduard.scn: Standing on brighton beach, when using timewarp for a while at high speed, I get a CTD in the D3D9Client.
> Eduard1.scn: Transfer from Earth to Moon, using DG-S. When repeating I sometimes experience a CTD, but it's difficult to reproduce.
> Eduard1A.scn: A modified version of the previous scenario: I replaced the DG-S by Shuttle-A (and checked very well that I did it in the correct way).
Now I get much more CTD's, when using the D3D9Client with setting "linear interpolation".
To reproduce: 1. move the vessel with the RCS. 2. Killrot. 3. timewarp 1000x or 10000x.
With 1000x, I am still very far away from the moon and I already get a CTD.
I have tried to reproduce exactly the same CTD with the stock client orbiter.exe, but I do not see it there anymore.
But I still think it's very strange that the problem occurs much more frequently with the Shuttle-A version than with the DG. So I am not shure if we can say that it's only a problem of the D3D9Client.
And finally, I also noticed this: Sometimes when coming very close to the moon, the stock client also crashes sometimes, at least when using "linear interpolation". This could be a purely terrain related problem of course. I don't know. But it's important to know that this also happens with the stock client.
I hope this information helps you.