![]() Other program, actions may interfere with /safebrowsing/ No updates need is obviously wrong, if already initialized is correct, nothing ever actually completes, so you're never updated One likely would even be aware anything was amiss particularly, unless something odd happened, like observing the file dates & saying, "hey, that doesn't look right"ī (thanks frg), starts with : needsUpdate:, guessing has to do with nextupdatetime's '1' setting, then it reports :no updates needed or already initialized: In those cases, one could perpetually be using stale data Not all non-updating /safebrowsing/ issues result in slow browser startup, high CPU usage Having changed .nextupdatetime to '1' (or reset its value), it may or may not update its value to current - depending - though thinking that in most instances it will, though once bad, you don't actually get updates It appears that once a /safebrowsing/ goes bad, it will not update (Likewise, there is nothing external, like antivirus, that would be interfering in any way.) I'll will note, that my Profile are not in places like %appdata%, but where I specify, so in that regard, /cache/ & /safebrowsing/ are in my Profile Folder itself - not that I would expect any difference in that regard. In all cases, safebrowsing is enabled, prefs are at their defaults. Nor do I know how to attempt to force an update? I don't know how often the files are expected to update, whether week old (1/15, at the time) is stale? Other Profile - file dates of 12/13 or 1/15, again exceptions being the "test" files, dated current (1-22-2018). One Profile - file dates of Nov/Dec 2017, exceptions being the "test" files, dated current (at the time). Judging by file dates (also available through the above link, full zips), I'm going to say that on the Profiles in question, they are not updating, have stopped updating. ![]() > Does the problem go away after the phishing list gets updated or does it persist forever once the profile gets into this bad state? You'd also want to monitor CPU usage & duration during startup. Setting the home page to a web page, say, makes it easier to "see" the issue. Starting FF in Safe Mode bypasses the issue. No idea what expected dates of the files in the safebrowsing directory should be, if files from 01-15-2018 (or earlier) would be considered outdated? No idea what caused Safebrowsing to go "bad", but it has gone bad on at least two of my Profiles. Though the mozillazine thread seems to indicate that FF 57 is also affected.) Observed in FF 52.6 & SeaMonkey 2.49.1, WinXP. Note that the Profile is slow, 20+ seconds on a relatively slow computer, to load the "home page" (regardless of what that page may or may not be) & during that time CPU using is high, ~100% of 1 core. ![]() Replace existing Profile/safebrowsing/ directory contents with that contained in safebrowsing_FF_52-BAD.zip A Bad 'Safebrowsing' Causes High CPU Usage & Slow Startup Times
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |