Tuesday, October 27, 18:48
Home security Google Chrome and Edge create random debug.log logs

Google Chrome and Edge create random debug.log logs

An error in the latest version of Chrome and other Chromium-based browsers causes random debug.log files to be created on the desktop and other user folders.

debug.log Chrome

On October 6, 2020, Google released Chrome 86 and all users were automatically updated to this version. Other Chromium-based browsers, such as Brave and Microsoft Edge were also upgraded to this version at about the same time.

Chromium randomly generates debug.log files

From circulation of Chrome 86.0.4240.75, the browser started creating debug.log error logs on the user's desktop and other folders.

The debug.log file is the default log file used by Chromium-based browsers to log a bug.

With the latest browser version, an error causes creation debug.log files with the following message:

debug.log
chrome debug.log

Although Google has not officially explained it error, Chrome has a recurring problem archives and subdirectories in a folder and logs it as an error.

It is not known if this is a new bug that caused the problem or if Google enabled it register and forgot to turn it off.

Those users who are experiencing this issue can resolve it by deleting the contents of the Chromium Crashpad folder.

debug.log

The Crashpad folder is located at the following locations for Chrome, Edge, and Brave:

Chrome: C: \ Users \ [username] \ AppData \ Local \ Google \ Chrome \ User Data \ Crashpad

Edge: C: \ Users \ [username] \ AppData \ Local \ Microsoft \ Edge \ User Data \ Crashpad

Brave: C: \ Users \ User \ AppData \ Local \ BraveSoftware \ Brave-Browser \ User Data \ Crashpad

To delete the contents of the Crashpad folder, follow these steps:

1. Close all Chrome, Edge, or other browser instances with the problem.

2. Navigate to your browser's Crashpad folder.

3.Delete the contents of the Crashpad folder.

4. Restart Chrome to recreate the contents of the Crashpad folder.

Now that Crashpad has been restored, debug.log files should no longer be created.

1 COMMENT

LEAVE ANSWER

Please enter your comment!
Please enter your name here

Teo Ehc
Teo Ehchttps://www.secnews.gr
Be the limited edition.

LIVE NEWS

How to install a .watchface file on Apple Watch

The Apple Watch lets you customize the faces of the watch to display all kinds of useful information. But did you know ...

The five biggest data breaches of the 21st century

Data is becoming more and more sought after as our daily lives become more digitized. The technology giants that monopolize data are ...

Microsoft is limiting the availability of Windows 10 20H2

Microsoft is currently restricting the availability of Windows 10 20H2 to provide all users who want to ...

How to enable the new Chrome Read more feature

The latest version of Google Chrome browser, v86, released earlier this month, contains a secret feature called Read ...

How to choose a custom color for the Start menu

Starting with the October 2020 update, Windows 10 is the default on a theme that removes bright colors from ...

NASA telescope discovers drinking water on the moon

Eleven years ago, a spacecraft changed our view of the moon forever. The data collected by ...

Microsoft: Enhances password spray attack detection capabilities

Microsoft has significantly improved the ability to detect password spray attacks in the Azure Active Directory (Azure AD) and has reached the point ...

How to prevent companies from finding our phone number

In the age of advertising, the more user information is known the more convenient it is for companies. And in particular, the ...

Violation in a psychotherapy clinic led to blackmail of patients

Two years ago, a cyber attack took place in a Finnish psychotherapy clinic, which resulted in data theft and ransom demand. Now,...

Australia: Enhances cybersecurity and privacy!

The Government of New South Wales in Australia has set up a task force to strengthen cybersecurity and protection ...