Profiling Windows Services

[beanmf]

I have a multi-threaded .Net Window Service on a 4cpu server. App domains are involved. Some profilers won't touch this kind of problem. What can you do (or what can I do to trace memory problems)? I can exercise the service code locally on a single cpu machine, but that may not be quite the same.

[Andreas Suurkuusk]

When AppDomains are involved, it is recommended that you disable root referee identification and heap utilization tracking (using the Settings form under the Tools menu).

If you disable those features, .NET Memory Profiler should be able to profile your service.

Are you experiencing a specific problem?