RESOLVED DUPLICATE of bug 149466 Bug 158451
com.apple.WebCore crashed at WebCore::EventListenerMap::remove(WTF::AtomicString const&, WebCore::EventListener&, bool, unsigned long&) + 92 
https://bugs.webkit.org/show_bug.cgi?id=158451
Summary com.apple.WebCore crashed at WebCore::EventListenerMap::remove(WTF::AtomicStr...
Ryan Haddad
Reported 2016-06-06 17:03:29 PDT
media/track/track-cue-rendering-snap-to-lines-not-set.html <https://build.webkit.org/results/Apple%20El%20Capitan%20Release%20WK2%20(Tests)/r201730%20(6586)/results.html> http/tests/xmlhttprequest/xmlhttprequest-onProgress-open-should-zero-length.html <https://build.webkit.org/results/Apple%20iOS%209%20Simulator%20Release%20WK2%20(Tests)/r201731%20(6289)/results.html> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.WebCore 0x000000010e3b087c WebCore::EventListenerMap::remove(WTF::AtomicString const&, WebCore::EventListener&, bool, unsigned long&) + 92 (EventListenerMap.cpp:138) 1 com.apple.WebCore 0x000000010e3b6ce1 WebCore::EventTarget::removeEventListener(WTF::AtomicString const&, WebCore::EventListener&, WebCore::EventTarget::ListenerOptions const&) + 65 (EventTarget.cpp:105) 2 com.apple.WebCore 0x000000010eb447b2 WebCore::Node::removeEventListener(WTF::AtomicString const&, WebCore::EventListener&, WebCore::EventTarget::ListenerOptions const&) + 18 (Node.cpp:1989) 3 com.apple.WebCore 0x000000010e543f7c WebCore::HTMLMediaElement::removeEventListener(WTF::AtomicString const&, WebCore::EventListener&, WebCore::EventTarget::ListenerOptions const&) + 76 (HTMLMediaElement.cpp:5253) 4 com.apple.WebCore 0x000000010e3b75a0 WebCore::EventTarget::fireEventListeners(WebCore::Event&, WebCore::EventTargetData*, WTF::Vector<WebCore::RegisteredEventListener, 1ul, WTF::CrashOnOverflow, 16ul>&) + 832 (EventTarget.cpp:293) 5 com.apple.WebCore 0x000000010e3b71a0 WebCore::EventTarget::fireEventListeners(WebCore::Event&) + 224 (EventTarget.cpp:226) 6 com.apple.WebCore 0x000000010e39ccdf 0x10dfca000 + 4009183 7 com.apple.WebCore 0x000000010e39d3eb WebCore::EventDispatcher::dispatchEvent(WebCore::Node*, WebCore::Event&) + 875 (EventDispatcher.cpp:127) 8 com.apple.WebCore 0x000000010e48b4e9 WebCore::GenericEventQueue::dispatchOneEvent() + 89 (GenericEventQueue.cpp:72) 9 com.apple.WebCore 0x000000010eceac7a WebCore::TaskDispatcher<WebCore::Timer>::sharedTimerFired() + 362 (GenericTaskQueue.cpp:66) 10 com.apple.WebCore 0x000000010f03027f WebCore::ThreadTimers::sharedTimerFiredInternal() + 175 (ThreadTimers.cpp:124) 11 com.apple.WebCore 0x000000010ea9187f WebCore::timerFired(__CFRunLoopTimer*, void*) + 31 (MainThreadSharedTimerCF.cpp:75) 12 com.apple.CoreFoundation 0x00007fff95b25b94 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 13 com.apple.CoreFoundation 0x00007fff95b25823 __CFRunLoopDoTimer + 1075 14 com.apple.CoreFoundation 0x00007fff95b2537a __CFRunLoopDoTimers + 298 15 com.apple.CoreFoundation 0x00007fff95b1c871 __CFRunLoopRun + 1841 16 com.apple.CoreFoundation 0x00007fff95b1bed8 CFRunLoopRunSpecific + 296 17 com.apple.HIToolbox 0x00007fff98218935 RunCurrentEventLoopInMode + 235 18 com.apple.HIToolbox 0x00007fff9821876f ReceiveNextEventCommon + 432 19 com.apple.HIToolbox 0x00007fff982185af _BlockUntilNextEventMatchingListInModeWithFilter + 71 20 com.apple.AppKit 0x00007fff93652df6 _DPSNextEvent + 1067 21 com.apple.AppKit 0x00007fff93652226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 22 com.apple.AppKit 0x00007fff93646d80 -[NSApplication run] + 682 23 com.apple.AppKit 0x00007fff93610368 NSApplicationMain + 1176 24 libxpc.dylib 0x00007fff90aa1194 _xpc_objc_main + 795 25 libxpc.dylib 0x00007fff90a9fbbe xpc_main + 494 26 com.apple.WebKit.WebContent.Development 0x000000010c1077e7 main + 422 27 libdyld.dylib 0x00007fff9f2fd5ad start + 1
Attachments
Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2016-06-06 17:04:59 PDT
Looking.
Ryan Haddad
Comment 2 2016-06-06 17:37:19 PDT
Duping to original bug since this change was rolled out. *** This bug has been marked as a duplicate of bug 149466 ***
Note You need to log in before you can comment on or make changes to this bug.