Stop leaking an XPC boost message to XPC services on builds where RunningBoard is able to give the right priorities to our XPC services based on the type of RunningBoard assertion is being held. There is no behavior change for the Network/WebContent processes since those were blocklisted in RunningBoard (Turning on the RB_full_manage_WK_jetsam feature flag gives us the default RunningBoard behavior without blocklisting). However, this allows the new GPUProcess to move to IDLE jetsam band when homing out of MobileSafari, which makes the GPUProcess eligible for the freezer. Previously, the leaked boost message would keep the GPUProcess in a higher jetsam band.
Created attachment 415250 [details]
Comment on attachment 415250 [details]
Committed r270542: <https://trac.webkit.org/changeset/270542>
All reviewed patches have been landed. Closing bug and clearing flags on attachment 415250 [details].
Reverted r270542 for reason:
Seems to have regressed perf benchmarks
Committed r270632: <https://trac.webkit.org/changeset/270632>
Committed r270969: <https://trac.webkit.org/changeset/270969>
Reverted r270969 for reason:
Regressed MotionMark with GPUProcess enabled
Committed r271017: <https://trac.webkit.org/changeset/271017>
Created attachment 417056 [details]
Committed r271189: <https://trac.webkit.org/changeset/271189>
All reviewed patches have been landed. Closing bug and clearing flags on attachment 417056 [details].