Hi, I'm working with @isaacweisberg and have been investigating this for the past few days. I've opened FB20359822 (Xcode 26 on device debugging performance severely degraded) which contains extensive information about the issue, a vanilla project that reproduces the behavior we see and experience as well as leads to what is causing this issue (a mix of new gdb/gdb-remote behavior, threads and dynamic libraries). Sincerely, Marty, iOS Engineering @amo

Hi @DTS Engineer ! I'm working with @isaacweisberg and have been investigating this issue for the past few days. I've opened FB20359822 (Xcode 26 on device debugging performance severely degraded) which contains extensive information and attachments regarding the issue, a vanilla project reproducing it and showing the same behaviors that we see in our main app as well as some leads to the source of the issue (changes in gdb/gdb-remote, threads and dynamic libraries). Sincerely, Marty, iOS @amo

Any news on this, issue is still present with Xcode 26.1 beta 2 (17B5035f)

Added log files to FB20359822 (Packets and sample, with the experimental feature disabled and enabled) Xcode 26.2 in conjunction with iOS 26.2 fixed the exponential time it took to do a DLOpen with the debugger attached on Xcode 26, however the time it takes for one DLOpen is still ~0.10/0.15s on Xcode 26.x when it was only ~0.02/0.03s on Xcode 16.4. A huge number of DLOpens at app start will still cause the issue (We have around 200 dylibs that are loaded after app delegate init, mostly from Accessibility Bundles). 2000.15 = 30 seconds 2000.02 = 4 seconds Pretty consistent with what we see when the debugger is attached on Xcode 26.2 vs Xcode 16.4. Thank you. Sincerely, Marty, iOS @amo