Profiler shows leaks on one machine but not another

LoopM

My coworker's machine shows no memory leaks for a given test case, whereas my machine shows leaks. He's tried running my exe on his machine...no leaks. I've tried running his exe on my machine...leaks. So that rules out different source code. We're both running version 5.1.0.15 of the profiler. We're both following the same steps (we've even tried "driving" at the other's machine.) Any ideas on what could be causing this? I also tried commenting out all of the useless finalizers in the code in case it was a non-deterministic cleanup scenario, but the results were the same.

Chris.Allen

That is, like, so totally freaked up man. Could you please save the results for each session and send them over to support@red-gate.com

We have some really freaky guys over here who will probably understand the problem )

Chris.Allen

Oooh- one thing- since .Net Frameworks are (mostly) backwards-compatible, I wondered if could you be running the same assembly on different framework versions?

LoopM

We got it figured out. The details contained in the memory profile eventually led us to find this WPF hotfix from Microsoft:

http://support.microsoft.com/kb/967328

which apparently had already been installed in some form or another on my colleague's machine. He had not explicitly installed this particular hotfix, but he may have installed other hot fixes. (Not sure how that works really. Are hotfixes cumulative? Oh well.) After installing the hotfix on my machine, the leaks are no longer being reported.

Thanks!