interpreting chrome_debug.log

[Stephen Kramer]

Hi,

I found a method to launch Chrome with the option to record a debug log file and I made a new shortcut with this target:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --enable-logging --v=1 --no-sandbox

I found this method after reading this tweet https://twitter.com/chromiumdev/status/119169013644394496 about troubleshooting Aw Snap errors and following the instructions on this webpage about logging:  How to enable logging.

I am doing this because I am experiencing a bad problem with Chrome, and my other browsers (IE, Opera)  giving "cannot display webpage errors" (Aw Snap) and I really need to fix this I can't even load gmail in Chrome right now.  FYI I have an extensive list of troubleshooting completed, please see my post on:  Aw Snap all the time... Google Chrome Help Forum.

I now have a log file from starting Chrome, going to the Youtube website where it gives the Aw Snap error several times repeatedly but finally loads upon reloading many times.

Is there a way I can interpret what is going on in this file that might indicate the root of the problem?  If not, is there a better way to do this?

Any ideas and suggestions are greatly appreciated.

Thank you,

Stephen

I attached the file for reference.