We have started seeing frequent assertion failures in InspectorTimelineAgent::didCompleteCurrentRecord a couple days ago. Not a lot of tests crash, but overall, this nearly blocks debug EWS. E.g.: http://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#tests=imported%2Fblink%2Fanimations%2Fbase-render-style-body-crash.html http://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fblink%2Fcompositing%2Flayer-creation%2Fiframe-clip-removed.html ASSERTION FAILED: entry.type == type /Volumes/Data/slave/elcapitan-debug/build/Source/WebCore/inspector/InspectorTimelineAgent.cpp(520) : void WebCore::InspectorTimelineAgent::didCompleteCurrentRecord(WebCore::TimelineRecordType) 1 0x110108670 WTFCrash 2 0x1131ac270 WebCore::InspectorTimelineAgent::didCompleteCurrentRecord(WebCore::TimelineRecordType) 3 0x1131b086c WebCore::InspectorTimelineAgent::internalStart(int const*)::$_1::operator()() const 4 0x1131b077d void std::__1::__invoke_void_return_wrapper<void>::__call<WebCore::InspectorTimelineAgent::internalStart(int const*)::$_1&>(WebCore::InspectorTimelineAgent::internalStart(int const*)::$_1&&&)
<rdar://problem/24427191>
Let me try rolling out r195799 to let the bots check whether it's the culprit over the weekend.
<rdar://problem/24427194>
The rollout fixed this. *** This bug has been marked as a duplicate of bug 153722 ***