Bug with starting Instruments via Profile under Xcode 4.1 Build 4B110

Question

Important Update

The strange bug is fixed (at least for me) in Xcode 4.2!

---

I've a serious problem with Xcode 4.1 Build 4B110 under Mac OS X Lion and running Instruments via Xcode. The problem is that Instrument freezes partly if I start it via Xcode. So if I start a project in Xcode 4.1 and open "Profile" the Instruments UI appears. The timer starts running, but the instruments app doesn't track anything and the more serious problem:

The program seems to be running but does not react to any actions I make. So I can not click on any buttons etc. Nothing happens. The timer is still running, but I can not do anything. I also can not close the window/app anymore. So I have to force stop the Instruments app.

But if I start the Instruments app directly via Developer/Applications/Instruments.app everything is ok. Of course, the app doesn't track anything, but I can click on the buttons and anything possible there.

So does anyone know about this problem?

Does anybody know how to fix this weird problem?

I've also deleted the developers folder with the corresponding deinstall-script file and reinstalled Xcode 4.1. But still the problem persists.

Can anybody give me a hint, tip, etc.?

Would be really great!

Update

So, further weird stuff:

Profile somehow worked for iOS 3.0 version apps, but after making a short break it didn't work again. So, I don't know where this bug is located. I guess it's about the target app iOS version.

Thanks, Andreas

Answer 1

Quoting your comment on this, andi1984, so that no one misses this "big" answer for anyone (like me) for whom it is a lifesaver. This worked great for me!

If I'm opening Xcode, choose Profile and choose one instrument (let's say Leaks) the new Instrument window opens. Then I need to go back to Xcode (while Instrument.app window is still open in background!) and have to use command + tab to choose out of Xcode in front the Instrument.app again. Then the Instrument app shows me the tracked data. Really weird problem, but now it works. ;-)