New issue
Advanced search Search tips

Issue 790542 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Autofill-Fixit


Sign in to add a comment

AutofillManager is created 3 times in the startup path (NTP)

Project Member Reported by ma...@chromium.org, Nov 30 2017

Issue description

An AutofillManager is created for every RenderFrame [1]. On the NTP that means three managers are created (there's iframes). 

We should:
(1) Reconsider creating AutofillManager for chrome:// pages (these days the NTP is at chrome-search://local-ntp) or their children frames 
(2) Consider lazily creating AutofillManager while keeping a Mojo channel up for the renderer to notify of parsed forms.
(3) Generally avoid expensive AutofillManager initializations (are there any?) and move those to a background task.

Assigning to Roger as low priority item but we should probably mitigate this in M65

[1] https://cs.chromium.org/chromium/src/components/autofill/content/browser/content_autofill_driver_factory.cc?type=cs&q=ContentAutofillDriverFactory::RenderFrameCreated&sq=package:chromium&l=123
 
Cc: ma...@chromium.org
Owner: ma...@chromium.org
mathp, will your change address this or are you only doing the address validator?
Cc: -ma...@chromium.org rogerm@chromium.org

Comment 3 by ma...@chromium.org, May 1 2018

Status: Untriaged (was: Assigned)
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Cc: -vabr@chromium.org
vabr going hobby only -> reducing involvement.
Please contact me directly in urgent matters.

Sign in to add a comment