#10Đx00007fff207a18da in _CFBundleLoadExecutableAndReturnError () ![]() #5Đx00000001183ed519 in dyld::link(ImageLoader*, bool, bool, ImageLoader::RPathChain const&, unsigned int) () #4Đx00000001183fc5a9 in ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, bool, ImageLoader::RPathChain const&, char const*) () #3Đx00000001183ecf51 in dyld::notifyBatchPartial(dyld_image_states, bool, char const* (*)(dyld_image_states, unsigned int, dyld_image_info const*), bool, bool) () #2Đx00000001183fa3af in notifyGDB(dyld_image_states, unsigned int, dyld_image_info const*) () ![]() #1Đx00000001183fa6bb in gdb_image_notifier(dyld_image_mode, unsigned int, dyld_image_info const*) () Every time I break into the debugger the top of the stack looks like this:Ĭode Block Main Thread (1) Queue : -thread (serial) The bundles in particular are now loading very slowly. (This is using an iMacPro 2017, 2.5 GHz 14-Core Intel Xeon with 64GB.) With this slower dyld in macOS 11.3 (and 11.3.1), the application takes over a minute before the splash screen is displayed and another 9 or 10 minutes to finish loading all the components. Previously, the splash screen was visible almost immediately however, it could take another minute or so to load the hundreds of dylibs, frameworks and plugin bundles to complete the application's initialization. It now takes ten times longer to startup our application after upgrading to BigSur 11.3 (and 11.3.1). The slow down in Debugger launch times can be even worse for large macOS applications.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |