Crash in dyld3 with 5.8 in Screen

Question

Created Feb ’21

Replies 4

Boosts 0

Views 1.4k

Participants 3

I am trying to load one webpage in webview using webkit.
But getting crashed in iPhone Xs, iPhone 11 pro in iOS 14.4

AppSpectorSDK
0x107cd4000 + 710820
AppSpectorSDK
0x107cd4000 + 710268
libdyld.dylib
___ZN5dyld39AllImages17runImageCallbacksERKNS_5ArrayINS_11LoadedImageEEE_block_invoke
libdyld.dylib
dyld3::AllImages::runImageCallbacks(dyld3::Array<dyld3::LoadedImage> const&)
libdyld.dylib
dyld3::AllImages::loadImage(Diagnostics&, char const*, unsigned int, dyld3::closure::DlopenClosure const*, bool, bool, bool, bool, void const*)
libdyld.dylib
dyld3::AllImages::dlopen(Diagnostics&, char const*, bool, bool, bool, bool, bool, void const*, bool)
libdyld.dylib
dyld3::dlopen_internal(char const*, int, void*)
libdyld.dylib
dlopen_internal(char const*, int, void*)
CoreFoundation
_CFBundleDlfcnLoadBundle
CoreFoundation
_CFBundleLoadExecutableAndReturnError
Foundation

[NSBundle loadAndReturnError:]

TextToSpeech
TTSSpeechUnitTestingMode
libdispatch.dylib
_dispatch_client_callout
libdispatch.dylib
_dispatch_lane_barrier_sync_invoke_and_complete
TextToSpeech
TTSSpeechUnitTestingMode
TextToSpeech
TTSSpeechUnitTestingMode
TextToSpeech
TTSSpeechUnitTestingMode
AXSpeechImplementation
0x1d7e3d000 + 31292
WebCore
WebCore::PlatformSpeechSynthesizer::initializeVoiceList()
WebCore
WebCore::PlatformSpeechSynthesizer::voiceList() const
WebKit
WebKit::WebPageProxy::speechSynthesisVoiceList(***::CompletionHandler<void (***::Vector<WebKit::WebSpeechSynthesisVoice, 0ul, ***::CrashOnOverflow, 16ul, ***::FastMalloc>&&)>&&)
WebKit
WebKit::WebPageProxy::didReceiveSyncMessage(IPC::Connection&, IPC::Decoder&, std::__1::unique_ptr<IPC::Encoder, std::__1::default_delete<IPC::Encoder> >&)
WebKit
IPC::MessageReceiverMap::dispatchSyncMessage(IPC::Connection&, IPC::Decoder&, std::__1::unique_ptr<IPC::Encoder, std::__1::default_delete<IPC::Encoder> >&)
WebKit
WebKit::WebProcessProxy::didReceiveSyncMessage(IPC::Connection&, IPC::Decoder&, std::__1::unique_ptr<IPC::Encoder, std::__1::default_delete<IPC::Encoder> >&)
WebKit
IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >)
WebKit
***::Detail::CallableWrapper<IPC::Connection::SyncMessageState::processIncomingMessage(IPC::Connection&, std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >&)::$_1, void>::call()
JavaScriptCore
***::RunLoop::performWork()
JavaScriptCore
***::RunLoop::performWork(void*)
CoreFoundation
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
CoreFoundation
__CFRunLoopDoSource0
CoreFoundation
__CFRunLoopDoSources0
CoreFoundation
__CFRunLoopRun
CoreFoundation
CFRunLoopRunSpecific
GraphicsServices
GSEventRunModal
UIKitCore

[UIApplication _run]

UIKitCore
UIApplicationMain
MCPTT_ATT
0x102c80000 + 375724
libdyld.dylib
start

Boost

Answer 1

Zengfeng OP

Mar ’22

Hi, how did you resolve this crash finally? I'm facing a crash with similar stack trace 😢

0

Answer 2

DTS Engineer OP

Apple

Mar ’22

I'm facing a crash with similar stack trace

There’s not much you can learn from a simple backtrace like this (especially given the formatting)-: If you post a full Apple crash report, I should be able to offer more insight into this.

For advice on how to do this, see Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

Zengfeng OP

Mar ’22

OK, I have attached full crash report. Any suggestions would be really appreciated!

crash report.txt

0

Answer 4

DTS Engineer OP

Apple

Mar ’22

OK, I have attached full crash report.

Unfortunately, while that looks kinda like an Apple crash report, it isn’t. Do you have an Apple crash report for this problem? If so, please post that.

If not, temporarily [1] remove your third-party crash reporter, reproduce the problem, and post that crash report.

Hmmm, that

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Well, my real advice is that you remove it permanently (-: See Implementing Your Own Crash Reporter for an explanation as to why.

0