I’ll leave the more technical details to BleepingComputer’s article, but there’s clear evidence that Google is working towards this. Apparently, this feature is designed with enterprise/G Suite customers primarily in mind.
Sounds crazy, right? According to a commit first spotted by Chrome Story and since elaborated on by BleepingComputer, Google is working towards letting users log in to their Windows 10 machines using their Google accounts. Today, we’re seeing evidence that hints that Google may be working to let users log into Windows 10 using their Google accounts… SOURCE_CODE_FILE_NAME(LINE_NUMBER): The name of the source-code file that triggered the event to be logged.Google’s focus when it comes to computers is definitely centered on Chrome OS, but the company has done a lot for macOS and Windows as well. This is usually VERBOSE1 as set by the command line. 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.
0 kommentar(er)
