A significant number of UIWebView crashes in Chrome for iOS look like this:
Thread 18 CRASHED [EXC_BAD_ACCESS / KERN_INVALID_ADDRESS @ 0x10000000000000000] MAGIC SIGNATURE THREAD
0x00000001936dd1b0 [WebCore + 0x000291b0 ] void std::__1::__push_heap_front<WebCore::TimerHeapLessThanFunction&, WebCore::TimerHeapIterator>(WebCore::TimerHeapIterator, WebCore::TimerHeapIterator, WebCore::TimerHeapLessThanFunction&, std::__1::iterator_traits<WebCore::TimerHeapIterator>::difference_type)
0x00000001936dd0c4 [WebCore + 0x000290c4 ] WebCore::TimerBase::heapDeleteMin()
0x00000001936dcf50 [WebCore + 0x00028f50 ] WebCore::ThreadTimers::sharedTimerFiredInternal()
0x00000001936dcec0 [WebCore + 0x00028ec0 ] WebCore::timerFired(__CFRunLoopTimer*, void*)
0x0000000185c91fd0 [CoreFoundation + 0x000ddfd0 ] __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
0x0000000185c91c80 [CoreFoundation + 0x000ddc80 ] __CFRunLoopDoTimer
0x0000000185c8f6cc [CoreFoundation + 0x000db6cc ] __CFRunLoopRun
0x0000000185bbd1f0 [CoreFoundation + 0x000091f0 ] CFRunLoopRunSpecific
0x0000000193763fe8 [WebCore + 0x000affe8 ] RunWebThread(void*)
0x0000000196befe7c [libsystem_pthread.dylib + 0x00003e7c ] _pthread_body
0x0000000196befdd8 [libsystem_pthread.dylib + 0x00003dd8 ] _pthread_start
0x0000000196becfac [libsystem_pthread.dylib + 0x00000fac ] thread_start
Unfortunately these are coming from automated reports, and we don't have repro steps. Is there any information we could gather from aggregated reports that could help pinpoint this?
Note that this is also filed as rdar//16068939
Please let us know once you have crash data from iOS 8.1.1. Bug 137009 may have addressed a portion of these crashes (or even all of them, if we are lucky).
We don't have much data yet, but so far none of our 8.1.1 crashes seem to have heapDeleteMin, which is a good sign. I'll update at the beginning of next week when we've had time to collect more data.
Still 0 hits on anything with WebCore::TimerBase::heapDeleteMin in the stack for 8.1.1; I think we have enough data that we can call this fixed. Thanks!
Great! I'll call this a duplicate of bug 137009 then.
*** This bug has been marked as a duplicate of bug 137009 ***