Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Xcode debug speed
See original GitHub issueThe speed of the debug is very slow ? any advice ? my xcode version is 11.6 (11E708)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
Extrem slow debug launch startup | Apple Developer Forums
Every debug start in an iOS project (macOS projects start up fast) that I'm working on (even in a blank new project), lasts...
Read more >Xcode 11 debugger is extremely slow - A known problem?
Program execution stops immediately when the breakpoint is reached. However Xcode needs up to 30 seconds to show the position in the code...
Read more >Five Xcode Tips To Speed Up Your Development - Cocoacasts
Whenever a breakpoint is hit during a debug session, Xcode automatically shows me the tab named Trace and opens the Debug Navigator. To...
Read more >Speeding Up Xcode Builds - Ricardo Castellanos - Medium
A few suggestions you can use to speed your Xcode build times ... Debug Symbol (dSYM): by default, debug builds of an application...
Read more >Lldb is slow to resolve local vars - Swift Forums
Whenever I set breakpoint in Swift code in Xcode, LLDB takes at least 60 seconds to resolve types of local variables on hot...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s a long story. I don’t think it’ll ever be quite as fast, but as long as it’s usable, that’s a start. About a year and a half ago I took the stock python file and did a bunch of optimizations on it, then submitted that to Jetbrains. They took some of them, but not all. I need to fix the current issue, then see if there are any other optimizations that would make sense, but I want to be able to use the file provided by Jetbrains if possible, so we don’t need to maintain a fork of it. We’ll see.
closing this. We’re going to be syncing our lldb script with the JB one more frequently going forward, and looking for ways to improve the step and data access speeds.