Best way to track down a memory leak (C#) only visible on one customer's box

Question

What is the best way to track down a memory leak that is only found on one customer\'s test/release box, and no where else?

Answer 1

Here's an option: Give them a box where the leak isn't present.

Sometimes, it's not the code.

Edit: It's either the code, the data, or the configuration.

Or the .NET Framework, the OS, the drivers, IIS, or COM (automating Excel, for example), or so-on.

My assumption is that the memory leak is not reproducible except on the client's box (which the dev cannot be allowed to access for debugging).