崩溃:WebThread-EXC_BAD_ACCESS KERN_INVALID_ADDRESS [英] Crashed: WebThread - EXC_BAD_ACCESS KERN_INVALID_ADDRESS

查看:397
本文介绍了崩溃:WebThread-EXC_BAD_ACCESS KERN_INVALID_ADDRESS的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

自2016年11月8日以来,我们发现WebThread导致的崩溃突然增加。我们不知道是什么原因导致了崩溃。

Since November 8, 2016, we've seen a sudden increase in crashes from WebThread. We don't know what is causing the crash.

我们的应用程序中确实有网络文章和广告。我们没有任何应用发布。网络或广告上没有任何重大变化。

We do have web articles and ads in the app. We did not have any App Release. There were no significant changes on the web or ads.

由于崩溃是在没有文章的屏幕上发生的,因此我们认为这是在广告上发生的。

Since crashes are happening on screens without articles, we are thinking it is happening on ads.

还有其他人看到吗?有什么想法,想法吗?

Is anyone else seeing this? Any thoughts, ideas, anything?

堆栈跟踪:

Crashed: WebThread
0  WebCore                        0x184b7e47c WTF::HashMap<WTF::String, WebCore::ApplicationCacheGroup*, WTF::StringHash, WTF::HashTraits<WTF::String>, WTF::HashTraits<WebCore::ApplicationCacheGroup*> >::remove(WTF::String const&) + 48
1  WebCore                        0x184b7abbc WebCore::ApplicationCacheStorage::cacheGroupDestroyed(WebCore::ApplicationCacheGroup*) + 52
2  WebCore                        0x184b7abbc WebCore::ApplicationCacheStorage::cacheGroupDestroyed(WebCore::ApplicationCacheGroup*) + 52
3  WebCore                        0x184b70628 WebCore::ApplicationCacheGroup::~ApplicationCacheGroup() + 56
4  WebCore                        0x184b70b10 WebCore::ApplicationCacheGroup::~ApplicationCacheGroup() + 12
5  WebCore                        0x184b72334 WebCore::ApplicationCacheGroup::disassociateDocumentLoader(WebCore::DocumentLoader*) + 184
6  WebCore                        0x184a024a0 WebCore::ApplicationCacheHost::~ApplicationCacheHost() + 48
7  WebCore                        0x184a01ad0 WebCore::DocumentLoader::~DocumentLoader() + 168
8  WebKitLegacy                   0x185976ba8 WebDocumentLoaderMac::~WebDocumentLoaderMac() + 84
9  WebCore                        0x184e30a78 WebCore::FrameLoader::detachFromParent() + 324
10 WebKitLegacy                   0x1859e0b08 __29-[WebView(WebPrivate) _close]_block_invoke + 348
11 WebCore                        0x1857842c4 HandleRunSource(void*) + 368
12 CoreFoundation                 0x180ab509c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
13 CoreFoundation                 0x180ab4ab0 __CFRunLoopDoSources0 + 412
14 CoreFoundation                 0x180ab2830 __CFRunLoopRun + 724
15 CoreFoundation                 0x1809dcc50 CFRunLoopRunSpecific + 384
16 WebCore                        0x1849ce108 RunWebThread(void*) + 456
17 libsystem_pthread.dylib        0x180763b28 _pthread_body + 156
18 libsystem_pthread.dylib        0x180763a8c _pthread_body + 154
19 libsystem_pthread.dylib        0x180761028 thread_start + 4


推荐答案

回答我自己的问题是要添加比注释区域更多的详细信息。

由于我没有解决方案,因此未标记为已回答。

很遗憾,我们无法解决问题。幸运的是,崩溃率在2-3天后下降了。

Unfortunately, we were not able to solve issue. Fortunately, crash rate came down after 2-3 days.

花费3天后,我们确定它与Google Ads有关。但是,为什么崩溃率上升和下降对我们来说仍然是一个谜。

After spending 3 days, we were certain it was related to Google Ads. However, Why crash rate went up and down is still a mystery for us.

一些注释/结论:


  • 请求/处理广告时,我们是否在做一些愚蠢的事情?


    • 可能,但是由于现有的稳定版本正在发生,因此机会很小。


    • 崩溃率下降了,因为我们不再投放该广告了吗?

    这篇关于崩溃:WebThread-EXC_BAD_ACCESS KERN_INVALID_ADDRESS的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆