Screen Name Entirely Too Accurate
As if I were not "Always Confused", now I am always confused....
1. I set the FF config option to force FF to export my bookmarks as an html file; that resulted in bookmarks.html, 914 KB.
2. I then ran AM-Deadlink against bookmarks.html, which indicated that I have 951 bookmarks.
3. My places.sqlite file is shown as 15,392 KB.
4. I next deleted places.sqlite, bookmarkbackups and localstore.rdf. Doing that, plus having created a new bookmarks.html file, forces FF 3 to create a new places.sqlite file when FF is restarted.
5. Restarted FF; the new places.sqlite file is 15,392 KB, but there is only one .json file in the new bookmarkbackups folder of course.
6. I then read Ivan1981's comment about running Spybot with FF3 also running, so I started Spybot, told it to check. This time, when Spybot got to Firefox bookmarks, the Spybot process ended almost instanteously.
[In the line of being Always Confused, as I was writing this brilliant missive, I realized that I might not have deleted bookmarks.html. I'm going to do that, restart FF, rerun Spybot, report the result. (This saves me from copying this, closing FF, restarting, etc.; easier to just confuse myself further...).
As Threatened, I Have Returned.
The forum software would not allow me to post the wonderful verbiage I had added to my previous missive, so herewith enclosed please find whatever it is that is enclosed:
A. I deleted the bookmarks.html file, restarted FF, and reran S&D. When the S&D process neared the end, I watched the S&D status bar carefully, and determined that the reason for the nearly instantaneous completion was due to S&D completely skipping the in-use FF3 profile. S&D did scan the places.sqlite file in my other profile; that places file is only 144 KB, which would account for S&D scanning it so quickly.
B. I then closed FF and reran S&D; when it got to the places.sqlite file for my normally-used profile, S&D again became so slow that I terminated the process.
My conclusion is that S&D has a problem scanning .sqlite files, that problem being directly (and understandably) related to the size of such files.