You can troubleshoot problems with Chrome Browser, such as hanging tabs and error messages. Use debug logs to help you. These logs aren't generated automatically. You need to turn on logging first. Note: Instructions assume that Chrome Browser is installed in the default location. Windows Mac
Linux
Debug logs are stored in the user data directory as chrome_debug.log. The file is overwritten every time Chrome restarts. So, if you have an issue with the browser, check the log before you restart Chrome. You can stop the file from being overwritten by moving it to the desktop. The location of the directory depends on the operating system. For information, see User Data Directory. Read the logsTools like Sawbuck on Microsoft® Windows® or Console on Apple® Mac® (located at Applications > Utilities > Console) can help you read the logs and find the source of a problem. These tools present the logs in a graphical user interface that you can easily view, filter, and search. You can also open the file in a text editor and use the information below to identify problems. What to look forThe first thing to look for in the chrome_debug.log file is the ERROR keyword. However, depending on the issue, this might not be the root cause. For example, if a user reports excessively long start times, you might see repeated lines at the beginning of the debug log or a high number of process IDs (PIDs) or thread IDs (TIDs). Each line of the log file begins in a time-stamp format with the following elements:
For example:
Was this helpful? How can we improve it? Finding Your Browser's Developer ConsoleNative web apps like Balsamiq Cloud can be tricky to troubleshoot, especially when it comes to the number of browser and browser plugins available to users today. One thing that can help us (and you) figure out what's going on is your browser's developer (or Javascript) console. Here is how to find it on most modern browsers.
Apple SafariBefore you can access the developer console in Safari, you first need to enable the Developer Menu. To do that, go into Safari's preferences (Safari Menu > Preferences) and select the Advanced Tab.
Once that menu is enabled, you will find the developer console by clicking on Develop > Show Javascript Console. You can also use the shortcut Option + ⌘ + C.
The console will either open up within your existing Safari window, or in a new window. It will automatically select the Console tab.
Google ChromeTo open the developer console in Google Chrome, open the Chrome Menu in the upper-right-hand corner of the browser window and select More Tools > Developer Tools. You can also use Option + ⌘ + J (on macOS), or Shift + CTRL + J (on Windows/Linux).
The console will either open up within your existing Chrome window, or in a new window. You may have to select the Console tab.
Mozilla FirefoxTo open the developer console in Firefox, click on the Firefox Menu in the upper-right-hand corner of the browser and select More Tools > Browser Console. You can also use the shortcut Shift + ⌘ + J (on macOS) or Shift + CTRL + J (on Windows/Linux).
The Browser console will open in a new window.
Microsoft EdgeTo open the developer console in Microsoft Edge, open the Edge Menu in the upper-right-hand corner of the browser window and select More Tools > Developer Tools. You can also press CTRL + Shift + i to open it.
The console will either open up within your existing Edge window, or in a new window. You may have to select the Console tab.
How do you access debugger in Chrome?The Chrome Web Inspector and Debugger are conveniently built-in with Chrome. You can launch it by hitting F12 while in your browser or by right clicking on a web page and selecting the Inspect menu item. The images below show a few different views that you'll see in the Chrome DevTools browser.
How do I open a browser debugger?How to open the devtools in your browser. Keyboard: Ctrl + Shift + I , except. Internet Explorer and Edge: F12. ... . Menu bar: Firefox: Menu. ... . Context menu: Press-and-hold/right-click an item on a webpage (Ctrl-click on the Mac), and choose Inspect Element from the context menu that appears.. How do I disable debugging in Chrome on Mac?Go to the "Sources" tab. At the top right hand side, toggle the button that looks like the pause symbol surrounded by a hexagon (button on the far right) until the color of the circle turns black to turn it off. If the pause symbol isn't blue it may be that you've accidentally marked a line for debugging inspection.
|