LOGGING_LEVEL: The current level of logging.
TIME: The current time in a 24-hour format of HH:MM:SS, which will help you narrow your search to the time an issue happened. PROCESS_ID: The identifier of the process that's currently running. 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).Įach line of the log file begins in a time-stamp format with the following elements:įor example: However, depending on the issue, this might not be the root cause. The first thing to look for in the chrome_debug.log file is the ERROR keyword. You can also open the file in a text editor and use the information below to identify problems. These tools present the logs in a graphical user interface that you can easily view, filter, and search. Tools 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. For information, see User Data Directory. The location of the directory depends on the operating system. You can stop the file from being overwritten by moving it to the desktop.
So, if you have an issue with the browser, check the log before you restart Chrome.
The file is overwritten every time Chrome restarts.
