| Summary: | Change the ScrollingThread code to use RunLoop::main().dispatch() rather than callOnMainThread(), which has Obj-C overhead | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> | ||||
| Component: | New Bugs | Assignee: | Simon Fraser (smfr) <simon.fraser> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | andersca, cmarcelo, commit-queue, jamesr, luiz, simon.fraser, thorton, tonikitoo | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Simon Fraser (smfr)
2014-10-31 15:20:23 PDT
Created attachment 240759 [details]
Patch
Comment on attachment 240759 [details]
Patch
Should we change the implementation of callOnMainThread to use RunLoop::main().dispatch?
(In reply to comment #3) > Comment on attachment 240759 [details] > Patch > > Should we change the implementation of callOnMainThread to use > RunLoop::main().dispatch? Probably, but the fix needs to take the iOS WebThread into account. Comment on attachment 240759 [details] Patch Clearing flags on attachment: 240759 Committed r175433: <http://trac.webkit.org/changeset/175433> All reviewed patches have been landed. Closing bug. |