Closed
Bug 782887
Opened 12 years ago
Closed 10 years ago
Lower peak memory usage of SafeBrowsing updates
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
FIXED
People
(Reporter: gcp, Unassigned)
Details
As seen in the the analysis in https://bugzilla.mozilla.org/show_bug.cgi?id=673470#c126, there is a peak memory usge of 8.4M in SafeBrowsing updates. If we can lower this peak usage without much problems, we should. There is an initial patch here: https://bugzilla.mozilla.org/show_bug.cgi?id=673470#c127 Chromium avoids this issue by using std:deque's: http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/safe_browsing/safe_browsing_store.cc?revision=107415&view=markup
Assignee | ||
Updated•10 years ago
|
Product: Firefox → Toolkit
Reporter | ||
Comment 1•10 years ago
|
||
Much improved by a bunch of other bugs, i.e.: https://bugzilla.mozilla.org/show_bug.cgi?id=995782 https://bugzilla.mozilla.org/show_bug.cgi?id=970981 https://bugzilla.mozilla.org/show_bug.cgi?id=821992
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•