Firstly I'm really not sure if this is a question for Super-User or Stack-Overflow. It may certainly useful for other developers but it's not a specific code question.
In Google Chrome is there a way to look at render engine exceptions or general debugging info? I have some code which i'm 99% certain is crashing the render/repaint engine for chrome but (i'm on a mac) in the Console.app I don't get notifications for the exception. I'm wondering if theres a way of forcing chrome to be much more verbose in it's logging? Perhaps it's a webkit thing rather than chrome specific.
Let me know if this really isn't for stack overflow and I'll remove/close the question like I said I'm aware it's not code specific.
Firstly I'm really not sure if this is a question for Super-User or Stack-Overflow. It may certainly useful for other developers but it's not a specific code question.
In Google Chrome is there a way to look at render engine exceptions or general debugging info? I have some code which i'm 99% certain is crashing the render/repaint engine for chrome but (i'm on a mac) in the Console.app I don't get notifications for the exception. I'm wondering if theres a way of forcing chrome to be much more verbose in it's logging? Perhaps it's a webkit thing rather than chrome specific.
Let me know if this really isn't for stack overflow and I'll remove/close the question like I said I'm aware it's not code specific.
Share Improve this question edited May 4, 2012 at 13:53 Alex asked Apr 24, 2012 at 2:41 AlexAlex 3,7905 gold badges40 silver badges60 bronze badges 1- 1 Have you read this: chromium/developers/how-tos/…? – j08691 Commented May 4, 2012 at 15:26
3 Answers
Reset to default 6Yes!
You can start chrome from the mand line on a mac. See a previous question here
something like this:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
You can also pass a flag to make chrome output to a log file by appending:
--enable-logging --v=1
This should write a log file chrome_debug.log
which lives somewhere in your ~/.config/
directory.
Then you can tail that log. My mand for that is:
$ tail -F ~/.config/chromium/chrome_debug.log
Your path to the log file may be different.
Hope that helps!
In a similar way as Rimian's answer, in Windows you can also start Chrome from mand line enabling logging. Just open CMD and type:
cd C:\Program Files\Google\Chrome\Application
chrome --enable-logging --v=1
The log file chrome_debug.log
is in C:\Users\<USERNAME>\AppData\Local\Google\Chrome\User Data
. Notice you have to replace for your username.
I am not pletely sure whether I understood it correctly but maybe you want to check out chromium HOW-TO for mac rather than windows. you have two possibilities to debug the renderer process
a) Run Chrome in a single process or b) Attach XCode's debugger to a renderer process after launch
They are described in detail here. Hope that helps
EDIT: updated the link