|
|
Chromium Code Reviews
DescriptionReduce use of ExecutionContextTask in core/
ExecutionContextTask is deprecated in favor of WTF::Closure.
This patch replaces ExecutionContextTask::postTask
with WebTaskRunner::postTask in some of the occurrences.
BUG=625927
Review-Url: https://codereview.chromium.org/2680013008
Cr-Commit-Position: refs/heads/master@{#449557}
Committed: https://chromium.googlesource.com/chromium/src/+/5fbd15767912e9546dab933ba377c8ab68a5b3c8
Patch Set 1 #Patch Set 2 : Restore instrument #
Total comments: 2
Patch Set 3 : use wrapWeakPersistent to hold ExecutionContext #Patch Set 4 : fix stacktrace #
Total comments: 2
Messages
Total messages: 33 (23 generated)
The CQ bit was checked by yuryu@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by yuryu@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
tzik@chromium.org changed reviewers: + tzik@chromium.org
https://codereview.chromium.org/2680013008/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp (right): https://codereview.chromium.org/2680013008/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp:90: WTF::bind(&runGetAsStringTask, wrapPersistent(context), Could you replace wrapPersistent(context) here with wrapWeakPersistent(context), and add a null check to runGetAsStringTask? On the previous code, ExecutionContext::postTask cancels the posted task when ExecutionContext is destroyed, and the posted task doesn't retain the strong reference to ExecutionContext. I think we should keep previous behavior now.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
yuryu@chromium.org changed reviewers: + nhiroki@chromium.org
https://codereview.chromium.org/2680013008/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp (right): https://codereview.chromium.org/2680013008/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp:90: WTF::bind(&runGetAsStringTask, wrapPersistent(context), On 2017/02/09 12:15:34, tzik wrote: > Could you replace wrapPersistent(context) here with wrapWeakPersistent(context), > and add a null check to runGetAsStringTask? > On the previous code, ExecutionContext::postTask cancels the posted task when > ExecutionContext is destroyed, and the posted task doesn't retain the strong > reference to ExecutionContext. I think we should keep previous behavior now. Done.
The CQ bit was checked by yuryu@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by yuryu@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
yuryu@chromium.org changed reviewers: + haraken@chromium.org
haraken, can you take a look? thanks.
lgtm Regarding CL subject and description, "Worker: " prefix sounds strange because this is not related to worker code (i.e., core/workers). I don't come up with a good alternative... no prefix or "PostTask: "??
Description was changed from ========== Worker: Reduce use of ExecutionContextTask in core/ ExecutionContextTask is deprecated in favor of WTF::Closure. This patch replaces ExecutionContextTask::postTask with WebTaskRunner::postTask in some of the occurrences. BUG=625927 ========== to ========== Reduce use of ExecutionContextTask in core/ ExecutionContextTask is deprecated in favor of WTF::Closure. This patch replaces ExecutionContextTask::postTask with WebTaskRunner::postTask in some of the occurrences. BUG=625927 ==========
deleted the prefix.
LGTM https://codereview.chromium.org/2680013008/diff/60001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp (right): https://codereview.chromium.org/2680013008/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp:88: context, "DataTransferItem.getAsString", callback); Not directly related to this CL, on what tasks do we need to add the inspector instrumentation? Normal postTasks don't have the inspector instrumentation.
https://codereview.chromium.org/2680013008/diff/60001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp (right): https://codereview.chromium.org/2680013008/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/core/clipboard/DataTransferItem.cpp:88: context, "DataTransferItem.getAsString", callback); On 2017/02/10 05:53:14, haraken wrote: > > Not directly related to this CL, on what tasks do we need to add the inspector > instrumentation? Normal postTasks don't have the inspector instrumentation. Conceptually, JS-initiated asynchronous tasks that fires a JS event should use it for better stack trace on the inspector. I think it should be done separately outside of postTask.
The CQ bit was checked by yuryu@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 60001, "attempt_start_ts": 1486708209142210,
"parent_rev": "ae9e1cac379b3eb4c1b78a0092a7c5f863bc891a", "commit_rev":
"5fbd15767912e9546dab933ba377c8ab68a5b3c8"}
Message was sent while issue was closed.
Description was changed from ========== Reduce use of ExecutionContextTask in core/ ExecutionContextTask is deprecated in favor of WTF::Closure. This patch replaces ExecutionContextTask::postTask with WebTaskRunner::postTask in some of the occurrences. BUG=625927 ========== to ========== Reduce use of ExecutionContextTask in core/ ExecutionContextTask is deprecated in favor of WTF::Closure. This patch replaces ExecutionContextTask::postTask with WebTaskRunner::postTask in some of the occurrences. BUG=625927 Review-Url: https://codereview.chromium.org/2680013008 Cr-Commit-Position: refs/heads/master@{#449557} Committed: https://chromium.googlesource.com/chromium/src/+/5fbd15767912e9546dab933ba377... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/chromium/src/+/5fbd15767912e9546dab933ba377... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
