Enabling network debugging makes Xcode unusably slow
| Originator: | steipete | ||
| Number: | rdar://34650530 | Date Originated: | 26-Sep-2017 11:29 AM |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | 9.0 9A235 |
| Classification: | Serious Bug | Reproducible: | Always |
Summary: When I enable network debugging, Xcode basically beachballs all the time. It takes me a few minutes to make it dispatch enough clicks so I can disable network debugging again. It’s crazy how slow this is, and I own the top of the line 2017 MacBook Pro 15’ TouchBar - literally costing 5000 Euros. Steps to Reproduce: Open complex project Enable network debugging Observe that Xcode slows to a crawl Expected Results: Xcode should work normally (so, beachballing < 2 seconds is acceptable and I’m used to it) Actual Results: My devices are all within 1 meter and WiFi is stable. Jet it seems that Xcode has connection troubles and thus triggers a device refresh. This takes around 5 seconds of pure main thread freezing time and is the same that I reported at WWDC: rdar://32626309 And by the time it’s updated, KVO triggered already another refresh, freezing it again. Version: 9.0 9A235 Notes: This feature is completely unusable. What’s Xcode really doing when it calls -[IDEScheme availableRunDestinations]? Why is that taking so long? Why is that refreshed so often? I did a Activity Monitor sample.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!