Bug 153721
| Summary: | REGRESSION(195799?): Assertion failures in InspectorTimelineAgent::didCompleteCurrentRecord | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | bburg, graouts, joepeck, mattbaker, nvasilyev, ryanhaddad, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Alexey Proskuryakov
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&&&)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/24427191>
Alexey Proskuryakov
Let me try rolling out r195799 to let the bots check whether it's the culprit over the weekend.
Radar WebKit Bug Importer
<rdar://problem/24427194>
Alexey Proskuryakov
The rollout fixed this.
*** This bug has been marked as a duplicate of bug 153722 ***