Bug 133094

Summary:

fix assertion failure in PerformanceTiming::responseStart

Product:

WebKit

Reporter:

Alex Christensen <achristensen>

Component:

WebKit Misc.

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

commit-queue

Priority:

Version:

528+ (Nightly build)

Hardware:

Unspecified

OS:

Unspecified

Attachments:

Description	Flags
Patch	none
Patch	none

Description Alex Christensen 2014-05-19 16:48:38 PDT

Sometimes responseStart is still -1 when the timing data from CFNetwork is 0.  This should fix the assertion failure.

Comment 1 Alex Christensen 2014-05-19 16:52:39 PDT

Created attachment 231737 [details]
Patch

Comment 2 Alex Christensen 2014-05-19 17:07:13 PDT

Created attachment 231739 [details]
Patch

Comment 3 Alexey Proskuryakov 2014-05-20 09:52:53 PDT

Comment on attachment 231739 [details]
Patch

Is this covered by any regression tests?

Comment 4 WebKit Commit Bot 2014-05-20 10:30:05 PDT

Comment on attachment 231739 [details]
Patch

Clearing flags on attachment: 231739

Committed r169119: <http://trac.webkit.org/changeset/169119>

Comment 5 WebKit Commit Bot 2014-05-20 10:30:07 PDT

All reviewed patches have been landed.  Closing bug.