Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(205)

Issue 1135183002: Ensure EasyUnlockPrivateAPI factory is initialized on start up. (Closed)

Created:
5 years, 7 months ago by Tim Song
Modified:
5 years, 7 months ago
CC:
chromium-reviews, chromium-apps-reviews_chromium.org, extensions-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Ensure EasyUnlockPrivateAPI factory is initialized on start up. BUG=487486 Committed: https://crrev.com/3b7173a8d1b6c445ae93f616fe742ddf57efd8c4 Cr-Commit-Position: refs/heads/master@{#329974}

Patch Set 1 #

Patch Set 2 : move EasyUnlockPrivateAPI out of api namespace #

Patch Set 3 : fix unit test #

Patch Set 4 : pass tests #

Total comments: 2

Patch Set 5 : uncomment #

Messages

Total messages: 20 (7 generated)
Tim Song
5 years, 7 months ago (2015-05-12 01:41:29 UTC) #2
scheib
LGTM api:: namespace stands out here doesn't it. BUG number on description, please.
5 years, 7 months ago (2015-05-12 03:15:27 UTC) #3
Tim Song
I moved the EasyUnlockPrivateAPI out of the api namespace to be consistent.
5 years, 7 months ago (2015-05-13 02:33:13 UTC) #4
scheib
LGTM still
5 years, 7 months ago (2015-05-13 04:13:52 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1135183002/40001
5 years, 7 months ago (2015-05-14 17:28:18 UTC) #8
commit-bot: I haz the power
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_chromeos_ozone_rel_ng/builds/17954)
5 years, 7 months ago (2015-05-14 18:31:13 UTC) #10
Tim Song
+tbarzic@ Toni, I lazily intialize the EasyUnlockPrivateCryptoDelegate because DBusManager is not created when the API ...
5 years, 7 months ago (2015-05-14 20:18:04 UTC) #12
tbarzic
lgtm https://codereview.chromium.org/1135183002/diff/60001/chrome/browser/extensions/browser_context_keyed_service_factories.cc File chrome/browser/extensions/browser_context_keyed_service_factories.cc (right): https://codereview.chromium.org/1135183002/diff/60001/chrome/browser/extensions/browser_context_keyed_service_factories.cc#newcode98 chrome/browser/extensions/browser_context_keyed_service_factories.cc:98: // extensions::EasyUnlockPrivateAPI::GetFactoryInstance(); remove comment
5 years, 7 months ago (2015-05-14 20:22:45 UTC) #13
Tim Song
https://codereview.chromium.org/1135183002/diff/60001/chrome/browser/extensions/browser_context_keyed_service_factories.cc File chrome/browser/extensions/browser_context_keyed_service_factories.cc (right): https://codereview.chromium.org/1135183002/diff/60001/chrome/browser/extensions/browser_context_keyed_service_factories.cc#newcode98 chrome/browser/extensions/browser_context_keyed_service_factories.cc:98: // extensions::EasyUnlockPrivateAPI::GetFactoryInstance(); On 2015/05/14 20:22:44, tbarzic wrote: > remove ...
5 years, 7 months ago (2015-05-14 22:01:07 UTC) #14
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1135183002/80001
5 years, 7 months ago (2015-05-14 23:17:16 UTC) #17
commit-bot: I haz the power
Committed patchset #5 (id:80001)
5 years, 7 months ago (2015-05-14 23:37:30 UTC) #18
commit-bot: I haz the power
Patchset 5 (id:??) landed as https://crrev.com/3b7173a8d1b6c445ae93f616fe742ddf57efd8c4 Cr-Commit-Position: refs/heads/master@{#329974}
5 years, 7 months ago (2015-05-14 23:38:12 UTC) #19
pneubeck (no reviews)
5 years, 7 months ago (2015-05-15 08:55:06 UTC) #20
Message was sent while issue was closed.
On 2015/05/14 20:18:04, Tim Song wrote:
> +tbarzic@
> 
> Toni, I lazily intialize the EasyUnlockPrivateCryptoDelegate because
DBusManager
> is not created when the API factories are created. Let me know if this looks
> okay to you.

I looked further into this, as it was not clear to me _why_ the API class is
affecting profile creation. If the API object is created lazily, i.e. when the
API is used the first time, this should not have any conflict with dbus.

It turns out, that the BrowserContextKeyedAPIFactory is by default created
during profile creation, which IMO is just wrong: see
https://code.google.com/p/chromium/codesearch#chromium/src/extensions/browser...

APIs should be lazily initialized on first use. I'll through out a CL to fix
this default.

Powered by Google App Engine
This is Rietveld 408576698