RESOLVED FIXED 178640
[iOS] WebProcess::initializeWebProcess spends ~150ms spinning up AVSystemController on some devices
https://bugs.webkit.org/show_bug.cgi?id=178640
Summary [iOS] WebProcess::initializeWebProcess spends ~150ms spinning up AVSystemCont...
Wenson Hsieh
Reported 2017-10-21 21:55:27 PDT
Optimizing this would improve web process bring-up time on certain devices.
Attachments
Patch (7.32 KB, patch)
2017-10-21 22:12 PDT, Wenson Hsieh
no flags
Wenson Hsieh
Comment 1 2017-10-21 21:58:21 PDT
Wenson Hsieh
Comment 2 2017-10-21 22:12:02 PDT
youenn fablet
Comment 3 2017-10-22 18:45:21 PDT
Comment on attachment 324517 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=324517&action=review > Source/WebKit/WebProcess/WebPage/ios/WebPageIOS.mm:3421 > + NSError *error = nil; Is is usually style for mm file to do "NSError *error" in lieu of CPP like "NSError* error"?
Wenson Hsieh
Comment 4 2017-10-22 18:54:26 PDT
Comment on attachment 324517 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=324517&action=review Thanks for the review! >> Source/WebKit/WebProcess/WebPage/ios/WebPageIOS.mm:3421 >> + NSError *error = nil; > > Is is usually style for mm file to do "NSError *error" in lieu of CPP like "NSError* error"? Correct. It's this rule, in the WebKit style guidelines: <https://webkit.org/code-style-guidelines/#pointers-non-cpp>. Although, it seems a common interpretation of this rule (and an interpretation I personally find more useful :)) is that Objective C objects should have a space between the type and the *, while pointers to C++ and C classes and structs should not have an extra space. FWIW, this appears to be the convention followed here, in WebPageIOS.mm, as well as many other Objective-C++ files in WebKit (e.g. search for "FrameView*" in this file).
WebKit Commit Bot
Comment 5 2017-10-22 19:20:23 PDT
Comment on attachment 324517 [details] Patch Clearing flags on attachment: 324517 Committed r223827: <https://trac.webkit.org/changeset/223827>
WebKit Commit Bot
Comment 6 2017-10-22 19:20:24 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.