Fix: slow app launch under the debugger#131
Open
wellingtoncosta wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The plugin installed a regex breakpoint (
BreakpointCreateByRegexon^_Konan_init_*) on the dummy target to discover loaded Kotlin modules. Regex breakpoints can't use LLDB's name-accelerator index, so resolving one forces LLDB to realize the full symbol table of every module as it loads. An iOS appdlopenshundreds of frameworks at launch, so this ran on every debug session for every app — even ones with no Kotlin — roughly doubling launch time.Replace it with lazy, stop-time discovery:
symtabtouch), exact-name probe for the Kotlin runtime marker, and only deep-scan real Kotlin modules. ~99% of modules are eliminated by path alone.ObjCbase-class prefix read on later stops (theclass_ro_tname pointer isn't rebased on the earliest stop), capped, with module-name formatters registered immediately.Measured on WordPress app (41 frameworks), launch->
UIApplicationMain, median of 5 interleaved runs: baseline 3.15s, old plugin 8.48s (2.70x), new plugin 3.11s (~baseline).