627915 - some frequently visited urls are not showing up in location bar

Status: RESOLVED INCOMPLETE

(Firefox :: Bookmarks & History, defect)

Description

[Shannon Prior]

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b9) Gecko/20100101 Firefox/4.0b9

All of the sudden all of my awesome bar history was gone. There are a few websites that still come up in the awesome bar history - although I have not visited these sites for months. Most frequently visited websites that I go to everyday are not appearing at all. Nothing was downloaded except for Adobe Reader today.

Comment 1

[Marco Bonardo [:mak]]

Hi, Gavin told me about this unfortunate problem.

Did you downgrade from b9 to firefox 3.6? and if so are you able to tell me to which 3.6.x revision?

Comment 2

[Shannon Prior]

Yes, I switched between beta 9 and 3.6.11 

Gavin was able to fix my problem (THANK GOODNESS ;)

Comment 3

[Marco Bonardo [:mak]]

hm, sounds weird, 3.6.11 should be the first good version that does NOT cause this issue :\ Any version of Firefox using sqlite 3.7.x+ should be fine indeed.

Btw, to exclude the worst case I tried opening a profile made with trunk on 3.6.11 and it works fine. I also tried creating a profile with 3.6.11, opening it with trunk, then reopening with 3.6.11, it is still working fine.

A possible edge case I could think of, is that you had 3.6.10 with a 3.6.11 update available, so downgrading happened on 3.6.10 but immediately 3.6.11 was applied... but this sounds not that probable :\

Comment 4

[Shawn Wilsher :sdwilsh]

(In reply to comment #3)
> A possible edge case I could think of, is that you had 3.6.10 with a 3.6.11
> update available, so downgrading happened on 3.6.10 but immediately 3.6.11 was
> applied... but this sounds not that probable :\
I don't think that would be the case because the update would happen before we open the profile (I think).

Comment 5

[Marco Bonardo [:mak]]

I'm sorry, but I think we don't have enough data to guess or debug what happened here, if we should hit another case like this we'll need a copy of the "corrupt" database.
Also luckily this incidents with not compatible downgrades/upgrades should be rare.