Commit cd54ad1b authored by Andrew Grieve's avatar Andrew Grieve Committed by Commit Bot

Remove obsolete calls to SequenceTaskRunner.disableLifetimeCheck()

SequenceTaskRunner no longer require lifetime checks.

Bug: 877963
Change-Id: I6d779e47b4ded24f38f6a9c29aaddda102a13bbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602152Reviewed-by: default avatarSam Maier <smaier@chromium.org>
Reviewed-by: default avatarBo <boliu@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#658353}
parent 0001b828
......@@ -62,12 +62,6 @@ public final class AwBrowserProcess {
private static FileLock sExclusiveFileLock;
private static String sWebViewPackageName;
// TODO(ksolt): This is a temporary solution to avoid lifetime check errors.
// Will be fixed after we decide how to handle the destruction of static TaskRunners.
static {
sSequencedTaskRunner.disableLifetimeCheck();
}
/**
* Loads the native library, and performs basic static construction of objects needed
* to run webview in this process. Does not create threads; safe to call from zygote.
......
......@@ -138,10 +138,6 @@ public class ShareServiceImpl implements ShareService {
private static final TaskRunner TASK_RUNNER =
PostTask.createSequencedTaskRunner(TaskTraits.USER_BLOCKING);
static {
TASK_RUNNER.disableLifetimeCheck();
}
public ShareServiceImpl(@Nullable WebContents webContents) {
mActivity = activityFromWebContents(webContents);
}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment