Corrupted Profile

861 views
Skip to first unread message

PhistucK

unread,
May 26, 2016, 1:43:07 AM5/26/16
to Chromium-dev
I updated from Chrome 50.0.2661.94 to 51.0.2704.63 (congratulations!) and immediately got a corrupted profile message (some feature might not be available).
I do have a lot of many windows open with many tabs, but I always have.

I ran --diagnostics (while Chrome is open) and it stopped at
[FAIL] App dictionaries directory path
       Path provider failure

That was weird. After searching the source code a bit, it looks like it needed a Dictionaries folder alongside chrome.exe. I "worked around" that by creating an empty folder. I ran --diagnostics again (I shut down Chrome first) and this is the result -

[PASS] Operating system supported version
       Windows NT 6.1 SP1

[PASS] Conflicting modules
       No conflicting modules found

[PASS] Install type
       System Level

[PASS] Chrome version test
       51.0.2704.63 m GCB

[PASS] User data path
       Path exists and is writable: 732094364

[PASS] Local state path
       Path exists and is writable: 121341

[PASS] App dictionaries directory path
       Path exists

[PASS] Resources path
       Path exists

[PASS] Available disk space
       Free space: 109661786112

[FAIL] User preferences integrity
       File too big

[FAIL] Local state integrity
       File too big

[PASS] Bookmark file
       File parsed OK

[PASS] Web Data database
       No corruption detected

[PASS] Cookie database
       No corruption detected

[PASS] History database
       No corruption detected

[FAIL] Thumbnails database
       Cannot open DB. Possibly corrupted

[PASS] Database tracker database
       No corruption detected

My session was (fortunately) not lost or anything, I see bookmarks and my settings, history and extensions seems to be fine (some of them could have come from Chrome Sync, but they were immediately available, so I do not think so).

How come the Dictionaries folder went away anyway (and why is that a good reason to stop the diagnostics at that step?)?

After restarting Chrome, the corrupted profile message did not appear again, but I am worried about the results of --diagnostics. Should I be?

Any idea?



PhistucK

Peter Kasting

unread,
May 26, 2016, 1:50:30 AM5/26/16
to PhistucK Productions, Chromium-dev, Shruthi Sreekanta
On Wed, May 25, 2016 at 10:41 PM, PhistucK <phis...@gmail.com> wrote:
After restarting Chrome, the corrupted profile message did not appear again, but I am worried about the results of --diagnostics. Should I be?

I've gotten a number of reports from Googlers internally that I believe boil down to "profile corruption on upgrade to Chrome 51".  I was treating them as one-offs but I'm beginning to think we have a real bug.  Usually things "seem to work" after completely closing all Chrome processes and starting again, but none of these users has provided more in-depth data to evaluate whether there's lasting damage.

Can you tell whether there is still evidence of corruption after your latest restart?

+Shruthi, the desktop release manager for M51, who can decide how to deal with this.

PK

PhistucK

unread,
May 26, 2016, 1:59:04 AM5/26/16
to Peter Kasting, Chromium-dev, Shruthi Sreekanta
I am not sure it is a new thing -
My new tab page shows only one thumbnail, the rest are blank (there are eight boxes, all of them had URLs, but no thumbnails except the first).
I removed all of the eight boxes, reloaded the new tab page and now I have eight blank boxes, without URLs.

I was mainly afraid of the local state and preferences failures, but I guess Chrome just ignores the integrity check and loads them anyway (which might be a bit hackable?).

Note that since I have not run --diagnostics before the update, those failures are not necessarily new.

I do not see any concrete evidence to a corruption otherwise.


PhistucK

PhistucK

unread,
May 26, 2016, 2:33:52 AM5/26/16
to Peter Kasting, Chromium-dev, Shruthi Sreekanta
I started another Chrome instance (a web development profile) and it rendered the windows as completely black. Control + Shift + Q and starting that instance again resolved that.


PhistucK

On Thu, May 26, 2016 at 8:49 AM, Peter Kasting <pkas...@chromium.org> wrote:

Wing-chung Leung

unread,
May 26, 2016, 7:54:51 AM5/26/16
to Chromium-dev
You can inspect the local state and the other file with a JSON tool.

And the thumbnail database is likely a SQLite database.

BTW, I suspect that can be a bug in Windows instead of Chrome.

PhistucK

unread,
May 26, 2016, 8:51:49 AM5/26/16
to Wing-chung Leung, Chromium-dev
Comments inline.


PhistucK

On Thu, May 26, 2016 at 2:54 PM, Wing-chung Leung <lwc...@gmail.com> wrote:
You can inspect the local state and the other file with a JSON tool.

​Well, the error is that the file is too large, so nothing to check there.​

 

And the thumbnail database is likely a SQLite database.

It is a LevelDB to be precise, but it probably refers to Top Site which is an SQLite database indeed. I sent it to Scott who wanted to look into it.​

 

BTW, I suspect that can be a bug in Windows instead of Chrome.

​Too large JSON files sound like a non Windows issue. The SQLite issue... I guess it could be a simple corruption after a sudden restart, yep​.

 

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

Wing-chung Leung

unread,
May 26, 2016, 9:39:58 AM5/26/16
to Chromium-dev
Here's my result. Thumbnail database fails for me as well, but nothing appears to be wrong for me.


[PASS] Operating system supported version
       Windows NT 10.0


[PASS] Conflicting modules
       No conflicting modules found

[PASS] Install type
       User Level

[PASS] Chrome version test
       52.0.2742.0

[PASS] User data path
       Path exists and is writable: 377752976

[PASS] Local state path
       Path exists and is writable: 16318


[PASS] App dictionaries directory path
       Path exists and is writable: 892416

[PASS] Resources path
       Path exists and is writable: 19765775

[PASS] Available disk space
       Free space: 509214048256

[PASS] User preferences integrity
       File parsed OK

[PASS] Local state integrity
       File parsed OK


[PASS] Bookmark file
       File parsed OK

[PASS] Web Data database
       No corruption detected

[PASS] Cookie database
       No corruption detected

[PASS] History database
       No corruption detected

[FAIL] Thumbnails database
       Cannot open DB. Possibly corrupted

[PASS] Database tracker database
       No corruption detected

Finished 17 tests.
Press [enter] to continue

Scott Hess

unread,
May 26, 2016, 9:50:39 AM5/26/16
to lwc...@gmail.com, Chromium-dev
On Thu, May 26, 2016 at 6:39 AM, Wing-chung Leung <lwc...@gmail.com> wrote:
> Here's my result. Thumbnail database fails for me as well, but nothing
> appears to be wrong for me.
<snip>
> [FAIL] Thumbnails database
> Cannot open DB. Possibly corrupted

I think it's a red herring. Diagnostics checks a list of databases by
name, and kThumbnailsFilename is "Thumbnails". But the NTP page
thumbnails moved to "Top Sites" years ago, and the current
"Thumbnails" is a directory containing a leveldb (I don't know what
it's used for). sqlite_diagnostics.cc tries to open the directory as
a SQLite database, and that's going to fail.

-scott

Wing-chung Leung

unread,
May 26, 2016, 9:59:22 AM5/26/16
to Chromium-dev, lwc...@gmail.com


On Thursday, May 26, 2016 at 8:51:49 PM UTC+8, PhistucK wrote:
Comments inline.


PhistucK

On Thu, May 26, 2016 at 2:54 PM, Wing-chung Leung <lwc...@gmail.com> wrote:
You can inspect the local state and the other file with a JSON tool.

​Well, the error is that the file is too large, so nothing to check there.​



 
Just checked the code, the "limit" for Local State is 50KiB, and for pref file is 100KiB. If the size is exceeded, the tests simply doesn't get to run. The bad news is we cannot know if the files are corrupt unless we look at it's actual contents. Anyway, likely another red herring as well.

Scott Graham

unread,
May 26, 2016, 12:28:09 PM5/26/16
to Peter Kasting, PhistucK Productions, Chromium-dev, Shruthi Sreekanta
Potentially related is
https://bugs.chromium.org/p/chromium/issues/detail?id=614753 which
landed on me. I don't really know anything about anything there, but
it's crashing trying to iterate through the last opened profiles.

Shruthi Sreekanta

unread,
May 26, 2016, 4:53:09 PM5/26/16
to Scott Graham, Peter Kasting, PhistucK Productions, Chromium-dev
I see this older ChromeOS issue where the last couple comments sound like a browser profile issue. Can you add your report/log there, if it seems like this might be related? If not, if you (or anybody Peter spoke with) have actionable reports, please do file a separate bug so we can dig in.

Scott Hess

unread,
Jun 7, 2016, 4:37:33 PM6/7/16
to Wing-chung Leung, Chromium-dev
I've removed the SQLite-level check on "Thumbnails", and added checks
on "Top Sites" and "Favicons". So this red herring should go away.

-scott

Will Harris

unread,
Jun 7, 2016, 4:46:38 PM6/7/16
to Peter Kasting, PhistucK Productions, Chromium-dev, Shruthi Sreekanta
The Profile.ProfileError histogram seems to be reported on profile error:


Perhaps this would be a good place to start investigation into any trends?

Will



On Wed, May 25, 2016 at 10:49 PM, Peter Kasting <pkas...@chromium.org> wrote:

--

Albert Bodenhamer

unread,
Jun 9, 2016, 7:42:32 PM6/9/16
to w...@chromium.org, Peter Kasting, afa...@google.com, PhistucK Productions, Chromium-dev, Shruthi Sreekanta

Reply all
Reply to author
Forward
0 new messages