Use Profile#getLastUsedProfile() instead of ProfileManager::GetActiveUserProfile() on Android |
||||
Issue descriptionIn its Java->C++ calls, PrefServiceBridge (and other similar bridges) typically obtain the Profile on the C++ side by calling ProfileManager::GetActiveUserProfile(). Instead, they should retrieve the profile on the Java side from Profile#getLastUsedProfile() and pass it to C++, as that method also checks that native initialization has completed. See issue 704025 for more background.
,
Mar 5 2018
msramek@ can this bug be marked as fixed now?
,
Mar 5 2018
No, the change in #1 was just for BrowsingDataBridge. There are plenty of others; especially PrefServiceBridge is likely going to be a large rewrite.
,
Mar 5 2018
I'll take it so it doesn't get forgotten. I have to resolve most of profile-related crashes anyway. I won't have time to work on it till M-67 branch, sorry.
,
Aug 1
,
Sep 3
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Feb 19 2018