Closed Bug 651505 Opened 15 years ago Closed 15 years ago

Freeze when open the history library and expand "History" in menu

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jiangiang91, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110420 Firefox/6.0a1 Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110420 Firefox/6.0a1 When I click nightly button and mouse over the "History", the browser will freeze for a while and then when I recover from freeze state, click "show all history", the browser will freeze again I also tried in safe mode and the result remain same. Reproducible: Always Steps to Reproduce: 1.click nighly button or press alt then click history 2.expand the history 3. Actual Results: The browser will freeze for half minutes.
Is your Issue reproducible in Safe-Mode? https://support.mozilla.com/en-US/kb/Safe+Mode
Version: unspecified → 4.0 Branch
Yes, reproducible.
Version: 4.0 Branch → Trunk
I cannot reproduce the issue on: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110420 Firefox/6.0a1 Is it reproducible also with a clean (new) firefox profile: http://support.mozilla.com/en-US/kb/Profiles Could you attach a screen video of the issue? Remaining Unconfirmed
http://www.youtube.com/watch?v=ahZ3HlLG61w here is the video i recorded.
In reply to Comment 4. According to the video there is definitely an issue there. But can you also try on a fresh (new) clean profile (no bookmarks, no history, no add-ons) ? See if the you can still reproduce the issue? http://support.mozilla.com/en-US/kb/Profiles Would it be related to some website in the current history?
Could be a database problem, how big is your database? Could you please open the Error Console and evaluate this code: Components.utils.import("resource://gre/modules/PlacesDBUtils.jsm");PlacesDBUtils.checkAndFixDatabase(); Then paste here the output you should get in the console after some seconds.
[ Places Maintenance ] > Integrity check + The database is sane > Coherence check + The database is coherent > Orphans expiration + Database cleaned up > Vacuum Initial database size is 10240 KiB + The database has been vacuumed Final database size is 10240 KiB > Statistics Database size is 10240 KiB user_version is 11 page_size is 32768 cache_size is 3908 journal_mode is wal synchronous is 1 History can store a maximum of 64042 unique pages Table moz_places has 1515 records Table moz_historyvisits has 3556 records Table moz_inputhistory has 100 records Table moz_bookmarks has 65 records Table moz_bookmarks_roots has 5 records Table moz_keywords has 0 records Table sqlite_sequence has 0 records Table moz_favicons has 152 records Table moz_annos has 0 records Table moz_anno_attributes has 7 records Table moz_items_annos has 21 records Table sqlite_stat1 has 15 records Index sqlite_autoindex_moz_inputhistory_1 Index sqlite_autoindex_moz_bookmarks_roots_1 Index sqlite_autoindex_moz_keywords_1 Index sqlite_autoindex_moz_favicons_1 Index sqlite_autoindex_moz_anno_attributes_1 Index moz_places_faviconindex Index moz_places_hostindex Index moz_places_visitcount Index moz_places_frecencyindex Index moz_places_lastvisitdateindex Index moz_historyvisits_placedateindex Index moz_historyvisits_fromindex Index moz_historyvisits_dateindex Index moz_bookmarks_itemindex Index moz_bookmarks_parentindex Index moz_bookmarks_itemlastmodifiedindex Index moz_places_url_uniqueindex Index moz_places_guid_uniqueindex Index moz_bookmarks_guid_uniqueindex Index moz_annos_placeattributeindex Index moz_items_annos_itemattributeindex Trigger moz_bookmarks_beforedelete_v1_trigger Here is the result.
After executed that code, it look like no problem anymore.
I suspect one of your indices was out of order, this utils also reindex the database if needed. As it is I'd solve the bug as WFM, but feel free to reopen if you should notice the issue again.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Thank you so much. But another thing I want to mention is when I reformat the PC two times(for testing purpose), I sync my firefox with the server data, and this was happened at two times I fresh install firefox and sync.
You mean this bug could have been caused by Sync?
I have no idea but the problem had came after I sync my firefox and the history had been loaded.
Hi, I'd found that after I fresh install my Firefox, and sync data to my PC, this problem will happen again unless i execute that code above.
when you see the problem, zip the places.sqlit file and send it to me by mail.
You need to log in before you can comment on or make changes to this bug.