RESOLVED FIXED 138263
Change the ScrollingThread code to use RunLoop::main().dispatch() rather than callOnMainThread(), which has Obj-C overhead 
https://bugs.webkit.org/show_bug.cgi?id=138263
Summary Change the ScrollingThread code to use RunLoop::main().dispatch() rather than...
Simon Fraser (smfr)
Reported 2014-10-31 15:20:23 PDT
Change the ScrollingThread code to use RunLoop::main().dispatch() rather than callOnMainThread(), which has Obj-C overhead
Attachments
Patch (3.27 KB, patch)
2014-10-31 15:21 PDT, Simon Fraser (smfr) 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Simon Fraser (smfr)
Comment 1 2014-10-31 15:21:34 PDT
Created attachment 240759 [details] Patch
Simon Fraser (smfr)
Comment 2 2014-10-31 15:22:09 PDT
rdar://problem/18833601
Geoffrey Garen
Comment 3 2014-10-31 15:23:56 PDT
Comment on attachment 240759 [details] Patch Should we change the implementation of callOnMainThread to use RunLoop::main().dispatch?
Simon Fraser (smfr)
Comment 4 2014-10-31 15:30:11 PDT
(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.
WebKit Commit Bot
Comment 5 2014-10-31 16:14:47 PDT
Comment on attachment 240759 [details] Patch Clearing flags on attachment: 240759 Committed r175433: <http://trac.webkit.org/changeset/175433>
WebKit Commit Bot
Comment 6 2014-10-31 16:14:51 PDT
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.