Make sure ProcessThrottler is always holding a ProcessAssertion for its child process

• Component: WebKit2
• Status: RESOLVED FIXED

[Chris Dumez]

Make sure ProcessThrottler is always holding a ProcessAssertion for its child process. Previously, when changing the assertion type (e.g. when going from background to foreground) we would release the previous assertion and then take the new one.
RunningBoard developers recommend that we wait until the new ProcessAssertion is taken before we release the previous one to avoid churn. It is also important we always hold a ProcessAssertion at all times for the child process because the child process may exit otherwise.

[Chris Dumez]

Created attachment 414386 [details]
Patch

[Geoffrey Garen]

Comment on attachment 414386 [details]
Patch

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

r=me

> Source/WebKit/UIProcess/ProcessThrottler.cpp:132
> +    // Keep the previous assertion around until after the new one has been created so that we always have
> +    // hold a process assertion for the process.

have hold => hold

[Chris Dumez]

Created attachment 414388 [details]
Patch

[EWS]

Committed r269934: <https://trac.webkit.org/changeset/269934>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 414388 [details].

[Radar WebKit Bug Importer]

<rdar://problem/71512123>