New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 709072 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 719002
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Ensure reputation-cache doesn't grow too large

Project Member Reported by nparker@chromium.org, Apr 6 2017

Issue description

Let's monitor the size of data we're adding to content-settings, for phishguard pings, and find a better place if they turn out to be large.  

brettw's suggestion on the doc:
"I'd say If this is more than a couple of KB of data total, we should probably find a better place than the prefs for it to live on disk. The prefs are a pretty inefficient way to store data and makes everything slower. It doesn't seem like you need the "synchronously available at startup" properties of prefs. The main place to put random stuff like this is the WebDatabase (components/webdata) which is where things like autofill data are stored."
 
Cc: -jialiul@chromium.org
Owner: jialiul@chromium.org
Status: Assigned (was: Untriaged)
Labels: SafeBrowsing-Triaged
In addition, we can clean up the expired verdict periodically or during browser shutdown.
Cc: brettw@chromium.org
Mergedinto: 719002
Status: Duplicate (was: Assigned)

Sign in to add a comment