Make chrome crash reporting simpler for enduser.

[Pintu]

The Chrome Crash bug reporting process is really complicated. For a
end user like some who knows nothing about coding becomes really
tough. What finally the end user does is uninstall the chrome and
install something like SAFARI, MOZILLA etc.

The steps given by chrome are as belows . it not only looks lengthy
even a person like me would surely try to avoid this steps. Is there
any other way to make this thing easier..

Reporting a Crash Bug
If you are planning to report a crash bug, please make sure you
include enough information for debugging purpose.
•Make sure you have the latest Chrome version (on Windows go to Chrome
Options->About Google Chrome)
•Try to get exact reproducible steps for the crash, if possible.
•Try to also provide more debugging info by either reporting the crash
directly to Google or collecting a dump file.
Windows
•If possible, enable crash reporting in Google Chrome Options - Chrome
Options (wrench menu) -> Options -> Under the Hood -> select 'Help
make Google Chrome better by automatically sending usage statistics
and crash reports to Google'.
•If crash reporting is enabled and a crash happens, Google Chrome will
log a Windows event with a crash id. Open Windows Event Viewer
(Windows Start -> Run -> eventvwr.exe) and look for an event under
Application logs from Source 'Chrome'. This event will have a text
similar to 'Crash uploaded. Id=nnnnnnnnn'. Report this id in the crash
bug that you file. The mini dump file that gets uploaded is also saved
locally on your machine (%LOCALAPPDATA%\Google\CrashReports\Chrome-
last.dmp on Window Vista and higher, %USERPROFILE%\Local Settings
\Application Data\Google\CrashReports\Chrome-last.dmp on Windows XP).
•In Chrome profile directory (%LOCALAPPDATA%\Google\Chrome\User Data
on Window Vista and higher, %USERPROFILE%\Local Settings\Application
Data\Google\Chrome\User Data on Windows XP) there is a file called
Local State. Open this file in any text editor and search for
'client_id'. If you find this string in the file, please copy that
line and paste in your bug description.
•If you haven't enabled crash reporting OR you do not see the event in
Windows Event Viewer OR if you are using Chromium (which doesn't have
the option of reporting crashes), see the steps below on how to
capture a minidump file using windbg.exe.
◦If you do not already have windbg.exe, download it from Microsoft
website
◦Run WinDbg with this command - windbg.exe -o <full path to
chrome.exe>
◦Keep hitting F5 until you hit an exception (Access violation or some
other error) or until Chrome window comes up
◦If Chrome Window opens successfully, try to reproduce the crash. When
crash happens you should see an exception reported in WinDbg (Access
violation or some other error)
◦After the exception has been reported save the dump file by typing
this exact command in WinDbg command .dump C:\chrome.dmp (do not
forget '.' at the beginning)
◦Once the dump file has been successfully saved, compress this dump
file, upload it somewhere and post the link to the file along with the
bug description.

[John Blake]

---------- Forwarded message ----------
From: John Blake <vk6...@gmail.com>
Date: Tue, 11 Jan 2011 19:15:08 +0800
Subject: Re: [chromium-discuss] Make chrome crash reporting simpler for enduser.
To: swain....@gmail.com

I'm a real end user as well, I enable crash reporting, but thats it. I
use Canary, which sometimes gets bent out of shape a bit, but I also
have a stable chrome installed and use that untill all those other
clever folks ( thanks guys/gals) get it fixed, then I go back to
canary again . I wouldn't know where to start reporting a crash and
don't really want to. In fact the only reason I subscribe to this list
is so I can fool myself into thinking I'm smart :)) LOL

> --
> Chromium Discussion mailing list: chromium...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-discuss
>

--
Sent from my mobile device

John Blake

--
Sent from my mobile device

John Blake

[krisdestruction]

I completely agree. Uploading crash data, version number, and
gathering OS information is a pain as an end-user.

On Jan 11, 6:17 am, John Blake <vk6...@gmail.com> wrote:
> ---------- Forwarded message ----------
> From: John Blake <vk6...@gmail.com>
> Date: Tue, 11 Jan 2011 19:15:08 +0800
> Subject: Re: [chromium-discuss] Make chrome crash reporting simpler for enduser.
> To: swain.suve...@gmail.com
>
> I'm a real end user as well, I enable crash reporting, but thats it. I
> use Canary, which sometimes gets bent out of shape a bit, but I also
> have a stable chrome installed and use that untill all those other
> clever folks ( thanks guys/gals) get it fixed, then I go back to
> canary again . I wouldn't know where to start reporting a crash and
> don't really want to. In fact the only reason I subscribe to this list
> is so I can fool myself into thinking I'm smart :)) LOL
>

> > Chromium Discussion mailing list: chromium-disc...@chromium.org