If SQLite is crashing due to corruption in the database, we should be
able to get Dr Hipp to help fix it. But we'd need a repeatable case
to send to him. If we had a database which demonstrated this, I could
certainly see about crafting a simplified database of example data to
replicate the prob
Out of curiosity, when you had copies of a corrupt database, did you try
running sqlite's "pragma integrity_check" sql command on them? If so did it
actually find the problems? For a desktop application at a previous company
I was at, we wrote some code that would occasionally save a backup copy of
On Fri, Mar 6, 2009 at 9:33 AM, Brett Wilson wrote:
> Getting the database has helped in a few cases where it turned out some
> assumptions were being violated, but if the sqlite data structures are
> corrupted, getting the DB has never been helpful to diagnose the root cause.
>
> It might help u
One thing that would help is if some of the users who are running into
this would be willing to share their whole profile with us.
While our best guess is that this is sqlite corruption, we don't know
for sure. Even if it is sqlite corruption, having the specific db
might help us figure out how
Hello, thanks for your reply.
I understand about User Agreement between the user and Google, I thought a
Stack trace would help a little to figure out what is really going on.
People are getting really annoyed (on the forums) since their browser
quickly crashes when they open it, after couple secon
Maybe we could also make Chromium more resilient against corrupted profile?
We already have tools like stress_cache. There could be another tool, which
would launch Chrome, randomly perform several actions, close it, randomly
corrupt profile and launch it again. But I don't know for example how sql
I suspect this is like crashes due to memory corruption: It won't do much
good to stare at the call stack at the time corruption was detected; we need
to know the stack at the time corruption occurred (assuming this is Chrome
that is corrupting the profile).
For memory corruptions we have gflags; I
Mohamed,
I'm glad to see your interest in tackling this problem.
Unfortunately, that data is collected under an agreement between the user
and Google, so we cannot share the dumps. It's OK to share the stack traces,
which have no personally identifying information, but I'm not sure we can
even fi
