Bug 133038

Summary:

We shouldn't make a ScrollingThread on iOS.

Product:

WebKit

Reporter:

Andreas Kling <kling>

Component:

Layout and Rendering

Assignee:

Andreas Kling <kling>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

kling, simon.fraser, thorton

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Unspecified

OS:

Unspecified

Attachments:

Description	Flags
Patch	sam: review+

Description Andreas Kling 2014-05-17 18:05:23 PDT

<rdar://problem/16947589>

Comment 1 Andreas Kling 2014-05-17 18:07:29 PDT

Created attachment 231643 [details]
Patch

Comment 2 Sam Weinig 2014-05-17 18:57:49 PDT

Comment on attachment 231643 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=231643&action=review

> Source/WebCore/ChangeLog:10
> +        * platform/MemoryPressureHandler.cpp:
> +        (WebCore::MemoryPressureHandler::releaseMemory):

This could use some explanation.  I assume this is the only place where we dispatch the to the scrolling thread still?  Perhaps we should have a proper ENABLE() for this and compile out all the ScrollingThread code.

Comment 3 Andreas Kling 2014-05-17 19:05:57 PDT

Committed r169004: <http://trac.webkit.org/changeset/169004>

Comment 4 Tim Horton 2014-05-18 20:23:31 PDT

This doesn't seem like the right fix. What if we have UI-side compositing turned on on Mac?

Comment 5 Andreas Kling 2014-07-03 23:46:23 PDT

*** Bug 133037 has been marked as a duplicate of this bug. ***