Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

After the upgrade from version 5 to 6, "clear recent history" hangs indefinetly.

  • 3 replies
  • 3 have this problem
  • 3 views
  • Last reply by cor-el

more options

If I attempt to manually clear history, I can do that one site at a time. That takes about 5 seconds. If I attempt to clear > 20 sites, sometimes it works (after about a 3-5 minute wait), and sometimes it hangs (a time period, which, IMO, exceeds 20 minutes).

There was a site which simply would not clear (from last July) no matter what I did. I believe it was "The Other McCain", but I can't swear to that, and it no longer appears in my list of history options.

If I attempt to manually clear history, I can do that one site at a time. That takes about 5 seconds. If I attempt to clear > 20 sites, sometimes it works (after about a 3-5 minute wait), and sometimes it hangs (a time period, which, IMO, exceeds 20 minutes). There was a site which simply would not clear (from last July) no matter what I did. I believe it was "The Other McCain", but I can't swear to that, and it no longer appears in my list of history options.

All Replies (3)

more options

How many history items do you see in the History Manager (Library)?

  • History > Show All History

A possible cause is a problem with the file places.sqlite that stores the bookmarks and the history.

more options

Thanks for the pointers!

From the link, it was suggested I rename "places.sqlite" to "places.sqlite.corrupt". I already had one of those -- dated May 5th of this year. I deleted that, renamed places.sqlite to places.sqlite.corrupt, then tried "Tools->Clear Recent History->Everything".

Seemed to work OK. I'll know more after I build up some history and attempt to clear everything again.

An alternative solution which involved downloading a command-line SQL program seemed problematic, especially because it suggested using a SQL statement involving "DELETE WHERE LIKE". Since I'm not sure what I'm looking for to begin with, "LIKE" didn't sound very good.

Since I wanted to clear everything anyway, just deleting (or renaming) the file seemed the most sensible.

Which, of course, begs the question: why would you want to keep and potentially restore a ".corrupt" file?

more options

You're welcome