|
|
Created:
5 years, 7 months ago by Will Harris Modified:
5 years, 7 months ago CC:
chromium-reviews, darin-cc_chromium.org, jam Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDo not attempt to open a channel to a plugin in Plugin Data Remover if there are no plugins available.
BUG=485886
Committed: https://crrev.com/2327c7044eeabc2e70700ff7f752e4b2e2978657
Cr-Commit-Position: refs/heads/master@{#331168}
Patch Set 1 #
Total comments: 4
Patch Set 2 : code review comments #Patch Set 3 : rebase #Patch Set 4 : signal done doesn't actually signal it's done if there is nothing to do. #Messages
Total messages: 20 (7 generated)
wfh@chromium.org changed reviewers: + bauerb@chromium.org
PTAL - this fixes the issue with the CrOS OOBE
Thank you! I've been meaning to do this for a while (well, I've been meaning to do this at some point, then forgot about it...) https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... File content/browser/plugin_data_remover_impl.cc (right): https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... content/browser/plugin_data_remover_impl.cc:97: OnTimeout(); We should probably call this method OnError() now.
Oh, and LGTM
https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... File content/browser/plugin_data_remover_impl.cc (right): https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... content/browser/plugin_data_remover_impl.cc:97: OnTimeout(); On 2015/05/20 21:48:34, Bernhard Bauer wrote: > We should probably call this method OnError() now. I tried calling OnError() first, but it prints a scary error "Couldn't open plugin channel" which isn't really an error, since having no plugins is not an error... so I went with OnTimeout() without setting is_removing_ which prints nothing. WDYT?
https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... File content/browser/plugin_data_remover_impl.cc (right): https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... content/browser/plugin_data_remover_impl.cc:97: OnTimeout(); On 2015/05/20 21:52:12, Will Harris wrote: > On 2015/05/20 21:48:34, Bernhard Bauer wrote: > > We should probably call this method OnError() now. > > I tried calling OnError() first, but it prints a scary error "Couldn't open > plugin channel" which isn't really an error, since having no plugins is not an > error... so I went with OnTimeout() without setting is_removing_ which prints > nothing. WDYT? Oh, durr. We really only need SignalDone(), so I guess that's what we should call.
most of my time was spent complaining to my officemates about having to use gdb... :) https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... File content/browser/plugin_data_remover_impl.cc (right): https://codereview.chromium.org/1144353003/diff/1/content/browser/plugin_data... content/browser/plugin_data_remover_impl.cc:97: OnTimeout(); On 2015/05/20 21:55:03, Bernhard Bauer wrote: > On 2015/05/20 21:52:12, Will Harris wrote: > > On 2015/05/20 21:48:34, Bernhard Bauer wrote: > > > We should probably call this method OnError() now. > > > > I tried calling OnError() first, but it prints a scary error "Couldn't open > > plugin channel" which isn't really an error, since having no plugins is not an > > error... so I went with OnTimeout() without setting is_removing_ which prints > > nothing. WDYT? > > Oh, durr. We really only need SignalDone(), so I guess that's what we should > call. yes. good plan.
wfh@chromium.org changed reviewers: + creis@chromium.org
looking for an OWNER el gee tee em please
LGTM!
The CQ bit was checked by wfh@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from bauerb@chromium.org Link to the patchset: https://codereview.chromium.org/1144353003/#ps20001 (title: "code review comments")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1144353003/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by wfh@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from bauerb@chromium.org, creis@chromium.org Link to the patchset: https://codereview.chromium.org/1144353003/#ps60001 (title: "signal done doesn't actually signal it's done if there is nothing to do.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1144353003/60001
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/2327c7044eeabc2e70700ff7f752e4b2e2978657 Cr-Commit-Position: refs/heads/master@{#331168} |