Since downloading Xcode 11, I have noticed that setting breakpoints, stepping into and over code, that the debugger tends to hang, sometimes for minutes at a time. I cannot imagine that Apple would release something like this so I assume I have some misplaced configuration setting or something. Has anybody else noticed this? If so, is there a fix? Surely I am not the only person who has ran into this problem.
Yes, 11.2.1 was the fix provided by Apple
Related
I'm on Xcode 13 GM (13A233) and I'm noticing that it won't stay paused when it hits a breakpoint. It stops, but about a minute later it just resumes. Is there a new default setting that might cause this? I don't see anything relevant in "Behaviors," but maybe I'm missing something. Has anybody else encountered this issue?
The only unusual thing about my project is that I am calling Python from it, using PythonKit. But this breakpoint pause issue isn't isolated to code involving PythonKit.
I've tried all the usual "fixes"—i.e., clean build, delete derived data, reboot, etc. The app is just a simple SwiftUI app for macOS.
This is actually the debugger crashing and the app detaching: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log....
It doesn't do it my main View, but does do it in a static method called on a singleton in the app, and also at various points in a custom package I'm developing alongside the app.
I see a similar unresolved issue from August at bugs.swift.org: https://bugs.swift.org/browse/SR-15110?jql=text%20~%20%22lldb%20crash%22, In case anyone else is seeing the same issue (maybe you can post your log there).
UPDATE: I completely forgot that I was running on a dev snapshot toolchain. All good in Xcode 13.1 with bundled toolchain. Moral of the story; if something really strange is going on, check your toolchain.
I'm experienced a weird issue with Instruments. When I try to Profile the application, it gets stuck on an interface and becomes unresponsive. The same application is running perfectly on both Simulator and Device -- when not run with Instruments.
Is anyone else experiencing this issue? What's the workaround?
Additional Information:
1). This situation is occurring with both Allocations and Energy Diagnostics templates.
2). I'm profiling using "Debug" Build Configuration.
3). This issue is reproducing for more than one application.
Turns out, there were some NSLog statements in the code, and Instruments immediately freezes when NSLog statement is called. Pretty annoying and inconvenient (if you ask me).
Removing ALL NSLog statements from the code fixed the problem.
Since installing XCode 6 GM, it has been freezing and locking, showing the spinning wheel of death while I attempt to edit code that has syntax errors. Has anyone else seen this, and are there any known work-arounds?
I foolishly abandoned my cautious strategy of saving the previous version (Beta 7) and it appears that Beta 7 is no longer available for download. Are there any known archives of / for the link?
I have also posted to the dev forums and will follow up with a bug report, but it is hard to pin down the exact circumstances.
Edit:
Additonal Notes:
CPU: SourceKit Service is generally around 100%, but that has seem to have been the norm for the flavors of XCode, and the CPU seems to properly drop off when it finishes recompiling.
RAM: SourceKit is no longer exhibiting the memory leaks that used to cause it to halt and catch fire, memory does not appear to be a factor, and there are several ~ 5+ gigs to spare.
Environment:
Late 2012 Mac Mini, 16GB RAM
OS X 10.9.4 (to be fair, this was new today as well, driven by the requirements of XCode 6 GM).
That said, only the software changed today.
Update
Apple claims that this bug is fixed in Beta 6.1, for what it's worth.
You should look if you have any imports missing in your bridging header file. Sometimes even commented out imports will cause this behaviour. For me it was commented out Pixate Freestyle Cocoa Pod. I had to remove pod completely from my project to stop SourceKitService from crashing.
https://stackoverflow.com/a/25173389/527539
I can't say any of these fixed the issue, but they alleviated the situation:
I removed all playgrounds from the project tree. Saved them somewhere else.
I removed all objectiveC code from the swift project (when possible). This Spinning-wheel, BTW, is a problem only in my swift projects. My other Objective-C-only projects are fine.
It looks like it's the background indexing process which is taking all the CPU. Open "Activity Monitor" and see it right there at the top, using 360% CPU. Lowering the priority for this process helped as well (type in terminal):
renice 10 -p [pid]
Make sure to take the correct process id from Activity Monitor.
The higher the number (should not exceed 19) the lower the priority.
I make significant changes one at a time. It seems that the amount of errors in the file affect how many times and for how long the spinning wheel spins. It looks like some type of errors trigger it more often than others, but I'm not able to pin point which exactly.
XCode had a similar indexing issue in previous versions (see this Xcode4 issue: How to disable indexing in Xcode 4?) which gives me the hope they will fix this issue sometime, hopefully soon...
I create a new tab via menu File->New Tab and close the old tab that is frozen.
CmdT does not work that time.
If this isn't an appropriate question for SO, let me know and I'll take it down.
While working in Xcode on my MBA, I sometimes encounter a strange problem. It goes something like this:
Code, build and test my app on iPhone for a period of time (hours).
Save work, unplug iPhone test device, put MBA to sleep by closing lid.
Come back later and wake up MBA.
Internet on my MBA will not reconnect until I plug iPhone back in and continue to work on app.
The internet problem occurs around 70% of the time, and it seems to only subside once I continue work.
I understand this sounds like a vague and un-researched question, but I have looked and haven't found a solution.
Is this happening for anyone else? Perhaps I should file it as a radar...
I guess you are running Maveric OS (v10.9.*).
Try resetting SMC & PRAM with precaution ..
I'm on windows 7 x64. Using C++ in Visual Studio 2008 and 2010.
When I run any own application with VS after, aprox, 15 seconds the application is forced to exit. No messages, no Exceptions, no nothing. It doesn't matter how simple it is the application.
After a couple of weeks reviewing and commenting my code, I tried by reinstalling my S.O. and programs, thinking in some driver update or something similar. Whatever it was should solve my problem. That didn't solve the problem either.
You can see an example in
https://twitter.com/#!/nachovall/status/176996407780188160/photo/1/large
Note that it hasn't empty the buffer!! Just crazy.
I'm thinking in some whatchdog problem. I mean some, windows 7 issue which causes a given application to exit after some seconds.
The worst thing is that I have no idea about how to search this in Google. 'Silent crash'? It's not crashing, just exiting.
Well, if anyone knows what the problem is... you know.
By the way, I did a whole hardware analysis looking for some CPU or Memory problem. Nothing found.
Even more. I run the debug. I set a breakpoint in the first line of code. The application is doing nothing. Just waiting me to step over in the debugger. After 15 seconds, the application ends. Cool ha?
Ok, all night awake but finally found.
It was the antivirus program. Avast version 7.0.1407. When I disable it, everything get sense again.
It's been 2 weeks. 2 large and exhausting weeks. Anyone who's using this antivirus, please be aware.