Bug 105637

Summary: REGRESSION(r138237): Regresses web inspector's editor performance. (Requested by pfeldman on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED FIXED    
Severity: Normal CC: pfeldman
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 105429    
Attachments:
Description Flags
ROLLOUT of r138237 none

WebKit Review Bot
Reported 2012-12-21 08:28:40 PST
http://trac.webkit.org/changeset/138237 broke the build: Regresses web inspector's editor performance. (Requested by pfeldman on #webkit). This is an automatic bug report generated by the sheriff-bot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests case pain. "Only you can prevent forest fires." -- Smokey the Bear
Attachments
ROLLOUT of r138237 (3.58 KB, patch)
2012-12-21 08:29 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2012-12-21 08:29:20 PST
Created attachment 180524 [details] ROLLOUT of r138237 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the rollout will be successful. This process takes approximately 15 minutes. If you would like to land the rollout faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
WebKit Review Bot
Comment 2 2012-12-21 08:48:21 PST
Comment on attachment 180524 [details] ROLLOUT of r138237 Clearing flags on attachment: 180524 Committed r138383: <http://trac.webkit.org/changeset/138383>
WebKit Review Bot
Comment 3 2012-12-21 08:48:24 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.