I am having a problem with the CLR Profiler, that i downloaded here:
 http://www.microsoft.com/downloads/details.aspx?familyid=a362781c-3870-43be-8926-862b40aa0cd0&displaylang=en
When i run my game with the CLR P. opens a box with the text "Waitng for application to start Common Runtime...". My game starts, but when i close the game CLR P. crashes :S.. My game is online, can that be the problem? Or is it a problem with XNA? I seached the forum, and i can see that other people have been able to use CLR P. with XNA

I don't know what to suggest there. I've used the profiler many times without any trouble.

Maybe you could try profiling some other XNA games or samples, to see if this is an installation problem or just something specific to your game?

 It seems like it works just fine for me aswell... Strange.

And to hijack the thread: are there any good articles on how to use the CLR Profiler 2.0? I've found a few but they are mostly very theoretical and I would like to see some practical examples / instructions. It would also be nice with an XNA article on this because when I start to profile my little test application I get alot of information and tons of boxes and connections - I find it very hard to find anything useful at all from the output.

And also, the CLR Profiler 2.0 only supports memory profiling? What is recommended as code profiling, I've only found Ants (commercial) and nProf.

I would really like to learn these tools and take advantage of them, if you have any tips / recommendations on articles or approaches they are very welcome.

After hours of work i finally got it working.. I dont know what was wrong but it works now :S.. Anyway good question Michael Söderman

I just tried using to figure out what was stealing a bunch of memory in my game :p  It started up, I told it which exe to run, and it ran it, but the exe it was trying to run crashed.  It still outputted the reports, but I don't know how valid they are :/ 

Reviving an old thread... I just had this happen to me (it worked before).  After a little playing around, I was able to spot in the allocation graph (where tons of strings were being created) from the short time before my game crashed, that there was an I/O exception thrown in the AudioEngine's constructor.

So I tried running the CLR profiler from my game's directory and then it started working - so it seems like it isn't setting the correct current working directory when starting the game.

Michael Söderman:

And to hijack the thread: are there any good articles on how to use the CLR Profiler 2.0? I've found a few but they are mostly very theoretical and I would like to see some practical examples / instructions. It would also be nice with an XNA article on this because when I start to profile my little test application I get alot of information and tons of boxes and connections - I find it very hard to find anything useful at all from the output.

It's not much, but you might find a blog post I wrote helpful.

I've got an even worse problem than the OP. My game crashes on startup - I get no profiling at all, the game just goes kaboom. Anyone come across that and what did you do to fix it?

There are several versions of the .NET Profiler floating around (and available from Microsoft download) -- I know at least one works, and at least one doesn't work. Search the MSDN download area for the lastest version, and you should be OK.

I've got the latest CLR Profiler and it's crashing for me too -- it only seems to happen when the game screen loads, not in the menus. I've got deadlines to meet, so I can't exactly construct a repro right now.... anyone have a clue whats causing it?

Turned out for me the initial crash was in initialising XACT. No idea why - works fine when not using CLRProfiler. So I commented that out and tried again. Didn't crash, but didn't capture any data either (just sat there saying "waiting for CLR to start" or whatever). Not impressed so far, and the documentation is worse than useless. Basically, it just doesn't work as far as I can tell.

That's the problem I get when using the wrong version. Search for the 2.0 .NET CLR Profiler on MSDN downloads, and try more than one download. One of them will work (at least, it did for me, when I had the exact same symptoms as you).