886064 - Aurora doesn't start after June 19 update (constant read-access to places.sqlite)

Status: RESOLVED INVALID

(Toolkit :: Places, defect)

Description

[[:philipp]]

Since the June 19 update, Firefox Aurora won't launch for my configuration (I'm using the german l10n builds on a win7 64bit machine). 
The firefox.exe process is just sitting in the task manager with a fixed amount of RAM and using all the CPU of one core, but no visible interface will show up. 
When inspecting what's going on with the process monitor utility, it is apparent, that firefox.exe is constantly accessing the places.sqlite file in the profile folder.

I can solve the issue by deleting the places.sqlite file or recreate the issue by placing the file in a otherwise fresh profile.

last working version: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-06-17-00-40-17-mozilla-aurora-l10n/
first failing version: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-06-19-00-40-18-mozilla-aurora-l10n/ 
(there doesn't seem to be a german aurora win32 build for june 18)

I'd be willing to provide my bookmarks/history file in a non-public way if it can help in investigating the issue...

Comment 1

[[:Aleksej]]

https://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2013-06-16+23%3A00&enddate=2013-06-19+00%3A40%3A18

Comment 2

[[:philipp]]

thank you Aleksej, i'm not sure but when it's affecting aurora is this the right pushlog?: http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?startdate=2013-06-16+23%3A00&enddate=2013-06-19+00%3A40%3A18

by going trough the bugs from that time spam it seems that Bug 769348 introduces a new schema for the places library & does perform some migration work, which looks like a probable cause for the issue i'm experiencing...

Comment 3

[[:Aleksej]]

(In reply to philipp from comment #2)
> http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?startdate=2013-06-
> 16+23%3A00&enddate=2013-06-19+00%3A40%3A18

Oh, sorry.  This list is much better. :-)

> Bug 769348

Posted a comment there.

Comment 4

[Marco Bonardo [:mak]]

I'd like to look at the database to see what's up, I suspect something is wrong in it. Could you please mail it to me privately for debugging?

Comment 5

[[:philipp]]

thanks marco, i've uploaded the places.sqlite file to the filelocker of my university - an email should have been sent out to your address, which contains the link to access it...

Comment 6

[Marco Bonardo [:mak]]

Thanks, I just downloaded it, will see if I can figure the issue.

Comment 7

[Marco Bonardo [:mak]]

Assigned per investigation.

Comment 8

[Marco Bonardo [:mak]]

Looks like you database is missing a lot of indices, basically all of the indices on moz_places table...

Did you edit this database manually, or by chance dropped the moz_places table, or used a third party tool to cleanup your history?

Comment 9

[Marco Bonardo [:mak]]

I suggest you to delete your places.sqlite and let Firefox generate a new one, it should restore your bookmarks from a json file. Unfortunately this will lose history but that's the safer way to have a proper database.

The alternative is to run these queries on the db through an external tool, but I cannot guarantee anything about future of it, since by removing a table on the db a lot of referential integrity has been compromised:
CREATE INDEX moz_places_visitcount ON moz_places (visit_count);
CREATE UNIQUE INDEX moz_places_url_uniqueindex ON moz_places (url);
CREATE INDEX moz_places_lastvisitdateindex ON moz_places (last_visit_date);
CREATE INDEX moz_places_hostindex ON moz_places (rev_host);
CREATE UNIQUE INDEX moz_places_guid_uniqueindex ON moz_places (guid);
CREATE INDEX moz_places_frecencyindex ON moz_places (frecency);
CREATE INDEX moz_places_faviconindex ON moz_places (favicon_id);

Comment 10

[Marco Bonardo [:mak]]

resolving since it's not a Firefox bug, somehow the moz_places table has been dropped and recreated, we don't make such operations in the product.

If you have any idea how that may have happened, it may help other users.

Comment 11

[[:philipp]]

i did resolve it in the meantime anyway by importing the history to chrome, removing the places.sqlite file & importing the data back to firefox afterwards.

i think the profile where it happened is quite old and used with aurora versions - it may well be that i've once used an addon that performs some kind of database "cleanup", but i cannot attribute it to anything specific anymore...

just wanted to report the issue originally in order to ensure that it is not something endemic that might affect many users - thanks for looking into it!