35

I upgraded to Xcode 4.6 and whenever I debug and I execute "po" for the first time to inspect an object, the debugger takes like 1 minute to return. After that, every "po" command will work fast as usual.

Are you guys seeing this as well? Any fix?

Thank you

LocoMike
  • 5,626
  • 5
  • 30
  • 43
  • Nope, that is not what I get. Works just as good as it did before in prior versions. – Till Feb 07 '13 at 20:23
  • 4
    This is the effect of the phenomenon called "dynamic linkage". Also, Xcode is Xcode and not xCode. –  Feb 07 '13 at 20:24
  • Changed to Xcode, thanks. So if it is because of "dynamic linkage", how come @Till is not experiencing it? Does it have to do with some settings? Thanks – LocoMike Feb 07 '13 at 20:27
  • 1
    Because I do use a machine with 8GB of RAM and an SSD, I guess. – Till Feb 07 '13 at 20:28
  • 2
    @LocoMike I'd say it may or may not be actually visible (depending on the exact OS version, more precisely the implementation of the loader/dyld, the phase of the Moon, etc.) –  Feb 07 '13 at 20:28
  • I'm running Snow Leopard on an Air so that might make sense. I think it is time to ask for an upgrade then :) Thanks guys, I wish you had replied so that I could mark it as answered. – LocoMike Feb 07 '13 at 20:33
  • @LocoMike, is that issue when doing a po an array element. I noticed that when po array[32] element for example but not regular pos. This by the way happens on an iMac with 8MB Ram. If you answer yes, then it is a bug. – Khaled Barazi Feb 07 '13 at 23:44
  • @Spectravideo328 it happens almost every time, even with simple views. But as I said before, it only happens the first time. I run a 4GB Air, so that might be the reason. – LocoMike Feb 08 '13 at 16:11
  • 1
    You're not alone mike, SSD, 8 gigs of ram, 2.6 i7. PAINFULLY slow. (as in I was able to open chrome, google it and post this comment just in time for the object to print) – endy Feb 09 '13 at 08:49
  • @endy What OS are you using? I'm on Snow Leopard. Sorry to hear it is slow for you as well... well, not very sorry as it is good to see other people seeing it, but I share the pain :) – LocoMike Feb 09 '13 at 19:53
  • Mountain lion. Latest version. – endy Feb 09 '13 at 22:29
  • Ok, then I'm clueless... Have you seen people talking about this beside this thread? – LocoMike Feb 10 '13 at 01:58
  • I don't have a fix, but I can say that it has nothing to do with 8 Gb of RAM and an SSD. I have both, and I'm experiencing the same problem. Mountain Lion, mid 2009 MBP. Sometimes takes a minute to display. It's also not likely to be permissions. I recently rebuilt my primary drive from scratch, and migrated all my settings. The problem remains. – Ken Cooper Mar 02 '13 at 00:06
  • 7
    I see the same problem, it was introduced with 4.6. I suggest we all write a bug on Xcode, so that Apple can fix it. – fishinear Mar 05 '13 at 16:09
  • 3
    At the risk of being voted down, this is a prevalent bug which makes debugging worse than in 4.5.2 (a difficult feat). I propose (given @fishinear 's suggestion) that Apple be petitioned for a fix. – NSTJ Mar 15 '13 at 16:30
  • 1
    i see this painful 4.6 delay when trying to print in integer value: > p n – paiego Mar 16 '13 at 01:27
  • 1
    Still slow in 4.6.1. :-( – Ken Cooper Mar 16 '13 at 07:08
  • @fishinear do you know what the best way to report a bug to Apple is? – NSTJ Mar 16 '13 at 20:13
  • 1
    @TomJowett Use bugreporter, http://bugreport.apple.com, and login with your developer account. You cannot see bugs that other people have reported, but you can report your own bugs. See https://developer.apple.com/support/resources/bug-reporting.html for more info. – fishinear Mar 18 '13 at 14:41
  • much obliged, thanks @fishinear (edit: I just reported bug #13430971 if there's any way for people to get on board, though from what fishinear described it may not be possible to see/add to other bug reports) – NSTJ Mar 18 '13 at 15:52
  • You cannot join an existing bug. You'll need to report your own bug (I reported one earlier as well). Apple puts priority on bugs based on how many people have reported it. – fishinear Mar 18 '13 at 19:11
  • I've only noticed this when I am debugging on a device, in the simulator it is not noticeable. – Chris Wagner Mar 19 '13 at 05:22
  • as a coda I just went out today and bought a new rMBP with 8GB and I can guarantee this is not a system issue (it still hangs like maddd when running a po) – NSTJ Mar 20 '13 at 15:52
  • I started a bounty to this question here: http://stackoverflow.com/questions/15988445/how-do-i-quickly-inspect-the-value-of-an-arbitrary-variable-in-xcode-4-6-x/ – NSTJ Apr 19 '13 at 15:27

1 Answers1

6

Upgrading to 4.6.2 fixed this problem for me in Xcode

mattvv
  • 583
  • 5
  • 17
  • 1
    I read they improved LLDB performance for debugging. Well, this is closed! Thanks for sharing the pain everybody ;) – LocoMike Apr 23 '13 at 20:51