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 seconds, when they click on
a tab, etc. All this was resolved by a profile cleanup.
Would it be possibly to do an integrity check if the profile is valid? How
much cost would that add to the run-time of chrome? If we somehow check if
the profile is valid, and as you said, inform the user that it is corrupt,
we can even break it down even further, to find out which section of his
profile is corrupt. That way, we might have a mechanism to attempt fixing it
or wiping it.
I believe adding that small performance cost will make browsing more
enjoyable due to corruption, it never happened to me, and I always cross my
fingers that it does, because I could try and attempt debugging it at my
end.
Thanks!
On Fri, Mar 6, 2009 at 1:20 AM, Mark Larson (Google) <m...@chromium.org>wrote:
> 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 find a set of reports definitely correlated with profile corruption.
> This makes me wonder if we should have an integrity check when we detect
> that the browser crashed in the previous session. It might be useful to
> offer to reset the user's profile or (ideally) drop the parts that are
> corrupt. I'd personally rather drop my entire browsing history to keep my
> saved passwords (and vice versa). The UI would have to be diplomatic.
>
> Maybe some developers who have dealt with corruption issues in the past can
> provide some advice on things we could do to address corruption.
>
> Thanks,
> Mark
>
> On Thu, Mar 5, 2009 at 21:09, Mohamed Mansour <m0.interact...@gmail.com>wrote:
>
>> Hello, on the Google Help Forums, 80-85% of the crashes reported there are
>> due to profile corruptions. What they have to do is run chrome in a new user
>> directory, chrome.exe --user-data-dir=c:\foo, or deleting the local state
>> file.
>> Anyone have any idea what may of caused this? Users who don't know the
>> answer to this problem, usually give up using the browser. Chrome is a great
>> browser, and its sad to see people not using it because of this. If anyone
>> has any crash logs due to this (from user reporting), and since its internal
>> to Google, can you share the stack trace? I would like to spend one weekend
>> taking a look at it.
>>
>> Thanks!
>>
>> >>
>>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
