Best way to debug Chrome crash

[Alastair Paterson]

Hi there,

I'm running Chrome 25 beta and have been experiencing strange behaviour for a few weeks now. Occasionally after a long-running browser session, opening a new tab and typing into the Omnibox will cause Chrome to close gracefully without any prompt from the user. No crash dialogue is presented, Chrome does not think it has crashed, nothing is logged to Console and the returned status code for the close is 0. 

This is annoying, although not the end of the world, and I would like to file a bug against Chrome, but do not think that this description will be particularly useful. I have tried running Chrome against GDB (with no settings changed/not using a special build) but it does not report a crash (instead, normal process termination), leading me to suspect it may be a different process crashing. 

What is the best way I can try and get meaningful data from this crash (unexpected close?) so I can report this issue?

Thanks in advance,

Alastair

[Mark Pearson]

If you are on Mac, this is probably http://crbug.com/175341

Normally for debugging crashes you should get the crash ID after it happens from chrome://crashes/

For this particular bug, there is no crash ID so that wouldn't help. :(

In general, try searching the bug database before posting to a mailing list.  Most issues you'll run into will have already been reported.  And if you can't find a issue, try posting a new bug with whatever little information you have.  In my experience, usually someone appears to mark the bug as a duplicate against a bug I couldn't find or someone appears to ask for more information (and helpfully tells me how to get it).

thanks,

mark

Thanks in advance,

Alastair